-
Notifications
You must be signed in to change notification settings - Fork 40
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
Not working with the docker image selenium/standalone-chrome:3.9 or newer #44
Comments
Could this be an issue with the docker image instead? Have you tried the debugging instructions at https://github.com/SeleniumHQ/docker-selenium#troubleshooting ? |
Hi. I suspect this is a problem with the JS library wd and how wd attempts to access the selenium hub instance. We have no problems accessing that container the normal selenium Java library. The first issue is that sessionId is null => I currently found no way to inspect the HTTP traffic wd sends to the selenium endpoint. If I interpret it correclty, the issue might be around that line in wd: The error message is confusing, the error handling in |
I get this error in selenoid when the appropriate selenoid image (selenoid/vnc_chrome:xxx) is not pulled manually in docker. |
When using this driver to connect to selenium/standalone-chrome:3.9 or newer, one gets a confusing error message:
Tried to use several configs, the session id is always undefined. Might be a bug somewhere in the wd dependency.
Workaround: Use the selenium/standalone-chrome:3.8 docker image.
The text was updated successfully, but these errors were encountered: