Chrome not reachable Exception with chromedriver2.6, Selenium Server 2.37, Win 7

[Satya]

Hi,

I am getting "Chrome not reachable" exception when i migrated to new win 7 virtual machines.

Configuration:

ChromeDriver - 2.6

SeleniumServer - 2.37

OS - Win 7 64Bit / 32Bit

chrome browser is invoking but not communicating with the opened window.

Regards,

Sathya

[aditya charan]

Sathya,

Can you post the exact error stack that you are seeing. How are you contacting the Virtual machine?

Thanks.

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To post to this group, send email to seleniu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/c2358e15-05ed-42ef-a6e9-2b0923bc2924%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Satya]

Hi,

I am able to run the same test on IE and FirFox browsers successfully. but on Chrome getting following error message.

org.openqa.selenium.WebDriverException: chrome not reachable

  (Driver info: chromedriver=2.6.232923,platform=Windows NT 6.1 SP1 x86) (WARNING: The server did not provide any stacktrace information)

Command duration or timeout: 20.82 seconds

Build info: version: '2.33.0', revision: '4e90c97', time: '2013-05-22 15:32:38'

System info: os.name: 'Windows 7', os.arch: 'x86', os.version: '6.1', java.version: '1.6.0_25'

Driver info: org.openqa.selenium.chrome.ChromeDriver

Command duration or timeout: 25.70 seconds

Build info: version: '2.33.0', revision: '4e90c97', time: '2013-05-22 15:32:38'

System info: os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version: '1.6.0_25'

Driver info: org.openqa.selenium.remote.RemoteWebDriver

[aditya charan]

Satya,

What is the chromedriver version is that v1.0 or 2.0? if its v1.0, please upgrade it and give it a try.

Thanks

Aditya
901029657

To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/feb3228e-a00f-406e-b38d-143fdc4b97bc%40googlegroups.com.

[aditya charan]

Satya,

I was looking on net for support/solution for your issue and found that may be the ChromeDriver is not bypassing the proxy settings.

Try below one :

In Internet Properties->connections->LAN settings, set 'Bypass proxy server for local addresses'?

Hope this should resolve your issue.

Thanks.

To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/feb3228e-a00f-406e-b38d-143fdc4b97bc%40googlegroups.com.

[Dar Ko]

This  Control Panel\All Control Panel Items\Network and Sharing Center\Internet Options\Connections\LAN settings\Bypass proxy server for local addresses  option works fine for me...

[Prasad Nutalapati]

In our Selenium remote webdriver set up, we wrote our Selenium Java test scripts for to run in Chrome Browser. We are using Chrome Driver 2.28. Selenium Standalone Server 2.53. Selenium API 2.53. When we run our scripts from with in Eclipse IDE, 3 out of 5 times, the Chrome browser does not get invoked or take a long time to start by the script. When it fails to invoke the browser, it fails with this exception ....

Caused by: org.openqa.selenium.WebDriverException: chrome not reachable

  (Driver info: chromedriver=2.28.455520 (cc17746adff54984afff480136733114c6b3704b),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)

Command duration or timeout: 60.83 seconds

Build info: version: '2.53.0', revision: '35ae25b', time: '2016-03-15 17:00:58'

System info: host: 'LCHI093234-7', ip: '10.34.1.60', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_121'

Driver info: org.openqa.selenium.chrome.ChromeDriver

        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

        at java.lang.reflect.Constructor.newInstance(Constructor.java:423)

        at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206)

        at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158)

        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:678)

        at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:249)

        at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:131)

        at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:144)

        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:170)

        at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:138)

        ... 14 more

12:40:44.570 WARN - Exception: chrome not reachable

  (Driver info: chromedriver=2.28.455520 (cc17746adff54984afff480136733114c6b3704b),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)

Command duration or timeout: 60.83 seconds

Build info: version: '2.53.0', revision: '35ae25b', time: '2016-03-15 17:00:58'

System info: host: 'LCHI093234-7', ip: '10.34.1.60', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_121'

Driver info: org.openqa.selenium.chrome.ChromeDriver

The temporary but painful solution is to go to Windows TaskManager and kill the half a dozen or so, Chrome.exe processes one after another. It is observed that even when we run our script or manually running the application, the Chrome browser processes that get invoked are more like 6 or 7, not less.

Is it a Chrome Browser or Selenium issue. ? Individually, I used NOT to have this problem unlike my team member who is having this problem since a year. As soon as I upgraded Chrome Driver to 2.28 from 2.25, I started having this problem.

[Mikhail Ramendik]

On Friday, April 14, 2017 at 12:51:40 PM UTC+1, Prasad Nutalapati wrote:

Is it a Chrome Browser or Selenium issue. ? Individually, I used NOT to have this problem unlike my team member who is having this problem since a year. As soon as I upgraded Chrome Driver to 2.28 from 2.25, I started having this problem.

Just in case, please ensure your Chrome is the latest version. Chrome Driver 2.28 was updated specifically for Chrome 57. I am not saying this IS your problem - I am only saying this is worth a look.

[Prasad Nutalapati]

Hi:

 

We are at Chrome Browser Version 57.0.2987.133 (64-bit)

Chrome Driver 2.28

Selenium Standalone Server 2.53.

 

I think this means I am doing fine.

 

 

 

Thanks,

 

 

 

[Prasad Nutalapati]