-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Exception: unknown error: unable to discover open pages #56
Comments
I also tried the standalone chrome Docker image, but same error their appeared also. I also updated the Chromedriver to 2.15 in the "selenium/node-chrome" image. But same problem still. It works however with this image: https://github.com/elgalu/docker-selenium |
@elgalu Maybe you have a clue what is wong? thanks! |
Getting a timeout also with https://github.com/elgalu/docker-selenium when I remove the |
So privileged fixes the issue on this repo too? Idk how to troubleshoot this issue unless you provide a public GitHub minimum selenium project that reproduces it. |
Unortunately I have only time to test this repo next week again. I'm not sure if I can provide such a minimal project here. The thing is locally on my private machine all works fine, however on server side (digitalocean, Docker 1.4.1, ubuntu precise) the problem occurs and only 'privileged' can solve it. |
If anyone still has an issue with this error please check my proposed solution at this link: http://stackoverflow.com/questions/21001652/chrome-driver-error-using-selenium-unable-to-discover-open-pages/38700776#38700776 Look for the answer by pelican, hope that helps out someone! |
Closing this issue as it got solved in the SO link provided above. |
Having the following issue with docker image "selenium/node-chrome"
https://gist.github.com/anonymous/b4b0f90d2889d310a1a0
any ideas what might causing this?
the firefox node is just working like a charm
thanks a lot
m
The text was updated successfully, but these errors were encountered: