[🐛 Bug]: Using selenium/node-chrome: 142 image and configuring noVNC in Docker compose. However, it is not possible to manually open a visual Chrome browser in noVNC, but the same configuration can be manually opened in selenium/nod-chrome: 134

[1betty2]

What happened?

Using selenium/node-chrome: 142 image and configuring noVNC in Docker compose. However, it is not possible to manually open a visual Chrome browser in noVNC, but the same configuration can be manually opened in selenium/nod-chrome: 134

docker-compose.yml using selenium/node-chrome:134
`services:
selenium-hub2:
container_name: hub2
image: selenium/hub:4.39
ports:
- "4446:4442"
- "4447:4443"
- "4445:4444"
restart: unless-stopped # Set automatic restart

selenium-node41:
container_name: chrome_41
environment:
- SE_EVENT_BUS_HOST=192.168.1.61
- SE_EVENT_BUS_PUBLISH_PORT=4446
- SE_EVENT_BUS_SUBSCRIBE_PORT=4447
- HUB_HOST=192.168.1.61
- HUB_PORT=4445
- SE_NODE_HOST=192.168.12.114
- SE_NODE_PORT=10041
- SE_START_VNC=true
- SE_NODE_VNC_ENABLED=true
- SE_NODE_VNC_PORT=7841
- SE_NODE_VNC_RESOLUTION=2080X19200
- SCREEN_WIDTH=1360
- SCREEN_HEIGHT=1020
- SE_VNC_LOCAL_SCALING=true
- SE_VNC_NO_PASSWORD=true
- SE_NODE_MAX_INSTANCES=2
- SE_NODE_MAX_SESSIONS=1
- SE_NODE_STEREOTYPE={"browserName":"chrome","browserVersion":"142.0","platformName":"Linux","nodename:applicationName":"chrome_41","networkname:applicationName":"chrome_41","goog:chromeOptions":{"binary":"/usr/bin/google-chrome"}}
image: selenium_node_all_in_one
ports:
- 192.168.12.114:10041:10041
- 192.168.12.114:7841:7900
shm_size: 2gb
volumes:
- /media/viu/VIUAUTOQA2T/web_screen_records:/media
- /home/web_farm/docker/mitmproxy-ca-cert.crt:/usr/local/share/ca-certificates/mitmproxy-ca-cert.crt`

Using selenium/node chrome: 134 image to open the interface in noVNC:

docker-compose.yml using selenium/node-chrome:142
`services:
selenium-hub:
container_name: hub
image: selenium/hub:4.39
ports:
- "4442:4442"
- "4443:4443"
- "4444:4444"
restart: unless-stopped # Set automatic restart

selenium-node1:
container_name: chrome_01
depends_on:
- selenium-hub
environment:
- SE_EVENT_BUS_HOST=selenium-hub
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
- HUB_HOST=selenium-hub
- HUB_PORT=4444
- SE_NODE_HOST=192.168.12.114
- SE_NODE_PORT=10001
- SE_NODE_VNC_ENABLED=true
- SE_NODE_VNC_PORT=7801
- SE_NODE_VNC_RESOLUTION=1920X1080
- SCREEN_WIDTH=1360
- SCREEN_HEIGHT=1020
- SE_VNC_LOCAL_SCALING=true
- SE_VNC_NO_PASSWORD=true
- SE_NODE_MAX_INSTANCES=2
- SE_NODE_MAX_SESSIONS=1
- SE_NODE_STEREOTYPE={"browserName":"chrome","browserVersion":"142.0","platformName":"Linux","nodename:applicationName":"chrome_01","networkname:applicationName":"chrome_01","goog:chromeOptions":{"binary":"/usr/bin/google-chrome"}}
image: selenium_node142.0_web_test_20251211
ports:
- 192.168.12.114:10001:10001
- 192.168.12.114:7801:7900
shm_size: 2gb
volumes:
- /media/viu/VIUAUTOQA2T/web_screen_records:/media
- /home/web_farm/docker/mitmproxy-ca-cert.crt:/usr/local/share/ca-certificates/mitmproxy-ca-cert.crt`

Using selenium/node chrome: 142 image to open the interface in noVNC:

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

Command used to start Selenium Grid: docker compose up -d

Relevant log output

logs for selenium/node-chrome:134:
Setting up SE_NODE_GRID_URL...
Appending Selenium option: --tracing false
Tracing is disabled
Appending Selenium option: --bind-host false
Appending Selenium option: --config /opt/selenium/config.toml
Selenium Grid Node configuration: 
[events]
    publish = "tcp://192.168.1.61:4446"
    subscribe = "tcp://192.168.1.61:4447"
    
[server]
host = "192.168.12.114"
port = "10041"
[node]
session-timeout = 300
override-max-sessions = false
detect-drivers = false
drain-after-session-count = 0
max-sessions = 1

[[node.driver-configuration]]
display-name = "chrome"
stereotype = '{"browserName":"chrome","browserVersion":"142.0","platformName":"Linux","nodename:applicationName":"chrome_41","networkname:applicationName":"chrome_41","goog:chromeOptions":{"binary":"/usr/bin/google-chrome"}}'
max-sessions = 1
    
