Always get errors using "npm install / update" #2663

Closed
iamlinix opened this Issue Aug 1, 2012 · 7 comments

7 participants

@iamlinix

Always get the following error message.

I was using nodejs 0.6.4 and everything worked just fine back then.
Then I updated my nodejs to 0.8.4, and since then, I got this error every time I try to install a new component or update anything.

npm ERR! Error: SSL Error: Hostname/IP doesn't match certificate's altnames
npm ERR! at ClientRequest. (/opt/nodejs/lib/node_modules/npm/node_modules/request/main.js:440:26)
npm ERR! at ClientRequest.g (events.js:185:14)
npm ERR! at ClientRequest.EventEmitter.emit (events.js:88:17)
npm ERR! at HTTPParser.parserOnIncomingClient (http.js:1445:7)
npm ERR! at HTTPParser.parserOnHeadersComplete as onHeadersComplete
npm ERR! at CleartextStream.socketOnData (http.js:1356:20)
npm ERR! at CleartextStream.CryptoStream._push (tls.js:485:27)
npm ERR! at SecurePair.cycle (tls.js:839:20)
npm ERR! at EncryptedStream.CryptoStream.write (tls.js:220:13)
npm ERR! at Socket.ondata (stream.js:38:26)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! npm-@googlegroups.com

@DigitalGoldfish

I had the same problem today. In the end i managed to bypass it by setting the configuration parameter "strict-ssl" to false.

npm config set strict-ssl false

@iamlinix
@mfncooper mfncooper closed this Aug 7, 2012
@fresheneesz

@mfncooper Is this fixed in a version of npm later than 1.3.24 (where I see this happening for browserify)? I'm wondering if i should just upgrade or if I have to use a work around

@iDVB

Looks like it happens even in 1.4.28

Image of Err

However, running npm config set strict-ssl false does work

@othiym23

For all of you stumbling across this issue today (2014-12-11), see status.npmjs.org or this tweet (ETA that I know what year it is):

a cdn configuration mistake means some people are seeing cert errors: http://status.npmjs.org/incidents/7xv9rx6722v8

rollback in progress.

Please note that today's production incident is completely unrelated to the OP on this issue.

@fresheneesz

Gotcha, thanks Forrest!

@wallstudios

thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment