-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[BUG] Playwright cannot talk to Chromium on Heroku #1568
Comments
Any updates on this? Having the same issue. EDIT: #2205 Make sure the --no-sandbox flag is set when running on heroku. Everything seems to be working fine on heroku with the latest version of playwright and the the build pack.
|
Thanks for checking this @Wisbell. Can you share more info on your Heroku config (e.g., which buildpack are you using)? We'd love to add it to the docs for other users. |
Buildpack: https://github.com/jontewks/puppeteer-heroku-buildpack And of course whatever nodejs buildpack heroku automatically adds. The package.json for the library I am using has this playwright version: "playwright": "^0.15.0" |
@arjun27 assigning to make sure it is in the docs and can be closed. |
@Wisbell I'm doing exactly the same steps, and it's not working.
|
@pcborges I've created a Heroku buildpack for running Playwright including Chromium and Firefox on Heroku, let me know if it fits for your needs: https://github.com/mxschmitt/heroku-playwright-buildpack/ |
@mxschmitt It worked very well, I just needed to remove the playwright package and install playwright-firefox as in your example, and added your buildpack before nodejs. |
Context:
Chromium doesn’t work with Playwright on Heroku even with the recommended puppeteer build pack that worked with Playwright 0.9. Details and discussion in #634
To reproduce, use this repo and change the Playwright version: https://github.com/diervo/testing-heroku-playwright
The text was updated successfully, but these errors were encountered: