Skip to content
This repository has been archived by the owner. It is now read-only.

SELF_SIGNED_CERT_IN_CHAIN error and npm config set strict-ssl=false v0.10.33 #6916

Closed
nestoru opened this issue Dec 12, 2014 · 5 comments

Comments

@nestoru
Copy link

commented Dec 12, 2014

Hi guys,

To upgrade npm for node v0.10.33 without getting "SELF_SIGNED_CERT_IN_CHAIN" error it would look like the only alternative is to run "npm config set strict-ssl=false" which would look insecure to me.

Is this a bug?

Thanks!

  • Nestor
@smikes

This comment has been minimized.

Copy link
Contributor

commented Dec 13, 2014

You can also try npm config set ca=null. This tells npm to not use the special npm-supplied certificate authority which was necessary when npm used a self-signed certificate.

You may be able to update by using the install script: https://github.com/npm/npm/wiki/Troubleshooting#if-your-npm-is-broken
curl https://www.npmjs.org/install.sh | sh

Please let me know if this doesn't address your question.

@nestoru

This comment has been minimized.

Copy link
Author

commented Dec 13, 2014

Hi smikes. Thanks for your reply. Yes I did try npm config but it did not work for me. And yes I install from that script which BTW used to have a -L to follow location changes and it was giving me issues but I basically worked round it downloading to tmp and executing after. The installation worked but the issue is when you want to use it, no matter what command you issue "SELF_SIGNED_CERT_IN_CHAIN" error stops the show.

I think if you install a brand new ubuntu you will be able to recreate the issue. Not sure if you can but I can try perhaps using docker and some recipes to make a demonstration.

@smikes

This comment has been minimized.

Copy link
Contributor

commented Dec 13, 2014

Can you please tell me the output of the following:

which npm
npm config ls
env | grep -i node

(If there is a //registry.npmjs.org/:_password key, please delete it before posting)

@nestoru

This comment has been minimized.

Copy link
Author

commented Dec 13, 2014

Thank you very much! 'npm config ls' made me realized npm was somehow using a proxy I had configured system wide via gsettings. This is a non issue. Best regards, - Nestor

@othiym23

This comment has been minimized.

Copy link
Contributor

commented Dec 15, 2014

Closing as resolved!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants
You can’t perform that action at this time.