[🐛 Bug]: Unable to register selenium node to remote selenium hub 4

[capnand]

What happened?

I'm using selenium grid 4.22.0
I'm running selenium hub in a k8 cluster and all required ports like 4444, 4442, 4443 are correctly exposed and working.
So when Im trying to register my local windows as a node to remote selenium hub, Im a having issues
I tried in two ways

1. java -jar selenium-server-4.22.0.jar node --publish-events tcp://:4442 --subscribe-events tcp://:4443
   it is sending multiple registration requests to hub
   

2. java -jar selenium-server-4.22.0.jar node --publish-events tcp://:4442 --subscribe-events tcp://:4443 --host
   Im getting Caused by: java.net.BindException: Cannot assign requested address: bind
   

How can we reproduce the issue?

note use selenium grid 4
1.run selenium hub in k8 cluster or run selenium hub in different machine
2. try connecting selenium node to remote selenium hub

Relevant log output

1. java -jar selenium-server-4.22.0.jar node --publish-events tcp://<hubip>:4442 --subscribe-events tcp://<hubip>:4443 
it is sending multiple registration requests to hub
![image](https://github.com/user-attachments/assets/5e7d16c9-466f-468d-a39f-43f86f908dbe)

2. java -jar selenium-server-4.22.0.jar node --publish-events tcp://<hubip>:4442 --subscribe-events tcp://<hubip>:4443  --host <public ip of node>
Im getting Caused by: java.net.BindException: Cannot assign requested address: bind
![image](https://github.com/user-attachments/assets/2352ad0c-1161-44cb-afe7-3e9bf99fb444)

Operating System

windows 10

Selenium version

4.22.0

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

nothing

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

nothing

Are you using Selenium Grid?

4.22.0

[github-actions]

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

[pujagani]

Thank you for sharing the details.

1. If you are starting multiple nodes, ensure each uses a different port. The default node uses port 5555. So if you have a node running on it and you try to run a different node then you will get the exception you shared. Use the option: --port to pass in a port exclusively. Example: java -jar selenium-server-4.25.0.jar node --port 5556
2. Pass in the public URI of the Hub using the option --hub. Refer

   selenium/java/src/org/openqa/selenium/grid/node/config/NodeFlags.java

   Line 132 in 40bfc5e

   names = {"--hub"},

   .

[capnand]

Hi Puja I'm not running multiple nodes. I'm trying to connect single node with default port and also Im passing public url in --hub I'm able to connect to hub within its connect but when Im trying to connect I'm facing issue

…

On Tue, Oct 8, 2024 at 1:56 PM Puja Jagani ***@***.***> wrote: Thank you for sharing the details. 1. If you are starting multiple nodes, ensure each uses a different port. The default node uses port 5555. So if you have a node running on it and you try to run a different node then you will get the exception you shared. Use the option: --port to pass in a port exclusively. Example: java -jar selenium-server-4.25.0.jar node --port 5556 2. Pass in the public URI of the Hub using the option --hub. Refer https://github.com/SeleniumHQ/selenium/blob/40bfc5e2bd473737d89aa1d47f64d3d67d23dd14/java/src/org/openqa/selenium/grid/node/config/NodeFlags.java#L132 . — Reply to this email directly, view it on GitHub <#14573 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJZZ7O5SW224ABU7QUJPUGTZ2OJMPAVCNFSM6AAAAABPQW4NZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJZGE4TANRVGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[pujagani]

I am not sorry I did not understand what you meant. Can you please elaborate? You are able to connect to the Hub but the registration is not happening. Are you passing the correct parameters for the event bus?
The link I shared points to this comment:

"The address of the Hub in a Hub-and-Node configuration. This can "
              + "be a plain hostname or IP address (`hostname`), in which case the Hub will be "
              + "assumed to be `http://hostname:4444`, the `--grid-url` will be the same, "
              + "`--publish-events` will be `tcp://hostname:4442` and `--subscribe-events` "
              + "will be `tcp://hostname:4443`. If `hostname` contains a port number, that "
              + "will be used for `--grid-url` but the URIs for the event bus will remain "
              + "the same. Any of these default values may be overridden but setting the "
              + "correct flags. If the hostname has  a protocol (such as `https`) that will "
              + "be used too."

[VietND96]

I think you have to explicit define the IP (or at least localhost if it is exposed in same machine) instead of e.g --publish-events tcp://:4442

[diemol]

I will close this as the issue has not had any more activity.

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