Error: read ECONNRESET with fresh npm install
See original GitHub issueI have installed Cypress using npm to an angular 9.0 project. I can start cypress using npx cypress open and upon selecting any of the example tests the chrome browser opens for a second then both cypress and the browser close with the following output to the console.
Error: read ECONNRESET at TCP.onStreamRead (internal/stream_base_commons.js:205:27) { errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' } Error: read ECONNRESET at TCP.onStreamRead (internal/stream_base_commons.js:205:27)
I have not changed anything, its a fresh install. Anybody able to point me in the right direction on getting this resolved?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:40 (2 by maintainers)
Top Results From Across the Web
npm not working - "read ECONNRESET" - Stack Overflow
I was trying to install jquery in Angular project using the cmd - npm install jquery But there was a proxy error which...
Read more >just started and already wasted a few hours on this issue : r/node
The error says you cannot reach npm registry. Can you reach registry.npmjs.org from your browser?
Read more >npm not working - "read ECONNRESET" - SyntaxFix
I'm having a problem with npm, I cant install anything. Here is the error messages: C:\Windows\system32>npm install -g yo npm http GET ...
Read more >node:events:505 throw er; / unhandled 'error' event ^ error
"ECONNRESET" means the other side of the TCP conversation abruptly closed its end of the connection. This is most probably due to one...
Read more >phantomjs-prebuilt - npm
Installation fails with Error: read ECONNRESET or Error: connect ETIMEDOUT. This error means that something went wrong with your internet ...
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
We are getting the same error, and we narrowed the source of our error to Sophos, specifically the Network Threat Protection. When this is disabled the error does not occur. We are opening a ticket with Sophos in our case to try and get more info.
Just wanted to provide an update; We have spent time with Sophos support in order for them to pinpoint the issue and we have received report back that they believe they found the cause and are targeting a fix:
Keep in mind this isn’t “a sure thing”, but I am simply giving some hope to everyone affected by the Sophos issue that we might see a fix in the coming weeks.
Fingers crossed ! 🤞