Puppeteer Error: Failed to launch browser process

1

Not quite sure what is going on, but I have reviewed all the posts here, especially this one (which my setup directly mirrors): Puppeteer failed to launch browser process and not sure why I am running into issues getting Puppeteer to run properly on Render.

I would have just continued on that previous thread, but it was closed.

Any ideas?

2

Hi there,

Looks like you are getting an EACCES error when trying to launch Chrome. This is different to the issue you linked. From what I can see, it looks like you are doing the right things, so I don’t understand why you are getting permission errors on Chrome.

Can you try setting DEBUG=puppeteer:browsers:launcher when you run your code. This will give you additional debug logs when Puppeteer is launching Chrome.

Regards,

Keith
Render Support, UTC+10 :australia:

3

Hmmm…yeah, not sure what’s going on. It appears as though the launcher is coming back as undefined. Here’s the error dump:

2024-08-13T02:57:00.491Z puppeteer:browsers:launcher Launching /opt/render/project/puppeteer --allow-pre-commit-input --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-component-update --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-hang-monitor --disable-infobars --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-search-engine-choice-screen --disable-sync --enable-automation --export-tagged-pdf --generate-pdf-document-outline --force-color-profile=srgb --metrics-recording-only --no-first-run --password-store=basic --use-mock-keychain --disable-features=Translate,AcceptCHFrame,MediaRouter,OptimizationHints,ProcessPerSiteUpToMainFrameThreshold,IsolateSandboxedIframes --enable-features=PdfOopif --headless --hide-scrollbars --mute-audio about:blank --no-sandbox --disable-setuid-sandbox --remote-debugging-port=0 --user-data-dir=/tmp/puppeteer_dev_chrome_profile-XXXXXXUMQg1u {
  detached: true,
  env: {
    PUPPETEER_CACHE_DIR: '/opt/render/project/puppeteer',
    PUPPETEER_SKIP_CHROMIUM_DOWNLOAD: 'true',
    PUPPETEER_EXECUTABLE_PATH: '/opt/render/project/puppeteer',
    PUPPETEER_EXPERIMENTAL_CHROMIUM_MAC_ARM: 'true'
  },
  stdio: [ 'pipe', 'ignore', 'pipe' ]
}
2024-08-13T02:57:00.499Z puppeteer:browsers:launcher Launched undefined
Error: Failed to launch the browser process! spawn /opt/render/project/puppeteer EACCES

Any chance you have seen this before? I was just searching the Puppeteer issues and haven’t come across anything referencing undefined, but other errors after getting a valid—numeric—launcher.

4

Hi there,

Are you setting this: PUPPETEER_EXECUTABLE_PATH: '/opt/render/project/puppeteer'? If so, please unset it as this doesn’t look correct to me.

Regards,

Keith
Render Support, UTC+10 :australia:

5

Thank you so much, Keith. I think I must have got some wires crossed the last time I was trying to get this up and running, and didn’t realize it when I recently came back to it.

Everything appears to be working properly now. Thanks!

6

HI there,

No problem. Glad to hear it is now working.

Regards,

Keith
Render Support, UTC+10 :australia:

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.