Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
SELF_SIGNED_CERT_IN_CHAIN (Corporate Overlords SSL-intercepting proxy) #9282
After reading all the related issues I could, e.g. #7439 (comment) #9195 #8125 #7547 #7519 I thought I'd answer about what if you are on a corporate network that interjects a self-signed SSL certificate (such as http://packetpushers.net/using-ssl-intercept-with-adcs-firewalls-to-inspect-clean-encrypted-traffic/ ) but doesn't give you a proxy to work around it.
So, I was going to write this into https://github.com/npm/npm/wiki/Troubleshooting#ssl-intercepting-proxy
Corporate Overlord SSL-intercepting proxy
The following text courtesy of Alex Taylor on http://stackoverflow.com/posts/30341389/revisions
Here's the error:
On a Linux VM (hosted on a Windows machine behind an SSL-intercepting proxy), I get secure access to work using (as root):
No equals-sign and name SSL certificate path directly rather than using
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.