Skip to content
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

Closed
w2650489 opened this issue Jul 14, 2023 · 3 comments
Closed

Comments

@w2650489
Copy link

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

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

Operating System

server centos7

Docker Selenium version (tag)

4.10

@w2650489 w2650489 changed the title [🐛 Bug]: selenium/standalone-chrome(grid docker) devtoo;s(cdp) not work [🐛 Bug]: selenium/standalone-chrome(grid docker) devtools(cdp) not work Jul 14, 2023
@github-actions
Copy link

@w2650489, thank you for creating this issue. We will troubleshoot it as soon as we can.


Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

@diemol
Copy link
Member

diemol commented Jul 14, 2023

@diemol diemol closed this as not planned Won't fix, can't repro, duplicate, stale Jul 14, 2023
Copy link

github-actions bot commented Dec 9, 2023

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.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants