[🐛 Bug]: Node can't connect to Grid hub from version 4.14.0 (Error checking service status http://localhost:4723/status)

[VitaliiPivtorak]

What happened?

From version 4.14.0 node can't connect to hub ( checked on 4.10, 4.13 ,4.14.0, 4.14.1, 4.16.1, selenium-server-4.17.0-SNAPSHOT). it works on 4.13 and below.

from browser run link "http://localhost:4723/status"- {"value":{"ready":true,"message":"The server is ready to accept new connections","build":{"version":"2.4.1"}}}

node window result:
.@ Grid % java -jar selenium-server-4.16.1.jar node --config node4.toml
15:48:48.216 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
15:48:48.220 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
15:48:48.268 INFO [UnboundZmqEventBus.] - Connecting to tcp://0.0.0.0:4442 and tcp://0.0.0.0:4443
15:48:48.289 INFO [UnboundZmqEventBus.] - Sockets created
15:48:49.295 INFO [UnboundZmqEventBus.] - Event bus ready
15:48:49.393 INFO [NodeServer.createHandlers] - Reporting self as: http://192.168.1.144:5557
15:48:49.403 INFO [NodeOptions.getSessionFactories] - Detected 10 available processors
15:48:49.411 INFO [RelayOptions.getSessionFactories] - Adding relay configs for http://localhost:4723
15:48:49.415 INFO [RelayOptions.lambda$getSessionFactories$1] - Mapping Capabilities {appium:automationName: UiAutomator2, appium:deviceName: Pixar 5а, appium:platformVersion: 13, platformName: ANDROID}, 1 times
15:48:49.415 INFO [RelayOptions.lambda$getSessionFactories$1] - Mapping Capabilities {appium:automationName: UiAutomator2, appium:deviceName: Pixar 4, appium:platformVersion: 13, platformName: ANDROID}, 1 times
15:48:49.437 INFO [Node.] - Binding additional locator mechanisms: relative
15:48:49.509 INFO [NodeServer$1.start] - Starting registration process for Node http://192.168.1.144:5557
15:48:49.510 INFO [NodeServer.execute] - Started Selenium node 4.16.1 (revision 9b4c833): http://192.168.1.144:5557
15:48:49.620 WARN [RelaySessionFactory.isServiceUp] - Error checking service status http://localhost:4723/status. java.io.IOException: HTTP/1.1 header parser received no bytes
15:48:49.621 ERROR [NodeServer$1.lambda$start$1] - Node is not alive: http://192.168.1.144:5557 is DOWN

How can we reproduce the issue?

java version "21.0.2" (same with "20.0.2")
grid - 4.16.1 (also checked selenium-server-4.17.0-SNAPSHOT, and 4.15) 
Appium v2.4.1

1. Run hub "sudo java -jar selenium-server-4.16.1.jar hub" 
2. Run node "java -jar selenium-server-4.16.1.jar node --config node4.toml"


# node4.toml
[server]
port = 5557
[node]
detect-drivers = false

[relay]
# Default Appium/Cloud server endpoint
url = "http://localhost:4723"
status-endpoint = "/status"
configs = ["1", "{\"platformName\": \"Android\", \"appium:platformVersion\": \"13\", \"appium:deviceName\": \"Pixar 5а\", \"appium:automationName\": \"UiAutomator2\"}",
"1", "{\"platformName\": \"Android\", \"appium:platformVersion\": \"13\", \"appium:deviceName\": \"Pixar 4\", \"appium:automationName\": \"UiAutomator2\"}"]

Relevant log output

____._____@_________ Grid % java -jar selenium-server-4.16.1.jar node --config node4.toml
15:48:48.216 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
15:48:48.220 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
15:48:48.268 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://0.0.0.0:4442 and tcp://0.0.0.0:4443
15:48:48.289 INFO [UnboundZmqEventBus.<init>] - Sockets created
15:48:49.295 INFO [UnboundZmqEventBus.<init>] - Event bus ready
15:48:49.393 INFO [NodeServer.createHandlers] - Reporting self as: http://192.168.1.144:5557
15:48:49.403 INFO [NodeOptions.getSessionFactories] - Detected 10 available processors
15:48:49.411 INFO [RelayOptions.getSessionFactories] - Adding relay configs for http://localhost:4723
15:48:49.415 INFO [RelayOptions.lambda$getSessionFactories$1] - Mapping Capabilities {appium:automationName: UiAutomator2, appium:deviceName: Pixar 5а, appium:platformVersion: 13, platformName: ANDROID}, 1 times
15:48:49.415 INFO [RelayOptions.lambda$getSessionFactories$1] - Mapping Capabilities {appium:automationName: UiAutomator2, appium:deviceName: Pixar 4, appium:platformVersion: 13, platformName: ANDROID}, 1 times
15:48:49.437 INFO [Node.<init>] - Binding additional locator mechanisms: relative
15:48:49.509 INFO [NodeServer$1.start] - Starting registration process for Node http://192.168.1.144:5557
15:48:49.510 INFO [NodeServer.execute] - Started Selenium node 4.16.1 (revision 9b4c83354e): http://192.168.1.144:5557
15:48:49.620 WARN [RelaySessionFactory.isServiceUp] - Error checking service status http://localhost:4723/status. java.io.IOException: HTTP/1.1 header parser received no bytes
15:48:49.621 ERROR [NodeServer$1.lambda$start$1] - Node is not alive: http://192.168.1.144:5557 is DOWN

Operating System

Mac os 14.2.1

Selenium version

4.16.1

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

appium

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

2.4.1

Are you using Selenium Grid?

4.16.1

[github-actions]

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

[diemol]

Why is http://localhost:4723/ returning that error?

[diemol]

@VitaliiPivtorak can you please check that?

[VitaliiPivtorak]

Why is http://localhost:4723/ returning that error?

I am running hub and node on same Mac and use url = "http://localhost:4723" in toml file. Without any changes it works on version 4.13.0

[VitaliiPivtorak]

@VitaliiPivtorak can you please check that?

I have checked new version 4.17.0, and replace localhost with ip address in toml file problem the same:
@ Grid % java -jar selenium-server-4.17.0.jar node --config node4.toml
12:58:58.609 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
12:58:58.612 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
12:58:58.663 INFO [UnboundZmqEventBus.] - Connecting to tcp://0.0.0.0:4442 and tcp://0.0.0.0:4443
12:58:58.682 INFO [UnboundZmqEventBus.] - Sockets created
12:58:59.684 INFO [UnboundZmqEventBus.] - Event bus ready
12:58:59.779 INFO [NodeServer.createHandlers] - Reporting self as: http://192.168.1.144:5557
12:58:59.788 INFO [NodeOptions.getSessionFactories] - Detected 10 available processors
12:58:59.798 INFO [RelayOptions.getSessionFactories] - Adding relay configs for http://192.168.1.144:4723
12:58:59.801 INFO [RelayOptions.lambda$getSessionFactories$1] - Mapping Capabilities {appium:automationName: UiAutomator2, appium:deviceName: Pixar 5а, appium:platformVersion: 13, platformName: ANDROID}, 1 times
12:58:59.801 INFO [RelayOptions.lambda$getSessionFactories$1] - Mapping Capabilities {appium:automationName: UiAutomator2, appium:deviceName: Pixar 4, appium:platformVersion: 13, platformName: ANDROID}, 1 times
12:58:59.822 INFO [Node.] - Binding additional locator mechanisms: relative
12:58:59.890 INFO [NodeServer$1.start] - Starting registration process for Node http://192.168.1.144:5557
12:58:59.891 INFO [NodeServer.execute] - Started Selenium node 4.17.0 (revision e52b1be*): http://192.168.1.144:5557
12:58:59.995 WARN [RelaySessionFactory.isServiceUp] - Error checking service status http://192.168.1.144:4723/status. java.io.IOException: HTTP/1.1 header parser received no bytes
12:58:59.996 ERROR [NodeServer$1.lambda$start$1] - Node is not alive: http://192.168.1.144:5557 is DOWN

[diemol]

OK, might be related to the JDK 11 HTTP client.

[ShivasinyV]

@VitaliiPivtorak im getting same issue by using 4.13 version also.

[VitaliiPivtorak]

@VitaliiPivtorak im getting same issue by using 4.13 version also.

Same toml file only change grid version (for hub and node run) is working:
@_ Grid % java -jar selenium-server-4.13.0.jar node --config node4.toml
10:41:19.765 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
10:41:19.768 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
10:41:19.823 INFO [UnboundZmqEventBus.] - Connecting to tcp://0.0.0.0:4442 and tcp://0.0.0.0:4443
10:41:19.845 INFO [UnboundZmqEventBus.] - Sockets created
10:41:20.847 INFO [UnboundZmqEventBus.] - Event bus ready
10:41:20.939 INFO [NodeServer.createHandlers] - Reporting self as: http://192.168.1.144:5557
10:41:20.949 INFO [NodeOptions.getSessionFactories] - Detected 10 available processors
10:41:20.958 INFO [RelayOptions.getSessionFactories] - Adding relay configs for http://localhost:4723
10:41:20.963 INFO [RelayOptions.lambda$getSessionFactories$1] - Mapping Capabilities {appium:automationName: UiAutomator2, appium:deviceName: Pixar 5а, appium:platformVersion: 13, platformName: ANDROID}, 1 times
10:41:20.963 INFO [RelayOptions.lambda$getSessionFactories$1] - Mapping Capabilities {appium:automationName: UiAutomator2, appium:deviceName: Pixar 4, appium:platformVersion: 13, platformName: ANDROID}, 1 times
10:41:20.987 INFO [Node.] - Binding additional locator mechanisms: relative
10:41:21.064 INFO [NodeServer$1.start] - Starting registration process for Node http://192.168.1.144:5557
10:41:21.065 INFO [NodeServer.execute] - Started Selenium node 4.13.0 (revision ba948ec*): http://192.168.1.144:5557
10:41:21.233 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
10:41:21.259 INFO [NodeServer.lambda$createHandlers$2] - Node has been added