[🐛 Bug]: Selenium HUB Websocket URL is not correctly formatted

[NikolaZag]

What happened?

I am running a Selenium Hub with nodes in Openshift(kubernetes) Environment and noticed a strange formatting of the websocket url.

From what I've looked the websocket url should be "ws://selenium-hub..." but when checking the logs I can see it is "ws:/selenium-hub"

How exactly is this managed and can it be changed/setup correctly ?

There is nothing special in the setup of the Hub/nodes

How can we reproduce the issue?

Not exactly sure. The Setup is straight forward:
Using the Selenium Docker image, which was mirrored in a QUAY internal repo and running it in an Openshift Environment. 

these are the Env. variables that have been added. 
   env:
            - name: SE_OPTS
              value: '--tracing false'
            - name: SE_VNC_NO_PASSWORD
              value: '1'
            - name: JAVA_OPTS
              value: '-Djdk.httpclient.websocket.intermediateBufferSize=3000000'
            - name: SE_SESSION_REQUEST_TIMEOUT
              value: '180'
            - name: SE_SESSION_RETRY_INTERVAL
              value: '10'
            - name: GRID_MAX_SESSION
              value: '40'
            - name: SE_OPTS
              value: '--log-level INFO'
            - name: SE_JAVA_OPTS
              value: '-Xms256m'
            - name: SE_JAVA_OPTS
              value: ' -Xmx1024M'


Edge node env. Variables 


  env:
        - name: SE_EVENT_BUS_HOST
          value: selenium-hub-svc
        - name: SE_EVENT_BUS_PUBLISH_PORT
          value: '4442'
        - name: NODE_MAX_INSTANCES
          value: '10'
        - name: SE_EVENT_BUS_SUBSCRIBE_PORT
          value: '4443'
        - name: SE_OPTS
          value: '--tracing false'
        - name: SE_VNC_NO_PASSWORD
          value: '1'
        - name: JAVA_OPTS
          value: '-Djdk.httpclient.websocket.intermediateBufferSize=3000000'
        - name: SE_NODE_SESSION_TIMEOUT
          value: '120'
        - name: SE_NODE_GRID_URL
          value: masked url
        - name: SE_OPTS
          value: '--enable-managed-downloads true'
        - name: SE_JAVA_OPTS
          value: ' -Xmx1024M'
        - name: SE_NODE_OVERRIDE_MAX_SESSIONS
          value: 'true'
        - name: SE_NODE_MAX_SESSIONS
          value: '3'
        - name: SE_OPTS
          value: '--log-level FINE'

Relevant log output

Session created by the Node. Id: 53716055f22afe4ab32f90f5e89a107e, Caps: Capabilities {acceptInsecureCerts: true, browserName: MicrosoftEdge, browserVersion: 132.0.2957.140, fedcm:accounts: true, ms:edgeOptions: {debuggerAddress: localhost:4444}, msedge: {msedgedriverVersion: 132.0.2957.140 (a81e27b375d..., userDataDir: /tmp/.com.microsoft.Edge.sx...}, networkConnectionEnabled: false, pageLoadStrategy: eager, platformName: linux, proxy: Proxy(), se:cdp: ws:/selenium-hub-****-****..., se:cdpVersion: 132.0.2957.140, se:containerName: node-edge-86d7958bb9-mbd5c, se:gridWebSocketUrl: ws://localhost:25423/sessio..., se:noVncPort: 7900, se:vnc: ws:/selenium-hub-***-***..., se:vncEnabled: true, se:vncLocalAddress: ws://10.128.37.203:7900, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webSocketUrl: ws:/selenium-hub-****-***..., webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:extension:minPinLength: true, webauthn:extension:prf: true, webauthn:virtualAuthenticators: true}

Operating System

Linux

Selenium version

4.28.1

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

Edgedriver v.132.0

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

Edgedriver v.132.0

Are you using Selenium Grid?

4.28.1

[github-actions]

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

I think you should look at Node env var SE_NODE_GRID_URL it will construct the se:cdp endpoint, via session capabilities you can see it. Ensure it is using the public ip can be accessed from outside the cluster

[NikolaZag]

I think you should look at Node env var SE_NODE_GRID_URL it will construct the se:cdp endpoint, via session capabilities you can see it. Ensure it is using the public ip can be accessed from outside the cluster

the url is supposedly set correctly. I will look into it some more. Wasn't sure how exactly from where that url was coming.

[NikolaZag]

I think you should look at Node env var SE_NODE_GRID_URL it will construct the se:cdp endpoint, via session capabilities you can see it. Ensure it is using the public ip can be accessed from outside the cluster

Edit: Yeah that was the issue. Now it is working fine.

[VietND96]

Yes, great to hear 🎉

[NikolaZag]

Yes, great to hear 🎉

I've only put the address of the hub without http, it was working in general, but I guess it mattered somewhere.

[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.