nvm: `nvm ls-remote` returns N/A prior to v0.17.3

nodejs.org switched to HTTPS today, so to fix this issue, either:

Switch to v0.17.3 or later: https://github.com/creationix/nvm/tree/v0.17.3
add export NVM_NODEJS_ORG_MIRROR="https://nodejs.org/dist" to your shell profile.

I’ll leave this open for a little while since people will probably trickle in.

About this issue

Original URL
State: closed
Created 10 years ago
Reactions: 1
Comments: 16 (6 by maintainers)

Most upvoted comments

If you´re like me and are joined to a domain using centrify you will need to set the CURL_CA_BUNDLE environmental variable so that it uses the correct CA.

On ubuntu the default location is /etc/ssl/certs/ca-certificates.crt so you can type this in your terminal (or to make it permanent, add it to the bottom of your .bashrc file)

export CURL_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt

Further info: http://community.centrify.com/t5/DirectControl-Express-for-UNIX/Curl-OpenSSL-certificate-question/td-p/15539

grimurd on Feb 23, 2015

If anyone else running into this issue, try this:

CentOS:

cp /etc/pki/tls/certs/ca-bundle.crt /etc/pki/tls/certs/ca-bundle.crt.bak
wget -O /etc/pki/tls/certs/ca-bundle.crt http://curl.haxx.se/ca/cacert.pem

^{Source: http://it.i88.ca/2014/09/how-to-update-root-ca-certificate.html}

Debian:

update-ca-certificates

That worked for me.

am11 on Jan 19, 2015