http://selenium-hub:4444/grid/register is not working

Question

http://selenium-hub:4444/grid/register is not working

maaixprt opened this issue 5 years ago · 1 comments

Describe the bug
http://selenium-hub:4444/grid/register unable to access in the brwoser.

To Reproduce
Steps to reproduce the behavior:

Go to Browser and try to access http://selenium-hub:4444/grid/register
Click on '....'
Scroll down to '....'
See error:

Hmm. We’re having trouble finding that site.

We can’t connect to the server at selenium-hub.

If that address is correct, here are three other things you can try:

    Try again later.
    Check your network connection.
    If you are connected but behind a firewall, check that Firefox has permission to access the Web.

Expected behavior
url should access with selenium server

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]: Linux Ubuntu 18.*
Browser [e.g. chrome, safari] firefox
Version [e.g. 22] : 71.0 (64-bit

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Here is logs:


SeleniumDemo/docker/selenium$ sudo docker-compose up 
[sudo] password for aixprt: 
Creating network "selenium_default" with the default driver
Pulling firefox (selenium/node-firefox-debug:latest)...
latest: Pulling from selenium/node-firefox-debug
7ddbc47eeb70: Already exists
c1bbdc448b72: Already exists
8c3b70e39044: Already exists
45d437916d57: Already exists
29c0b8a44c93: Already exists
c9aa98866ffb: Already exists
6584a4b691b2: Already exists
842fb67ea81b: Already exists
758108596d08: Already exists
dff828979cf3: Already exists
18e9721273f4: Already exists
9e553a64ecfd: Already exists
9eb2588dfeab: Already exists
c5e5810e287c: Already exists
529de0265d85: Already exists
2e7d7ae8994e: Already exists
8af760dc5257: Already exists
c5c25483247a: Already exists
63a7b9c279ad: Already exists
9c62b5746687: Already exists
bde50510f08f: Already exists
7d7e913d90e5: Already exists
3c619c712a6e: Pull complete
89360bbe017d: Pull complete
06b2284bb704: Pull complete
d8d887324a20: Pull complete
ec4c822b8265: Pull complete
4f6891e6a116: Pull complete
Creating selenium-hub ... done
Creating selenium_chrome_1_b4d980f4319b  ... done
Creating selenium_firefox_1_ca368c866529 ... done
Attaching to selenium-hub, selenium_chrome_1_c4c693f43863, selenium_firefox_1_28d7809b4165
selenium-hub    | 2019-12-16 13:48:56,649 INFO Included extra file "/etc/supervisor/conf.d/selenium-hub.conf" during parsing
selenium-hub    | 2019-12-16 13:48:56,651 INFO supervisord started with pid 7
chrome_1_c4c693f43863 | 2019-12-16 13:48:57,200 INFO Included extra file "/etc/supervisor/conf.d/selenium-debug.conf" during parsing
chrome_1_c4c693f43863 | 2019-12-16 13:48:57,200 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
chrome_1_c4c693f43863 | 2019-12-16 13:48:57,202 INFO supervisord started with pid 10
firefox_1_28d7809b4165 | 2019-12-16 13:48:57,273 INFO Included extra file "/etc/supervisor/conf.d/selenium-debug.conf" during parsing
firefox_1_28d7809b4165 | 2019-12-16 13:48:57,274 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
firefox_1_28d7809b4165 | 2019-12-16 13:48:57,275 INFO supervisord started with pid 8
selenium-hub    | 2019-12-16 13:48:57,657 INFO spawned: 'selenium-hub' with pid 10
selenium-hub    | Starting Selenium Hub with configuration:
selenium-hub    | 2019-12-16 13:48:57,665 INFO success: selenium-hub entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
selenium-hub    | {
selenium-hub    |   "host": "0.0.0.0",
selenium-hub    |   "port": 4444,
selenium-hub    |   "role": "hub",
selenium-hub    |   "maxSession": 5,
selenium-hub    |   "newSessionWaitTimeout": -1,
selenium-hub    |   "capabilityMatcher": "org.openqa.grid.internal.utils.DefaultCapabilityMatcher",
selenium-hub    |   "throwOnCapabilityNotPresent": true,
selenium-hub    |   "jettyMaxThreads": -1,
selenium-hub    |   "cleanUpCycle": 5000,
selenium-hub    |   "browserTimeout": 0,
selenium-hub    |   "timeout": 1800,
selenium-hub    |   "debug": false
selenium-hub    | }
selenium-hub    | 13:48:57.829 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
selenium-hub    | 13:48:57.905 INFO [GridLauncherV3.lambda$buildLaunchers$5] - Launching Selenium Grid hub on port 4444
chrome_1_c4c693f43863 | 2019-12-16 13:48:58,203 INFO spawned: 'xvfb' with pid 13
chrome_1_c4c693f43863 | 2019-12-16 13:48:58,205 INFO spawned: 'fluxbox' with pid 14
chrome_1_c4c693f43863 | 2019-12-16 13:48:58,206 INFO spawned: 'vnc' with pid 15
chrome_1_c4c693f43863 | 2019-12-16 13:48:58,208 INFO spawned: 'selenium-node' with pid 17
chrome_1_c4c693f43863 | 2019-12-16 13:48:58,257 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
chrome_1_c4c693f43863 | 2019-12-16 13:48:58,257 INFO success: fluxbox entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
chrome_1_c4c693f43863 | 2019-12-16 13:48:58,257 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
chrome_1_c4c693f43863 | 2019-12-16 13:48:58,257 INFO success: selenium-node entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
selenium-hub    | 2019-12-16 13:48:58.268:INFO::main: Logging initialized @598ms to org.seleniumhq.jetty9.util.log.StdErrLog
chrome_1_c4c693f43863 | Connecting to the Hub using the host selenium-hub and port 4444
firefox_1_28d7809b4165 | 2019-12-16 13:48:58,278 INFO spawned: 'xvfb' with pid 11
firefox_1_28d7809b4165 | 2019-12-16 13:48:58,280 INFO spawned: 'fluxbox' with pid 12
firefox_1_28d7809b4165 | 2019-12-16 13:48:58,282 INFO spawned: 'vnc' with pid 13
firefox_1_28d7809b4165 | 2019-12-16 13:48:58,284 INFO spawned: 'selenium-node' with pid 15
firefox_1_28d7809b4165 | 2019-12-16 13:48:58,338 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
firefox_1_28d7809b4165 | 2019-12-16 13:48:58,338 INFO success: fluxbox entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
firefox_1_28d7809b4165 | 2019-12-16 13:48:58,338 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
firefox_1_28d7809b4165 | 2019-12-16 13:48:58,338 INFO success: selenium-node entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
firefox_1_28d7809b4165 | Connecting to the Hub using the host selenium-hub and port 4444
selenium-hub    | 13:48:58.527 INFO [Hub.start] - Selenium Grid hub is up and running
selenium-hub    | 13:48:58.528 INFO [Hub.start] - Nodes should register to http://172.31.0.2:4444/grid/register/
selenium-hub    | 13:48:58.529 INFO [Hub.start] - Clients should connect to http://172.31.0.2:4444/wd/hub
chrome_1_c4c693f43863 | 13:48:58.544 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
firefox_1_28d7809b4165 | 13:48:58.614 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358
chrome_1_c4c693f43863 | 13:48:58.636 INFO [GridLauncherV3.lambda$buildLaunchers$7] - Launching a Selenium Grid node on port 5555
firefox_1_28d7809b4165 | 13:48:58.703 INFO [GridLauncherV3.lambda$buildLaunchers$7] - Launching a Selenium Grid node on port 5555
chrome_1_c4c693f43863 | 2019-12-16 13:48:58.714:INFO::main: Logging initialized @434ms to org.seleniumhq.jetty9.util.log.StdErrLog
firefox_1_28d7809b4165 | 2019-12-16 13:48:58.773:INFO::main: Logging initialized @386ms to org.seleniumhq.jetty9.util.log.StdErrLog
chrome_1_c4c693f43863 | 13:48:58.875 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
firefox_1_28d7809b4165 | 13:48:58.953 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
chrome_1_c4c693f43863 | 13:48:58.954 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 5555
chrome_1_c4c693f43863 | 13:48:58.954 INFO [GridLauncherV3.lambda$buildLaunchers$7] - Selenium Grid node is up and ready to register to the hub
chrome_1_c4c693f43863 | 13:48:58.994 INFO [SelfRegisteringRemote$1.run] - Starting auto registration thread. Will try to register every 5000 ms.
firefox_1_28d7809b4165 | 13:48:59.037 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 5555
firefox_1_28d7809b4165 | 13:48:59.037 INFO [GridLauncherV3.lambda$buildLaunchers$7] - Selenium Grid node is up and ready to register to the hub
firefox_1_28d7809b4165 | 13:48:59.076 INFO [SelfRegisteringRemote$1.run] - Starting auto registration thread. Will try to register every 5000 ms.
firefox_1_28d7809b4165 | 13:48:59.314 INFO [SelfRegisteringRemote.registerToHub] - Registering the node to the hub: http://selenium-hub:4444/grid/register
chrome_1_c4c693f43863 | 13:48:59.315 INFO [SelfRegisteringRemote.registerToHub] - Registering the node to the hub: http://selenium-hub:4444/grid/register
selenium-hub    | 13:48:59.361 INFO [DefaultGridRegistry.add] - Registered a node http://172.31.0.3:5555
chrome_1_c4c693f43863 | 13:48:59.361 INFO [SelfRegisteringRemote.registerToHub] - The node is registered to the hub and ready to use
selenium-hub    | 13:48:59.361 INFO [DefaultGridRegistry.add] - Registered a node http://172.31.0.4:5555
firefox_1_28d7809b4165 | 13:48:59.362 INFO [SelfRegisteringRemote.registerToHub] - The node is registered to the hub and ready to use

Answer 1 · 2019-12-19T09:04:58.000Z

Try http://localhost:4444/grid/register