-
Notifications
You must be signed in to change notification settings - Fork 9k
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]: WSS Connection to Browserless Hangs #11268
Comments
The issue has been labeled as confirmed by the automatic analyser. |
|
Interesting. Is there a way for us to test it without the creation of the browserless account? |
Alternatively, could you provide the CDP log by running with the env var |
Unfortunately, Browserless doesn't have an endpoint that doesn't require a token. They do have a free tier that would suffice for troubleshooting. Here is the debug output:
|
@jwkuo interesting, it looks like the browser does not attach any targets on |
Noted. I've reached out to Browserless with this issue. |
Some context: there were a lot of changes in auto-attach in Chrome, in particular, many issues around tab target has been fixed . Starting from 21.4.0 Puppeteer relies on the new target type: #11099 We generally don't guarantee compatibility of new Puppeteer versions with older browser binaries and we recommend using the version that is bundled with a specific Puppeteer release. |
Minimal, reproducible example
Error string
no error
Bug behavior
Background
Version 21.4.1 hangs when connecting via secure websocket to Browserless. Version 21.3.8 successfully connects and sets browser for further interaction.
Expectation
Puppeteer should connect and set the browser const for further interaction.
Reality
The script hangs indefinitely.
Puppeteer configuration file (if used)
No response
Puppeteer version
21.4.1
Node version
18.18.2
Package manager
npm
Package manager version
9.8.1
Operating system
Linux
The text was updated successfully, but these errors were encountered: