[🐛 Bug]: Nodes not registering to hub after v4 upgrade

[ryan-cpi]

What happened?

We are trying to update from v3 to v4 however, our nodes are not connecting to the hub. We are using the selenium hub docker image on a Linux machine and we have 5 Windows machines running the below command.
Ports 4442-4444 and 5555 are open between the servers.
Using the node-chrome docker image works fine for us its just when we try to run on windows we see this issue

What would be causing the nodes to not link up to the hub?

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

Linux Hub:
docker run  -d   --restart=unless-stopped --name selenium_grid_hub   -p 4444:4444 -p 4443:4443 -p 4442:4442    -e GRID_TIMEOUT="300" -e GRID_MAX_SESSION="4" -e GRID_BROWSER_TIMEOUT="900" -e VERSION=4.20   selenium/hub:4.20 

Windows Nodes:
java -jar selenium-server-4.24.0.jar node --hub 'http://nlb-internal.elb.us-east-1.amazonaws.com:4444' --enable-managed-downloads true --selenium-manager true

Relevant log output

HUB
2024-09-12 12:35:35,819 INFO Included extra file "/etc/supervisor/conf.d/selenium-grid-hub.conf" during parsing
2024-09-12 12:35:35,824 INFO RPC interface 'supervisor' initialized
2024-09-12 12:35:35,824 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-09-12 12:35:35,824 INFO supervisord started with pid 8
2024-09-12 12:35:36,827 INFO spawned: 'selenium-grid-hub' with pid 9
Appending Selenium options: --reject-unsupported-caps false
2024-09-12 12:35:36,842 INFO success: selenium-grid-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Tracing is disabled
12:35:38.328 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
12:35:38.354 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
12:35:38.768 INFO [BoundZmqEventBus.<init>] - XPUB binding to [binding to tcp://*:4442, advertising as tcp://172.17.0.3:4442], XSUB binding to [binding to tcp://*:4443, advertising as tcp://172.17.0.3:4443]
12:35:38.938 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://172.17.0.3:4442 and tcp://172.17.0.3:4443
12:35:39.023 INFO [UnboundZmqEventBus.<init>] - Sockets created
12:35:40.038 INFO [UnboundZmqEventBus.<init>] - Event bus ready
12:35:42.039 INFO [Hub.execute] - Started Selenium Hub 4.20.0 (revision 866c76ca80): http://172.17.0.3:4444
12:46:49.868 INFO [Node.<init>] - Binding additional locator mechanisms: relative


NODES
14:31:54.389 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
14:31:54.389 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
14:31:54.594 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://nlb-internal.elb.us-east-1.amazonaws.com:4442 and tcp://nlb-internal.elb.us-east-1.amazonaws.com:4443
14:31:54.651 INFO [UnboundZmqEventBus.<init>] - Sockets created
14:31:55.666 INFO [UnboundZmqEventBus.<init>] - Event bus ready
14:31:55.792 INFO [NodeServer.createHandlers] - Reporting self as: http://10.251.128.16:5555
14:31:55.822 INFO [NodeOptions.getSessionFactories] - Detected 4 available processors
14:31:56.713 INFO [NodeOptions.report] - Adding Firefox for {"browserName": "firefox","platformName": "Windows XP","se:downloadsEnabled": true} 4 times
14:31:56.713 INFO [NodeOptions.report] - Adding Internet Explorer for {"browserName": "internet explorer","platformName": "Windows XP"} 1 times
14:31:56.713 INFO [NodeOptions.report] - Adding Chrome for {"browserName": "chrome","platformName": "Windows XP","se:downloadsEnabled": true} 4 times
14:31:56.713 INFO [NodeOptions.report] - Adding Edge for {"browserName": "MicrosoftEdge","platformName": "Windows XP","se:downloadsEnabled": true} 4 times
14:31:56.744 INFO [Node.<init>] - Binding additional locator mechanisms: relative
14:31:56.901 INFO [NodeServer$1.start] - Starting registration process for Node http://10.251.128.16:5555
14:31:56.901 INFO [NodeServer.execute] - Started Selenium node 4.24.0 (revision 748ffc9bc3): http://10.251.128.16:5555
14:31:56.918 INFO [NodeServer$1.lambda$start$1] - Sending registration event...

Operating System

ubuntu22.04/windows2022

Docker Selenium version (image tag)

4.20.0

Selenium Grid chart version (chart version)

No response

[github-actions]

@ryan-cpi, 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]

Is this LB nlb-internal.elb.us-east-1.amazonaws.com allowed TCP via port 4443 and 4442?
Since it needs to reach publish-events and subscribe-events - https://www.selenium.dev/documentation/grid/configuration/cli_options/#node

[ryan-cpi]

The NLB seems to work fine when we are running in Linux and docker. Is there a missing argument that's needed when running the jar file directly?

We might just run with using Linux only for v4 and move away from managing Windows boxes.