[🐛 Bug]: Unable to open CDP after #2876

[papegaaij]

What happened?

The change in #2876 broke all our tests, because the Chromium driver is no longer able to setup a CDP connection. In the log snippet, you can see that we connect at http://10.255.25.101:4444/wd/hub but the capabilities reported contain se:cdp: ws://localhost:4444/session. This seem to cause SeleniumCdpConnection to try to connect at localhost, which obviously doesn't work. For now, we've worked around this issue by setting SE_NODE_GRID_URL to an empty value.

Command used to start Selenium Grid with Docker (or Kubernetes)

Arquillian-cube:
keyhub-chrome*:
    image: selenium/standalone-chromium
    exposedPorts: [4444/tcp]
    networkMode: keyhub-test-nw
    removeVolumes: true
    shmSize: 268435456 #256M in bytes
    memoryLimit: 3221225472 #3G in bytes
    env:
        - START_XVFB=false
        - SE_NODE_MAX_SESSIONS=10
        - SE_NODE_OVERRIDE_MAX_SESSIONS=true
        - SE_NODE_SESSION_TIMEOUT=86400
        - "SE_JAVA_OPTS=-Dwebdriver.chrome.verboseLogging=true -Dwebdriver.chrome.logfile=/dev/stdout"
    await:
        strategy: polling
        sleepTime: 500ms
        ports: [4444]
        iterations: 120

Relevant log output

2025-07-08 06:39:45,575 [pool-2-thread-7] INFO org.jboss.arquillian.drone.webdriver.factory.DockerRemoteWebDriverFactory - Using Selenium WebDriver at http://10.255.25.101:4444/wd/hub
2025-07-08 06:39:46,295 [main] INFO nl.topicus.keyhub.arquillian.setup.WildFlySetup - Browser (TestAdmin): RemoteWebDriver: chrome on linux (4da16fe981a3def290694cefda73f945) - Capabilities {acceptInsecureCerts: true, browserName: chrome, browserVersion: 138.0.7204.92, chrome: {chromedriverVersion: 138.0.7204.92 (f079b9bc781e..., userDataDir: /tmp/.org.chromium.Chromium...}, fedcm:accounts: true, goog:chromeOptions: {debuggerAddress: localhost:41843}, goog:loggingPrefs: {browser: ALL}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: linux, proxy: Proxy(), se:bidiEnabled: false, se:cdp: ws://localhost:4444/session..., se:cdpVersion: 138.0.7204.92, se:containerName: c0a020ae1408, se:deleteSessionOnUi: true, se:downloadsEnabled: true, se:noVncPort: 7900, se:vnc: ws://localhost:4444/session..., se:vncEnabled: true, se:vncLocalAddress: ws://10.255.25.101:7900, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:extension:minPinLength: true, webauthn:extension:prf: true, webauthn:virtualAuthenticators: true}
2025-07-08 06:39:46,491 [main] WARN org.openqa.selenium.devtools.CdpVersionFinder - Unable to find an exact match for CDP version 138, returning the closest version; found: 137; Please update to a Selenium version that supports CDP version 138
2025-07-08 06:39:46,558 [main] ERROR nl.topicus.keyhub.arquillian.selenium.AbstractKeyHubSeleniumTest - JdkWebSocket initial request execution error
Build info: version: '4.33.0', revision: '2c6aaad03a'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '5.14.0-503.38.1.el9_5.x86_64', java.version: '21.0.7'
Driver info: driver.version: unknown
org.openqa.selenium.remote.http.ConnectionFailedException: JdkWebSocket initial request execution error
Build info: version: '4.33.0', revision: '2c6aaad03a'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '5.14.0-503.38.1.el9_5.x86_64', java.version: '21.0.7'
Driver info: driver.version: unknown
	at org.openqa.selenium.remote.http.jdk.JdkHttpClient.openSocket(JdkHttpClient.java:253)
	at org.openqa.selenium.devtools.Connection.<init>(Connection.java:89)
	at org.openqa.selenium.devtools.SeleniumCdpConnection.<init>(SeleniumCdpConnection.java:36)
	at org.openqa.selenium.devtools.SeleniumCdpConnection.lambda$create$2(SeleniumCdpConnection.java:103)
	at java.base/java.util.Optional.map(Optional.java:260)
	at org.openqa.selenium.devtools.SeleniumCdpConnection.create(SeleniumCdpConnection.java:103)
	at org.openqa.selenium.devtools.SeleniumCdpConnection.create(SeleniumCdpConnection.java:49)
	at org.openqa.selenium.devtools.DevToolsProvider.getImplementation(DevToolsProvider.java:50)
	at org.openqa.selenium.devtools.DevToolsProvider.getImplementation(DevToolsProvider.java:29)

Operating System

AlmaLinux 8

Docker Selenium version (image tag)

4.34.0-20250707

Selenium Grid chart version (chart version)

No response

[github-actions]

@papegaaij, 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!

[VietND96]

http://10.255.25.101:4444/wd/hub

I guess this is a container IP, and your test run in the same container network, so the endpoint could be reached, right?

[papegaaij]

Yes, that's correct. I suspect, it will also work correctly when we set SE_NODE_GRID_URL to http://10.255.25.101:4444/wd/hub, but just clearing it was easier.

[VietND96]

Hmm, the default was added due to few people get started with Grid in container, the endpoint use container IP which could not be reached if the script is executed on host. But looks like this impacts the user run tests in container network

[VietND96]

I will rollback default value and patch to the same image tag

[papegaaij]

Thank you for the quick response!

[github-actions]

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.