cordova install fails with CERT_UNTRUSTED

[ahujac]

Here is what i get - looks to me like something wrong with the cert on the registry server ?

C:\Users\cahuja\tpt>npm install -g cordova ionic
npm http GET https://registry.npmjs.org/cordova
npm http GET https://registry.npmjs.org/ionic
npm http GET https://registry.npmjs.org/cordova
npm http GET https://registry.npmjs.org/ionic
npm http GET https://registry.npmjs.org/ionic
npm http GET https://registry.npmjs.org/cordova
npm ERR! Error: SSL Error: CERT_UNTRUSTED
npm ERR! at ClientRequest. (C:\Program Files\nodejs\node_modules\npm\node_modules\request\main.js:525: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 as onIncoming
npm ERR! at HTTPParser.parserOnHeadersComplete as onHeadersComplete
npm ERR! at CleartextStream.socketOnData as ondata
npm ERR! at CleartextStream.CryptoStream._push (tls.js:495:27)
npm ERR! at SecurePair.cycle (tls.js:849:20)
npm ERR! at EncryptedStream.CryptoStream.write (tls.js:230: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

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "
-g" "cordova" "ionic"
npm ERR! cwd C:\Users\cahuja\tpt
npm ERR! node -v v0.8.8
npm ERR! npm -v 1.1.59
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\Users\cahuja\tpt\npm-debug.log
npm ERR! not ok code 0

[npm-robot]

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.