SeleniumHQ / SeleniumHQ/docker-selenium

[🐛 Bug]: can't access 4444

Open
#2,774 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs-triaging
Dominant language
Go
Stars
8.7k
Forks
2.5k
Avg merge
10h 16m
Merged PRs (30d)
20

Description

What happened?

can't access 4444 via host

Command used to start Selenium Grid with Docker (or Kubernetes)
docker run -d  -p 4444:4444 -p 5900:5900 -p 7900:7900 --shm-size 2g selenium/standalone-chromium:125.0-chromedriver-125.0-20240522
Relevant log output
[root@master noah-bi-server]# docker run -d  -p 4444:4444 -p 5900:5900 -p 7900:7900 --shm-size 2g selenium/standalone-chromium:125.0-chromedriver-125.0-20240522
dbea0618c5ad814a118ab7f5bc01eac8d65866fa5bead41ad36e79b119c8aae9
[root@master noah-bi-server]# docker logs -f dbea0618c5ad814a118ab7f5bc01eac8d65866fa5bead41ad36e79b119c8aae9
2025-04-10 08:07:57,163 INFO Included extra file "/etc/supervisor/conf.d/chrome-cleanup.conf" during parsing
2025-04-10 08:07:57,164 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
2025-04-10 08:07:57,214 INFO RPC interface 'supervisor' initialized
2025-04-10 08:07:57,214 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2025-04-10 08:07:57,215 INFO supervisord started with pid 8
2025-04-10 08:07:58,220 INFO spawned: 'xvfb' with pid 9
2025-04-10 08:07:58,224 INFO spawned: 'vnc' with pid 10
2025-04-10 08:07:58,229 INFO spawned: 'novnc' with pid 11
2025-04-10 08:07:58,233 INFO spawned: 'selenium-standalone' with pid 14
2025-04-10 08:07:58,240 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-04-10 08:07:58,241 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-04-10 08:07:58,241 INFO success: novnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-04-10 08:07:58,241 INFO success: selenium-standalone entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
^C
[root@master noah-bi-server]# curl -v http://localhost:4444/wd/hub/status
*   Trying 127.0.0.1:4444...
* Connected to localhost (127.0.0.1) port 4444 (#0)
> GET /wd/hub/status HTTP/1.1
> Host: localhost:4444
> User-Agent: curl/7.71.1
> Accept: */*
>
* Recv failure: 连接被对方重设
* Closing connection 0
curl: (56) Recv failure: 连接被对方重设
[root@master noah-bi-server]#
Operating System

Linux master 4.19.90-83.0.v2307.ky10.aarch64 #1 SMP Wed Oct 18 15:36:43 CST 2023 aarch64 aarch64 aarch64 GNU/Linux

Docker Selenium version (image tag)

selenium/standalone-chromium:125.0-chromedriver-125.0-20240522

Selenium Grid chart version (chart version)

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported docker run command on the listed Linux aarch64 host with image tag 125.0-chromedriver-125.0-20240522. Compare the container startup logs with the curl request to /wd/hub/status on port 4444, then inspect the image's Selenium startup configuration. Done means identifying the cause of the connection reset and documenting or validating a supported resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.