My setup includes:
- Operating System: Windows 10 (64 bit)
- Browser: Chrome version 58
- Node.js: 6.10.1
- Npm: 3.10.10
- Chromedriver: 2.29.0
After running my tests with Chrome using Selenium standalone, I encountered an error in the console where Selenium was launched:
Caused by: org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start.
Build info: version: '3.4.0', revision: 'unknown', time: 'unknown'
os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_131'
Driver info: driver.version: ChromeDriver
at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:193)
...
Caused by: org.openqa.selenium.net.UrlChecker$TimeoutException: Timed out waiting for [http://localhost:41643/status] to be available after 20002 ms
Furthermore, when I tried to access 27.0.0.1:4444 in the browser after opening Selenium standalone and loading the page, I received the following error in the console:
chrome
Error: connect ECONNREFUSED 127.0.0.1:4444
I have attempted switching between different versions of Node.js and npm, as well as using webdriver-manager instead of the selenium-standalone server, but the issue persists.
Interestingly, when I switch from Firefox to Chrome, the FF browser actually opens...
Previously, everything worked smoothly with Chrome until it suddenly stopped working. The current configurations match those of another team member who did not encounter this problem originally.