Selenium + FF : How to fix error, Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms?

Question

My script is not running even by using selenium 2.53.1 and firefox 47.0.1. Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. is the error returned.

The script that was tried is,

package SystemPackTest; 
import org.openqa.selenium.WebDriver; 
import org.openqa.selenium.firefox.FirefoxDriver; 
public class TestCalass { 
    public static void main(String[] args) { 
        WebDriver driver ;
        System.setProperty("webdriver.gecko.driver", "<geckodriver path>");
        driver = new FirefoxDriver(); 
        driver.get("google.com"); 
        System.out.println("Successfully opened the website"); 
        //driver.close(); 
    } 
} 

Question - How to fix error, Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms?

Answer 1

Solution 1 -

I will suggest to downgrade (replace with older version) your ff browser version. You are unable to connect to 127.0.0.1 maybe because version do not support each other.

Upgrade or downgrade version for Selenium or FF will resolve issue.

Note - Prefer to downgrade FF version, I got success with such approach.

Solution 2 - Try running this before you start your Selenium server:

export DISPLAY=:0

DISPLAY is essentially an environment variable which needs to be exported from the command line.

Answer 2

Scenarios :

1. As per Selenium Webdriver 3.0 Documentation and Geckodriver Configuration Document,

   Selenium 3.0 and higher version require Java8 and Firefox 46,47+ versions.

Note : Here you require to use geckodriver

2. For Selenium Webdriver 2.53.1 and Lesser version,

   Require lesser version from Firefox 45 and Java7

Note : Here only WebDriver driver = new FirefoxDriver(); will work perfectly.

Please configure system as per above combination and verify your script.

As per given comments, Answer is scenario 2.

Answer 3

In my case just now the issue was that I was passing a prepared profile dir that obviously appeared absent/invalid when I switched from MacOS to Windows node.

Yeah, it was impossible to figure this out by just reading the node/hub stderr.