npm install -g yo / tarball fetch failed issue

[jcc74]

Hi guys,

I'm stuck installing yeoman getting errors.
For information:

1. Proxy and registry have been configured correctly( I assume :-) ):
   npm config set proxy "http://user:password@server:port/"
   npm config set https-proxy "http://user:password@server:port/"
   npm config set registry http://registry.npmjs.org/
2. SASS, Compass and bower have already been installed correctly, c.f. "-v" check command -> I then assume that proxy is correctly configured

Apparently, during the the "npm install -g yo" command execution, https://github.com/Filirom1/nopt/tarball/master#pull-request-in-progress fetch failed, then it causes a UNABLE_TO_VERIFY_LEAF_SIGNATURE error. Others package have been downloaded correctly.
Here is the execution trace fragment:

$ npm install -g yo
npm http GET http://registry.npmjs.org/yo
npm http 304 http://registry.npmjs.org/yo
npm http GET http://registry.npmjs.org/update-notifier
npm http GET http://registry.npmjs.org/lodash
.....
npm http 304 http://registry.npmjs.org/mkdirp
npm ERR! fetch failed https://github.com/Filirom1/nopt/tarball/master#pull-reque
st-in-progress
npm http GET http://registry.npmjs.org/rimraf
.......
npm http 304 http://registry.npmjs.org/debuglog/0.0.2
npm http GET https://github.com/Filirom1/nopt/tarball/master#pull-request-in-progress
npm ERR! fetch failed https://github.com/Filirom1/nopt/tarball/master#pull-request-in-progress
npm http GET https://github.com/Filirom1/nopt/tarball/master#pull-request-in-progress
npm ERR! fetch failed https://github.com/Filirom1/nopt/tarball/master#pull-request-in-progress
npm ERR! Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE
npm ERR! at SecurePair. (tls.js:1370:32)
npm ERR! at SecurePair.EventEmitter.emit (events.js:92:17)
npm ERR! at SecurePair.maybeInitFinished (tls.js:982: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! at flow (_stream_readable.js:592:7)
npm ERR! at Socket.pipeOnReadable (_stream_readable.js:624:5)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/isaacs/npm/issues

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "c:\Program Files\nodejs\node.exe" "c:\Program Files\nodej
s\node_modules\npm\bin\npm-cli.js" "install" "-g" "yo"
npm ERR! cwd C:\Users\colinje
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.21
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\Users\colinje\npm-debug.log
npm ERR! not ok code 0

I've been googling for a while, but I have know idea to solve that issue. Does any one know what's going wrong there?
Thank's for your help.

[jcc74]

Moved this one to yeoman repositorie: yeoman/yeoman#1274

[Praimen]

I have check both links to this issue...has it been resolved somewhere else?

[jcc74]

Nop. Fyi, i gave a try from my house, without this corporate proxy, and it works great...
But still not working with this f*** corporate proxy. Still the same error...

[justinrknowles]

This dependency poses an issue for any one behind a proxy that blocks github (as above) or people running the npm registry in an offline / replicated mode.

[jcc74]

OK, is there any workaround or any fix planned to allow all these people to use yeoman?

[sixtyh8]

Getting the same error while trying to install yeoman behind a corporate proxy.

npm ERR! fetch failed https://github.com/Filirom1/nopt/tarball/master#pull-request-in-progress

[cocazoulou]

Hello All,

I found a work arround for our user.
npm --https-proxy=http://proxy.company.com install yo -g

Thank you

[jcc74]

Hi,

I gave it a try, with and without providing proxy authentication, and nothing better.

[rtelicak]

This helped me:
make sure your that in npm config you have strict-ssl = false and your proxy is set
then update npm sudo npm install -g npm
run sudo npm install -g yo

[domenic]

This usually occurs if you are being subjected to a man-in-the-middle (MITM) attack, either by the NSA, your ISP, your enemy who is using the same coffeeshop WiFi as you, or your corporate proxy. npm is erroring because something between you and the registry has interfered with the integrity of the SSL encryption, and it does not want to proceed in that state.

If you are willing to give up that security and allow the MITM-ing party, or any other party on the internet, to intercept and potentially modify your requests to/from the npm registry, then you can turn off SSL as people have said in this thread (via strict-ssl = false). Otherwise, you'll need to tell the MITM-ing party to politely stop defeating encryption, and/or make sure your proxy settings are compatible with their network.