remote ls fails

[oskotsky]

Operating system and version:

n/a

nvm debug output:

Details

nvm ls output:

Details

How did you install nvm?

What steps did you perform?

$ nvm ls-remote --lts
N/A
$

What happened?

command ls-remote fails

What did you expect to happen?

list of available in repo versions

Is there anything in any of your profile files that modifies the PATH?

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

$ curl -I --compressed -v https://nodejs.org/dist/

• Trying 104.20.23.46:443...
• connect to 104.20.23.46 port 443 failed: Connection refused
• Trying 104.20.22.46:443...
• Connected to nodejs.org (104.20.22.46) port 443 (#0)
• ALPN, offering h2
• ALPN, offering http/1.1
• CAfile: /etc/ssl/certs/ca-certificates.crt
• CApath: /etc/ssl/certs
• TLSv1.0 (OUT), TLS header, Certificate Status (22):
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• OpenSSL SSL_connect: Connection reset by peer in connection to nodejs.org:443
• Closing connection 0
• TLSv1.0 (OUT), TLS header, Unknown (21):
• TLSv1.3 (OUT), TLS alert, decode error (562):
  curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to nodejs.org:443

Details

[ljharb]

As you can see by your curl failing, your issue is that you can't connect to nodejs.org securely. You'll have to fix your machine's SSL. The easiest probable cause to fix is that your system time might be off?

[oskotsky]

Do I miss something here? I don’t have this issue with other sites and at the same time the same error I see running this check from other systems, for example, aws instances: $ curl -I --compressed -v https://nodejs.org/dist/ * Trying 104.20.23.46:443... * Trying [2606:4700:10::6814:162e]:443... * Immediate connect fail for 2606:4700:10::6814:162e: Cannot assign requested address * Trying [2606:4700:10::6814:172e]:443... * Immediate connect fail for 2606:4700:10::6814:172e: Cannot assign requested address * connect to 104.20.23.46 port 443 failed: Connection timed out * Trying 104.20.22.46:443... * Connected to nodejs.org (104.20.22.46) port 443 * ALPN: curl offers h2,http/1.1 * Cipher selection: ***@***.*** * TLSv1.2 (OUT), TLS handshake, Client hello (1): * CAfile: /etc/pki/tls/certs/ca-bundle.crt * CApath: none ^C $ $ curl -I --compressed -v https://ucsf.edu * Trying 52.73.160.199:443... * Connected to ucsf.edu (52.73.160.199) port 443 * ALPN: curl offers h2,http/1.1 * Cipher selection: ***@***.*** * TLSv1.2 (OUT), TLS handshake, Client hello (1): * CAfile: /etc/pki/tls/certs/ca-bundle.crt * CApath: none * TLSv1.2 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS change cipher, Change cipher spec (1): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 * ALPN: server accepted h2 * Server certificate: * subject: C=US; ST=California; O=University of California, San Francisco; CN=*.ucsf.edu * start date: May 31 00:00:00 2024 GMT * expire date: Jul 1 23:59:59 2025 GMT * subjectAltName: host "ucsf.edu" matched cert's "ucsf.edu" * issuer: C=US; O=Internet2; CN=InCommon RSA Server CA 2 * SSL certificate verify ok. * using HTTP/2 * [HTTP/2] [1] OPENED stream for https://ucsf.edu/ * [HTTP/2] [1] [:method: HEAD] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: ucsf.edu] * [HTTP/2] [1] [:path: /] * [HTTP/2] [1] [user-agent: curl/8.3.0] * [HTTP/2] [1] [accept: */*] * [HTTP/2] [1] [accept-encoding: deflate, gzip]

HEAD / HTTP/2 Host: ucsf.edu User-Agent: curl/8.3.0 Accept: */* Accept-Encoding: deflate, gzip

< HTTP/2 301 HTTP/2 301 < server: nginx server: nginx < date: Tue, 04 Mar 2025 04:18:12 GMT date: Tue, 04 Mar 2025 04:18:12 GMT < content-type: text/html; charset=iso-8859-1 content-type: text/html; charset=iso-8859-1 < content-length: 229 content-length: 229 < location: https://www.ucsf.edu/ location: https://www.ucsf.edu/ < x-content-type-options: nosniff x-content-type-options: nosniff < expires: Tue, 04 Mar 2025 04:17:26 GMT expires: Tue, 04 Mar 2025 04:17:26 GMT < x-request-id: v-943a194c-f8af-11ef-9e71-73084cb65640 x-request-id: v-943a194c-f8af-11ef-9e71-73084cb65640 < cache-control: max-age=900, public cache-control: max-age=900, public < age: 46 age: 46 < via: varnish via: varnish < x-cache: HIT x-cache: HIT < x-cache-hits: 1 x-cache-hits: 1 < * Connection #0 to host ucsf.edu left intact $ From: Jordan Harband ***@***.***> Sent: Monday, March 3, 2025 8:09 PM To: nvm-sh/nvm ***@***.***> Cc: Oskotsky, Boris ***@***.***>; Author ***@***.***> Subject: Re: [nvm-sh/nvm] remote ls fails (Issue #3539) As you can see by your curl failing, your issue is that you can't connect to nodejs. org securely. You'll have to fix your machine's SSL. The easiest probable cause to fix is that your system time might be off? — Reply to this email directly, ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd As you can see by your curl failing, your issue is that you can't connect to nodejs.org securely. You'll have to fix your machine's SSL. The easiest probable cause to fix is that your system time might be off? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/nvm-sh/nvm/issues/3539*issuecomment-2696140101__;Iw!!LQC6Cpwp!udVKxxrPuWsokaOjEF8fosEwYpW-tnBHwmaTSmr1-mhFQjnWI8-kveKG3kYkoNCgu3Qp-jccCO-j79pCaxGBh0vtBq_aqA4$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AHWKXF6WENLAXX7BAZJMPTD2SURNFAVCNFSM6AAAAABYIQJG5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJWGE2DAMJQGE__;!!LQC6Cpwp!udVKxxrPuWsokaOjEF8fosEwYpW-tnBHwmaTSmr1-mhFQjnWI8-kveKG3kYkoNCgu3Qp-jccCO-j79pCaxGBh0vtryOXCvk$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> [ljharb]ljharb left a comment (nvm-sh/nvm#3539)<https://urldefense.com/v3/__https:/github.com/nvm-sh/nvm/issues/3539*issuecomment-2696140101__;Iw!!LQC6Cpwp!udVKxxrPuWsokaOjEF8fosEwYpW-tnBHwmaTSmr1-mhFQjnWI8-kveKG3kYkoNCgu3Qp-jccCO-j79pCaxGBh0vtBq_aqA4$> As you can see by your curl failing, your issue is that you can't connect to nodejs.org securely. You'll have to fix your machine's SSL. The easiest probable cause to fix is that your system time might be off? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/nvm-sh/nvm/issues/3539*issuecomment-2696140101__;Iw!!LQC6Cpwp!udVKxxrPuWsokaOjEF8fosEwYpW-tnBHwmaTSmr1-mhFQjnWI8-kveKG3kYkoNCgu3Qp-jccCO-j79pCaxGBh0vtBq_aqA4$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AHWKXF6WENLAXX7BAZJMPTD2SURNFAVCNFSM6AAAAABYIQJG5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJWGE2DAMJQGE__;!!LQC6Cpwp!udVKxxrPuWsokaOjEF8fosEwYpW-tnBHwmaTSmr1-mhFQjnWI8-kveKG3kYkoNCgu3Qp-jccCO-j79pCaxGBh0vtryOXCvk$>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[ljharb]

Your system's time is a few minutes slow, but close enough - i think the window is about 5 minutes.

It is very strange indeed that you can connect correctly to ucsf but not to nodejs.org. It might be an IPv6 issue. Can you try disabling ipv6? (either way this has nothing to do with nvm)

[oskotsky]

Thank you for looking into this! It turned out that it happens with our VPN client running. I can’t control the configuration of VPN and need to reach out to our IT/networking department. This issue appeared in my aws servers a few days ago. Before everything worked as expected. Do you happen to know if anything changed on nvm side? Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Jordan Harband ***@***.***> Sent: Monday, March 3, 2025 8:24:11 PM To: nvm-sh/nvm ***@***.***> Cc: Oskotsky, Boris ***@***.***>; Author ***@***.***> Subject: Re: [nvm-sh/nvm] remote ls fails (Issue #3539) Your system's time is a few minutes slow, but close enough - i think the window is about 5 minutes. It is very strange indeed that you can connect correctly to ucsf but not to nodejs. org. It might be an IPv6 issue. Can you try disabling ipv6? ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd Your system's time is a few minutes slow, but close enough - i think the window is about 5 minutes. It is very strange indeed that you can connect correctly to ucsf but not to nodejs.org. It might be an IPv6 issue. Can you try disabling ipv6? (either way this has nothing to do with nvm) — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/nvm-sh/nvm/issues/3539*issuecomment-2696155285__;Iw!!LQC6Cpwp!svjSg36Arfu9enem2e_8_-7HRRwhNPWmyBeQba8pnsK6Kuf68gcN99PGLh0VpD58C4NU_nRKzdZyf2X0hLY-JWZEIuGE_JY$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AHWKXFZLJUVYGTZWWFNKIXT2SUTGXAVCNFSM6AAAAABYIQJG5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJWGE2TKMRYGU__;!!LQC6Cpwp!svjSg36Arfu9enem2e_8_-7HRRwhNPWmyBeQba8pnsK6Kuf68gcN99PGLh0VpD58C4NU_nRKzdZyf2X0hLY-JWZE-VU4mZM$>. You are receiving this because you authored the thread.Message ID: ***@***.***> [ljharb]ljharb left a comment (nvm-sh/nvm#3539)<https://urldefense.com/v3/__https://github.com/nvm-sh/nvm/issues/3539*issuecomment-2696155285__;Iw!!LQC6Cpwp!svjSg36Arfu9enem2e_8_-7HRRwhNPWmyBeQba8pnsK6Kuf68gcN99PGLh0VpD58C4NU_nRKzdZyf2X0hLY-JWZEIuGE_JY$> Your system's time is a few minutes slow, but close enough - i think the window is about 5 minutes. It is very strange indeed that you can connect correctly to ucsf but not to nodejs.org. It might be an IPv6 issue. Can you try disabling ipv6? (either way this has nothing to do with nvm) — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/nvm-sh/nvm/issues/3539*issuecomment-2696155285__;Iw!!LQC6Cpwp!svjSg36Arfu9enem2e_8_-7HRRwhNPWmyBeQba8pnsK6Kuf68gcN99PGLh0VpD58C4NU_nRKzdZyf2X0hLY-JWZEIuGE_JY$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AHWKXFZLJUVYGTZWWFNKIXT2SUTGXAVCNFSM6AAAAABYIQJG5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJWGE2TKMRYGU__;!!LQC6Cpwp!svjSg36Arfu9enem2e_8_-7HRRwhNPWmyBeQba8pnsK6Kuf68gcN99PGLh0VpD58C4NU_nRKzdZyf2X0hLY-JWZE-VU4mZM$>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[ljharb]

Nope, nothing's changed on the nvm side wrt this in a decade - seems like it's your VPN causing the issue. I'll close, but I'm happy to reopen it if there's something actionable for nvm.