Nvm: running nvm ls - remote returns N/A

Created on 4 Nov 2015  ·  18Comments  ·  Source: nvm-sh/nvm

I'm trying to install Node through nvm, but when i type nvm ls-remote I just get N/A.What reason is this and how to solve it ?

SSL issue needs followup
Source
picture LeoMustafa

All 18 comments

This is likely due to an SSL error on your side. If you do curl -v https://nodejs.org/dist/ and curl -v https://iojs.org/dist/, what output do you get?

ljharb picture ljharb on 4 Nov 2015
👍1

I get a long list of information,as follows:

  • Hostname was NOT found in DNS cache
  • Trying 2400:cb00:2048:1::6814:172e...
  • Trying 104.20.22.46...
  • Connected to nodejs.org (104.20.22.46) port 443 (#0)
  • successfully set certificate verify locations:
  • CAfile: none
    CApath: /etc/ssl/certs
  • SSLv3, TLS handshake, Client hello (1):
  • SSLv3, TLS handshake, Server hello (2):
  • SSLv3, TLS handshake, CERT (11):
  • SSLv3, TLS handshake, Server key exchange (12):
  • SSLv3, TLS handshake, Server finished (14):
  • SSLv3, TLS handshake, Client key exchange (16):
  • SSLv3, TLS change cipher, Client hello (1):
  • SSLv3, TLS handshake, Finished (20):
  • SSLv3, TLS change cipher, Client hello (1):
  • SSLv3, TLS handshake, Finished (20):
  • SSL connection using ECDHE-RSA-AES128-GCM-SHA256
  • Server certificate:
  • subject: OU=Domain Control Validated; OU=PositiveSSL Wildcard; CN=*.nodejs.org
  • start date: 2015-08-23 00:00:00 GMT
  • expire date: 2017-08-22 23:59:59 GMT
  • subjectAltName: nodejs.org matched
  • issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMODO RSA Domain Validation Secure Server CA
  • SSL certificate verify ok.

GET /dist/ HTTP/1.1
User-Agent: curl/7.35.0
Host: nodejs.org
Accept: _/_

< HTTP/1.1 200 OK

LeoMustafa picture LeoMustafa on 4 Nov 2015

I see that you're using SSLv3, which is old and insecure - I think you need to update your machine's openSSL, and root CAs. You may be able to do this simply by updating curl itself.

ljharb picture ljharb on 4 Nov 2015

It still doesn't work when i fished update curl.

LeoMustafa picture LeoMustafa on 5 Nov 2015

So nvm ls-remote node still returns N/A, and curl -v https://nodejs.org/dist/ still prints out the same info?

ljharb picture ljharb on 5 Nov 2015

Yes,i don't know what i should do next

LeoMustafa picture LeoMustafa on 6 Nov 2015

It can work normally now ! Thanks a lot!

LeoMustafa picture LeoMustafa on 6 Nov 2015

Thanks for confirming!

ljharb picture ljharb on 6 Nov 2015

I ran into this exact issue because my corporate proxy was not set.
Exporting the following environment variable fix my problem:
$ export ALL_PROXY=http://proxyhost:port

njtman picture njtman on 4 Nov 2016

i'm not familiar with "ALL_PROXY" nor with what tools respect it - can you clarify?

ljharb picture ljharb on 4 Nov 2016

FWIW I had the same issue as @njtman (corporate proxy) and solved it using his solution.

Basically I had set up the proxy on an operating system level (network settings in Mac os) but curl was ignoring it. Even though I'm not familiar with ALL_PROXY either, I tried it and it worked.

Would love to have some more time to investigate deeper but it's my first day at this new job and I have plenty of things to do.

igghera picture igghera on 20 Feb 2017

Thanks, appreciate the confirmation. No idea tho why a corporation wouldn't set up their proxy transparently (at the network level), as opposed to making individual machines configure it.

ljharb picture ljharb on 20 Feb 2017

I faced the same issue but by curl was not working as well so i added the http_proxy in my .bashrc file.

mansisce picture mansisce on 5 Mar 2018
👍1

For me curl --verbose https://nodejs.org/dist/ is returning :

* Could not resolve host: nodejs.org
* Closing connection 0
curl: (6) Could not resolve host: nodejs.org
AmmarHasan picture AmmarHasan on 10 Sep 2018

@AmmarHasan sounds like either the site is down, your dns isn’t resolving it properly, or you have something on your network blocking your connection to it. If you’re still having trouble, please file a new issue.

ljharb picture ljharb on 10 Sep 2018

@ljharb yes when I switched to other network everything worked

AmmarHasan picture AmmarHasan on 10 Sep 2018
👍1

curl -v https://iojs.org/dist/

Same question as above, but I got this output on the terminal: curl: (48) An unknown option was passed in to libcurl

wenlittleoil picture wenlittleoil on 12 Aug 2020

@wenlittleoil your curl doesn't support -v? Please file a new issue and fill out the template :-)

ljharb picture ljharb on 12 Aug 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

dillon picture dillon  ·  3Comments
kas picture kas  ·  3Comments
goalidea picture goalidea  ·  3Comments
raitucarp picture raitucarp  ·  3Comments
a-x- picture a-x-  ·  5Comments