Starting Selenium Grid Node...
Using JAVA_OPTS:  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
06:21:01.677 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
06:21:01.682 INFO [LoggingOptions.getTracer] - Using null tracer
06:21:01.726 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://192.168.1.61:4446 and tcp://192.168.1.61:4447
06:21:01.762 INFO [UnboundZmqEventBus.<init>] - Sockets created
2025-12-23 06:21:02,240 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-12-23 06:21:02,240 INFO success: vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-12-23 06:21:02,240 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
06:21:02.764 INFO [UnboundZmqEventBus.<init>] - Event bus ready
06:21:02.876 INFO [NodeServer.createHandlers] - Reporting self as: http://192.168.12.114:10041
06:21:02.879 INFO [LoggingOptions.getTracer] - Using null tracer
06:21:02.897 INFO [NodeOptions.getSessionFactories] - Detected 20 available processors
06:21:02.926 INFO [NodeOptions.report] - Adding chrome for {"browserName": "chrome","browserVersion": "142.0","goog:chromeOptions": {"binary": "\u002fusr\u002fbin\u002fgoogle-chrome"},"networkname:applicationName": "chrome_41","nodename:applicationName": "chrome_41","platformName": "linux","se:noVncPort": 7900,"se:vncEnabled": true} 1 times
06:21:02.944 INFO [Node.<init>] - Binding additional locator mechanisms: relative
06:21:03.047 INFO [NodeServer$2.start] - Starting registration process for Node http://192.168.12.114:10041
06:21:03.048 INFO [NodeServer.execute] - Started Selenium node 4.30.0 (revision 509c7f1): http://192.168.12.114:10041
06:21:03.055 INFO [NodeServer$2.lambda$start$2] - Sending registration event...
06:21:03.115 INFO [NodeServer.lambda$createHandlers$2] - Node has been added



=====================================

logs for selenium/node-chrome:142:
Selenium Grid Node configuration: 
[events]
    publish = "tcp://selenium-hub:4442"
    subscribe = "tcp://selenium-hub:4443"
    
[server]
host = "192.168.12.114"
port = "10001"
[node]
session-timeout = 300
override-max-sessions = false
max-sessions = 1
detect-drivers = false
drain-after-session-count = 0

[[node.driver-configuration]]
display-name = "chrome"
stereotype = '{"browserName":"chrome","browserVersion":"142.0","platformName":"Linux","nodename:applicationName":"chrome_01","networkname:applicationName":"chrome_01","goog:chromeOptions":{"binary":"/usr/bin/google-chrome"}}'
max-sessions = 1

Starting Selenium Grid Node...
Using JAVA_OPTS:  -Dwebdriver.remote.enableTracing=false -Dwebdriver.httpclient.version=HTTP_1_1
2025-12-23 06:15:49,145 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-12-23 06:15:49,145 INFO success: vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-12-23 06:15:49,145 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
06:15:49.219 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
06:15:49.226 INFO [LoggingOptions.getTracer] - Using null tracer
06:15:49.272 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://selenium-hub:4442 and tcp://selenium-hub:4443
06:15:49.304 INFO [ZmqUtils.configureHeartbeat] - ZMQ SUB socket heartbeat configured: interval=60s, timeout=180s, ttl=360s
06:15:49.310 INFO [ZmqUtils.configureHeartbeat] - ZMQ PUB socket heartbeat configured: interval=60s, timeout=180s, ttl=360s
06:15:49.312 INFO [UnboundZmqEventBus.<init>] - Sockets created
06:15:50.313 INFO [UnboundZmqEventBus.<init>] - Event bus ready
06:15:50.654 INFO [NodeServer.createHandlers] - Reporting self as: http://192.168.12.114:10001
06:15:50.660 INFO [LoggingOptions.getTracer] - Using null tracer
06:15:50.700 INFO [NodeOptions.getSessionFactories] - Detected 20 available processors
06:15:50.821 INFO [NodeOptions.report] - Adding chrome for {"browserName": "chrome","browserVersion": "142.0","goog:chromeOptions": {"binary": "\u002fusr\u002fbin\u002fgoogle-chrome"},"networkname:applicationName": "chrome_01","nodename:applicationName": "chrome_01","platformName": "linux","se:deleteSessionOnUi": true,"se:downloadsEnabled": true,"se:noVncPort": 7900,"se:vncEnabled": true} 1 times
06:15:50.887 INFO [Node.<init>] - Binding additional locator mechanisms: relative
06:15:51.143 INFO [NodeServer$2.start] - Starting registration process for Node http://192.168.12.114:10001
06:15:51.145 INFO [NodeServer.execute] - Started Selenium node 4.38.0 (revision 6b412e825c): http://192.168.12.114:10001
06:15:51.159 INFO [NodeServer$2.lambda$start$2] - Sending registration event...
06:15:52.101 INFO [NodeServer.lambda$createHandlers$2] - Node has been added

Operating System

Ubuntu 24.04.3 LTS Release: 24.04 Codename: noble

Docker Selenium version (image tag)

Selenium Grid 4.39.0 (revision 126f156aee)

Selenium Grid chart version (chart version)

No response

[github-actions]

@1betty2, 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!

[1betty2]

Hello team,any updates on this issue , and If you need me to provide more information, please let me know,Thanks