Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chromium not opening in headful mode #334

Open
sai-sy opened this issue Jan 26, 2025 · 1 comment
Open

chromium not opening in headful mode #334

sai-sy opened this issue Jan 26, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@sai-sy
Copy link

sai-sy commented Jan 26, 2025

Environment

I know this was mentioned in issue 38 but it was closed as fixed and am confused as to what I'm doing wrong, I seem to be following the docs exactly

  • puppeteer / puppeteer-core Version:24.0.0
  • Node.js Version: 22

Expected Behavior

chromium browser should've happened

Current Behavior

I think steps are continueing without chromium browser? browser opens (console.log after launch) but business logic times out

Steps to Reproduce

  const browser = await puppeteer.launch({
    args: process.env.IS_LOCAL
      ? puppeteer.defaultArgs().concat([`--proxy-server=${newProxyUrl}`])
      : chromium.args.concat([`--proxy-server=${newProxyUrl}`]),
    defaultViewport: chromium.defaultViewport,
    headless: process.env.IS_LOCAL ? false : chromium.headless,
    //dumpio: true,
    executablePath: process.env.IS_LOCAL
      ? "C:/saiscripts/lib-sub/v4/chromium/win64-1411386/chrome-win/chrome.exe"
      : await chromium.executablePath(),
  });

.env

NODE_ENV=dev
IS_LOCAL=true
  • I don't get "browser was not found" (which I get when switching to my base chrome) so it knows it's there (and knows it is a browser?)
@sai-sy sai-sy added the bug Something isn't working label Jan 26, 2025
@Sparticuz
Copy link
Owner

  const browser = await puppeteer.launch({
    args: puppeteer.defaultArgs().concat([`--proxy-server=${newProxyUrl}`]),
    headless: false,
    executablePath: "C:/saiscripts/lib-sub/v4/chromium/win64-1411386/chrome-win/chrome.exe",
  });

does this work? if no, then it's most likely an issue with your chrome version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants