-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
Puppeteer-sharp no longer seems to work for me since v9.0 #2280
Comments
Do you have any code I can use to reproduce the issue? |
Here's the code that is used to create a PDF from HTML. Let me know if you need anything else.
|
Any chance you can send me the server to my email? |
No, it's not available to the public internet. I can send you logs of the browserless chrome intance if that would help. |
Maybe the browser version you have on the other side is not compatible? |
I am using this docker image: https://hub.docker.com/layers/browserless/chrome/1-puppeteer-1.20.0/images/sha256-bf82032782dfc6de7d24ca65ac94ec117f89dc35f72df3800c599bd201120b23?context=explore What changed between puppeteer sharp 8, 9 and 10 that would make a browser no longer compatible? |
@brechtvhb The |
I just shipped v10.1.4. Can you try that version? |
v10.1.4 does not solve the issue. Using browserless/chrome:latest (or browserless/chrome:1-chrome-stable-112.0.5615.49) fixed the issue. I set it to browserless/chrome:1-puppeteer-1.20.0 around new year because the new headless mode they introduced was causing issues back then. |
Nice! Can we close this? |
Yeah, that's OK for me. Thanks for helping me out! |
Everything is working fine on version 8.0.
But when I try to upgrade to 9.0 (to 10.0) I get this error when trying to create a page:
When I upgrade to 10.1.0 or higher awaiting
await Puppeteer.ConnectAsync(options);
times outI am connecting to a browserless chrome instance on AKS (browserless/chrome:1-puppeteer-1.20.0)
with these settings:
KEEP_ALIVE : true
MAX_CONCURRENT_SESSIONS : 2
PREBOOT_CHROME : true
The code to connect is:
The text was updated successfully, but these errors were encountered: