npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

nom install throwing Error: tunneling socket could not be established, cause=connect EINVAL

Hello there

I’ve been running npm install in a node app, on a jenkins slave for the past 10 months without an issue.

Today, at approx 12:30 I started getting this error when trying to download the .tgz files from our internal nexus server

Error: tunneling socket could not be established, cause=connect EINVAL 0.0.12.56:80 - Local (0.0.0.0:0)

We’re using a .npmrc file in the repo that looks like this

registry = http://internalURL
email=my@example.com
always-auth=true
_auth=secretstuff

I can curl the .tgz files down from the machine, so there’s no sudden firewall changes.

Networks are being very quiet about any changes they may have made.

Could anyone think of how to try and debug this? How exactly is npm trying to connect?

Does that auth element expire or something?

Any tips or help, greatly appreciated.