seleniumselenium-webdriverselenium-gridwindows-firewallselenium-server

Selenium Server: Marking the node http://172.294.80.80:5566 as down: cannot reach the node for 2 tries

Marking the node http://169.254.80.80:5566 as down: cannot reach the node for 2 tries.

I thought this might be a security/port issue so I opened the ports 4444 and 5566 and told the firewall to allow connections from selenium-server-standalone-3.141.59.jar. However, Selenium Grid hub still "marks the node as down: cannot reach the node for 2 tries".

This happens for both selenium-server-standalone-3.141.59.jar and selenium-server-standalone-3.12.0.jar.

Question: Why is Selenium Grid Hub producing the "Marks the node as down: cannot reach the node for 2 tries"? I am running both the Hub and Node on the same machine. I am guessing this is okay.

I did find a similar post but not exactly the same error message and the answer looks like it was a typo. Similar Stack Overflow post

Figure 1: Messages from Selenium Grid Hub and Selenium Server Node output from selenium grid hub and node

Figure 2: Allowing connections to/from port 4444 Allowing connections to/from port 4444

Figure 3: Allowing Selenium Server through firewall Allowing Selenium Server through firewall

Figure 4: Allowing connections to/from port 5566 enter image description here

Solution

  • I was using an old version of Selenium Server.

    Lastest Versions of Selenium Projects/Products can be found here: lastest version of Selenium Projects

    Was eventually able to find a similar post about the issue here: node not registering in earlier versions of Selenium Server

    Description of Complete Fix (that worked for me):

    1. Upgrade Selenium to 3.5. Note-1: don't rely on Nuget package manager in VS to tell you what the most recent package is. The Nuget package manager (UI) thinks 3.141 is the most recent when it is actually 3.5. Note-2: looks like DebanjanB was able to get 1.141 Selenium Server connected without issues so not required to upgrade to 3.5.
    2. Disconnected from Cisco AnyConnect
    3. Run the hub: open cmd and type java -jar selenium-server-standalone-3.5.0.jar -role hub
    4. Run the node: open cmd and type, java -Dwebdriver.chrome.driver=C:\RepoTests\WebDrivers\chromedriver.exe -Dwebdriver.gecko.driver=C:\RepoTests\WebDrivers\geckodriver.exe -Dwebdriver.edge.driver=C:\RepoTests\WebDrivers\MicrosoftWebDriver.exe -jar selenium-server-standalone-3.5.0.jar -role node -hub http://localhost:4444/grid/register -browser "browserName=chrome,version=66.0,maxInstances=5,seleniumProtocol=WebDriver" -browser "browserName=firefox,version=60.0.1,maxInstances=5,seleniumProtocol=WebDriver" -browser "browserName=MicrosoftEdge,version=10.0,maxInstances=5,seleniumProtocol=WebDriver"

    Note-1: I did NOT have to create any inbound or outbound firewall rules (as described in the original question) since the node connected to the hub using 'http://localhost:4444/..'.

    Note-2: Was not able to get node to connect to hub with the actual IP address as suggested by DebanjanB. Will need to figure this out eventually. Will post if figure out.