I develop using Vagrant on OS X or Linux.I don't use a proxy, but have limited or unreliable internet access.I use a proxy when downloading Git repos.I use a proxy to connect to the npm registry.npm config get registry prints: Sorry, can't disclose this.It works on but throws an error on is my npm-debug.log (sensitive info replaced): To avoid any errors, ensure strict-ssl=false is set. Try running npm install to a custom registry with an invalid SSL certificate. How can the CLI team reproduce the problem? The corporate root CA is trusted locally (Windows and Mac keychain etc) but for npm we add a custom certificate bundle via npm config set cafile … and strict-ssl=false as a workaround. npmrc file, then going back and deleting those new key/values from my global. npmrc file and copying all the new key/value pairs, pasting those into my project specific.

I found success by just running all the npm config set commands I needed, going to my global.

Setting strict-ssl=false should workaround this. It only works on the global file, I think. We know our custom registry has an invalid SSL certificate. The registry is protected using a self-signed root CA certificate. We're using an internal registry via npm config set registry which is behind a corporate proxy. Running npm install on throws UNABLE_TO_VERIFY_LEAF_SIGNATURE Other ( see below for feature requests):.npm is doing something I don't understand.

Npm config set registry default