[GH-ISSUE #212] Not able to connect to selenium grid - getting connection refused error. #153

New issue

Closed

opened 2026-03-01 15:40:57 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 15:40:57 +03:00

Owner

Originally created by @qburst-hari on GitHub (Nov 25, 2019).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/212

I started a selenium hub with the command -

docker run -d -p 4444:4444 --name selenium-android-hub -P selenium/hub

Then I started the appium docker command -

docker run --privileged -d -p 6080:6080 -p 4723:4723 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" -e APPIUM=true -e CONNECT_TO_GRID=true -e APPIUM_HOST="127.0.0.1" -e APPIUM_PORT=4723 -e SELENIUM_HOST="127.0.0.1" -e SELENIUM_PORT=4444 -e MOBILE_WEB_TEST=true --name android-container budtmo/docker-android-x86-8.1

But when I accessed noVNC, in logs it says

[Appium] Request to register with grid was unsuccessful:Error: connect ECONNREFUSED 127.0.0.1:4444
[debug][Appium] Hub down or not responding:Error: connect ECONNREFUSED 127.0.0.1:4444

Please let me know whats the issue is ?

With the same hub, I was able to add normal chrome borwser nodes.

Originally created by @qburst-hari on GitHub (Nov 25, 2019). Original GitHub issue: https://github.com/budtmo/docker-android/issues/212 I started a selenium hub with the command - > `docker run -d -p 4444:4444 --name selenium-android-hub -P selenium/hub` Then I started the appium docker command - > `docker run --privileged -d -p 6080:6080 -p 4723:4723 -p 5554:5554 -p 5555:5555 -e DEVICE="Samsung Galaxy S6" -e APPIUM=true -e CONNECT_TO_GRID=true -e APPIUM_HOST="127.0.0.1" -e APPIUM_PORT=4723 -e SELENIUM_HOST="127.0.0.1" -e SELENIUM_PORT=4444 -e MOBILE_WEB_TEST=true --name android-container budtmo/docker-android-x86-8.1` But when I accessed noVNC, in logs it says > [Appium] Request to register with grid was unsuccessful:Error: connect ECONNREFUSED 127.0.0.1:4444 > [debug][Appium] Hub down or not responding:Error: connect ECONNREFUSED 127.0.0.1:4444 Please let me know whats the issue is ? With the same hub, I was able to add normal chrome borwser nodes.