Closed ryan-cpi closed 3 weeks ago
@ryan-cpi, thank you for creating this issue. We will troubleshoot it as soon as we can.
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!
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
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.
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)
Relevant log output
Operating System
ubuntu22.04/windows2022
Docker Selenium version (image tag)
4.20.0
Selenium Grid chart version (chart version)
No response