Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

phonegap installl problem #4249

Closed
jkishore opened this Issue Dec 4, 2013 · 5 comments

Comments

Projects
None yet
4 participants

jkishore commented Dec 4, 2013

I have installed nodejs software. Now trying to install the phonegap using the command
npm install -g phonegap. It is not installing but showing the errors as follows

C:\Users\username>npm install -g phonegap
npm http GET https://registry.npmjs.org/phonegap
npm http GET https://registry.npmjs.org/phonegap
npm http GET https://registry.npmjs.org/phonegap
npm ERR! Error: CERT_UNTRUSTED
npm ERR! at SecurePair. (tls.js:1362:32)
npm ERR! at SecurePair.EventEmitter.emit (events.js:92:17)
npm ERR! at SecurePair.maybeInitFinished (tls.js:974:10)
npm ERR! at CleartextStream.read as _read
npm ERR! at CleartextStream.Readable.read (_stream_readable.js:320:10)
npm ERR! at EncryptedStream.write as _write
npm ERR! at doWrite (_stream_writable.js:221:10)
npm ERR! at writeOrBuffer (_stream_writable.js:211:5)
npm ERR! at EncryptedStream.Writable.write (_stream_writable.js:180:11)
npm ERR! at write (_stream_readable.js:583:24)
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" "phonegap"
npm ERR! cwd C:\Users\username
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\Users\username\npm-debug.log
npm ERR! not ok code 0

Please try to suggest

Member

timoxley commented Jan 9, 2014

@jkishore Are you still having this problem?

This seems to be a duplicate of the various CERT_UNTRUSTED issues on npm. Can you please try the solutions proposed in #1580 (comment) and report back if this solves your problem? Also possible it's a local network configuration issue.

jkishore commented Jan 9, 2014

@timoxley Ya, issue got resolved... may be internal network issue... Late reply... but thanks for reply...

Member

timoxley commented Jan 9, 2014

@jkishore Great stuff, so this issue can be closed?

#4430

jkishore commented Jan 9, 2014

ya... you can close the issue....

@domenic domenic closed this Jan 9, 2014

Also if other people have this problem - I had to update my version of node

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