ECONNRESET. Is selenium server started?
See original GitHub issueI get this now when try to run Nightwatch. It seemed to begin suddenly and I’ve got it to run successfully a few times since it started too.
username@hostname ~/D/d/mysite-frontend> npm run e2e
> mysite-frontend@0.0.1 e2e /Users/username/Documents/dev/mysite-frontend
> ./node_modules/nightwatch/bin/nightwatch -c nightwatch.conf.js
Starting selenium server... started - PID:  1376
started - PID:  1376
[Homepage] Test Suite
=========================
Running:  Open login modal
[client :: capabilities] Test Suite
=======================================
Error retrieving a new session from the selenium server
Connection refused! Is selenium server started?
{ [Error: socket hang up] code: 'ECONNRESET' }
I’ve deleted and redownloaded selenium.jar and a few other things, but same error.
Issue Analytics
- State:
 - Created 7 years ago
 - Comments:29 (5 by maintainers)
 
Top Results From Across the Web
socket hang up" when mouse down on draggable DIV
ChromeDriver 76.0.3809.126 - moveto request fails "ECONNRESET Error: socket ... My new project uses the latest versions of Nightwatch, Selenium Server and ...
Read more >ECONNRESET. Is selenium server started? - Bountysource
I get this now when try to run Nightwatch. It seemed to begin suddenly and I've got it to run successfully a few...
Read more >Nightwatch Selenium "socket hang up" - Stack Overflow
I tried downgrading selenium to 2.53.1 to no avail. Verbose logging showed no helpful info, just the selenium server suddenly not starting new ......
Read more >Common Selenium and Webdriverio Error Messages SOLVED
This error is thrown when WebdriverIO tries to send an HTTP request to the default Selenium server location. The request to that location...
Read more >npm install - read ECONNRESET - Visual Studio Feedback
Since today, we start a getting an issue with npm install webdriver-manager on Windows runners, all others npm works. Azure DevOpsAzure DevOpsrepos.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Adding “headless” to the chrome args did it for me on our linux ci box.
chromeOptions: { args: [ 'headless', 'no-sandbox'] }I solved it by reinstalling the chrome driver:
npm i chromedriver --save