Seeing elevated network read ECONNRESET from AWS

[nodesocket]

Today been seeing lots of npm ERR! network read ECONNRESET when invoking npm install.

Does this indicate a CDN issue on npm's side? This is from multiple AWS instances in the us-west-1 and us-west-2 regions.

[nodesocket]

Anybody else confirm?

[pyramation]

there was an issue where an accepted answer was to change https to http here

however, that solution isn't ideal. Our registry is set to https://registry.npmjs.org/... could it be something with the cert or a configuration? This issue has been intermittent. Any ideas are greatly appreciated, cheers!

[blopker]

Having this issue as well. CentOS 7.

[blopker]

Confirmed that changing registry to use http fixes issue.

[nodesocket]

I'm not going to switch to http since it is a security concern because of man in the middle attacks. I'm guessing npm is having intermittent https issues upstream at their cdn? The npm status page does not indicate anything.

[othiym23]

This is a discussion for npm/registry because the CLI is just using stock Node.js HTTP / HTTPS, so I'm to redirect y'all there and close this issue. I can say that this is generally a local networking issue that happens when there's a lot of simultaneous HTTPS connections, and not a problem with npm's CDN provider. Somebody from @npm/registry-team can give you more information once you open an issue over there.

[webuniverseio]

It is worth to mention that the issue and solution is described here: npm/registry#10.