[🐛 Bug]: BiDi webSocketUrl in selenium grid wrong

[mikk150]

What happened?

I run selenium grid in container with each node having it's own container
I run client in host machine(but it really doesn't matter)
I request chrome browser with BiDi support using

{
  "browserName":"chrome",
  "webSocketUrl":true
}

I get back session with json

{
  "value": {
    "sessionId": "7b43d50b454d1ec7c16b77bc980306c0",
    "capabilities": {
      "browserName": "chrome",
...
      "webSocketUrl": "ws:\u002f\u002f172.22.0.3:4444\u002fsession\u002f7b43d50b454d1ec7c16b77bc980306c0\u002fse\u002fbidi",
...
    }
  }
}

Problem is that webSocketUrl is pointing to chrome node IP address, that does not run selenium
It should be

How can we reproduce the issue?

https://github.com/mikk150/selenium-bidi-wrong-url

start docker containers using provided docker-compose file
start `./reproduce.sh`

see how `webSocketUrl` is not selenium grid URL
it should be `ws://localhost:4444/session/<sessionId>/se/bidi` instead

Relevant log output

It's bash output

Operating System

Manjaro, Docker

Selenium version

not applicable

What are the browser(s) and version(s) where you see this issue?

Chrome 133

What are the browser driver(s) and version(s) where you see this issue?

The ones that are in docker container...

Are you using Selenium Grid?

4.29.0

[github-actions]

@mikk150, 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]

Have a look at https://github.com/SeleniumHQ/docker-selenium?tab=readme-ov-file#grid-url-and-session-timeout

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.