-
-
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
[🐛 Bug]: selenium/standalone-chrome(grid docker) devtools(cdp) not work #1892
Comments
@w2650489, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
when java run :driver = new Augmenter().augment(driver);
ERROR:java.net.ConnectException: connection timed out: /172.17.0.6:4444
Unable to establish websocket connection to http://172.17.0.6:4444/session/ef499e9888d5197b4c162f636a94b777/se/cdp
this ip is in docker network ,not server ip. so java can't use devtools(cdp).i want use 192.168.1.x ip like this.
Command used to start Selenium Grid with Docker
docker run -d -p 4444:4444 -p 7900:7900 --shm-size="2g" selenium/standalone-chrome:latest
Relevant log output
Operating System
server centos7
Docker Selenium version (tag)
4.10
The text was updated successfully, but these errors were encountered: