nvm ls-remote command results in "N/A" (can't install Node 20)

[MinaYuni]

Operating system and version:

SUSE Linux Enterprise Server 15 SP5

nvm debug output:

nvm --version: v0.39.7
$SHELL: /bin/bash
$SHLVL: 1
whoami: 'ifdev'
${HOME}: /home/ifdev
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: ${NVM_DIR}/versions/node/v18.19.0/bin:${HOME}/miniconda3/bin:${HOME}/miniconda3/condabin:${HOME}/bin:${HOME}/.local/bin:/opt/BullseyeCoverage/bin:${HOME}/bin:/usr/local/bin:/usr/bin:/bin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 4.4.23(1)-release (x86_64-suse-linux-gnu)'
uname -a: 'Linux 5.15.153.1-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux'
checksum binary: 'sha256sum'
awk: /usr/bin/awk, GNU Awk 4.2.1, API: 2.0
curl: /usr/bin/curl, curl 8.0.1 (x86_64-suse-linux-gnu) libcurl/8.0.1 OpenSSL/1.1.1l-fips zlib/1.2.13 brotli/1.0.7 zstd/1.5.0 libidn2/2.2.0 libpsl/0.20.1 (+libidn2/2.2.0) libssh/0.9.8/openssl/zlib nghttp2/1.40.0
wget: /usr/bin/wget, GNU Wget 1.20.3 built on linux-gnu.
git: /usr/bin/git, git version 2.35.3
grep: /usr/bin/grep, grep (GNU grep) 3.1
sed: /usr/bin/sed, sed (GNU sed) 4.4
cut: /usr/bin/cut, cut (GNU coreutils) 8.32
basename: /usr/bin/basename, basename (GNU coreutils) 8.32
rm: /usr/bin/rm, rm (GNU coreutils) 8.32
mkdir: /usr/bin/mkdir, mkdir (GNU coreutils) 8.32
xargs: /usr/bin/xargs, xargs (GNU findutils) 4.8.0
nvm current: v18.19.0
which node: ${NVM_DIR}/versions/node/v18.19.0/bin/node
which iojs: which: no iojs in (${NVM_DIR}/versions/node/v18.19.0/bin:${HOME}/miniconda3/bin:${HOME}/miniconda3/condabin:${HOME}/bin:${HOME}/.local/bin:/opt/BullseyeCoverage/bin:${HOME}/bin:/usr/local/bin:/usr/bin:/bin)
which npm: ${NVM_DIR}/versions/node/v18.19.0/bin/npm
npm config get prefix: ${NVM_DIR}/versions/node/v18.19.0
npm root -g: ${NVM_DIR}/versions/node/v18.19.0/lib/node_modules

nvm ls output:

->     v18.19.0
default -> 18.19.0 (-> v18.19.0)
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v18.19.0) (default)
stable -> 18.19 (-> v18.19.0) (default)
lts/* -> lts/iron (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.12 (-> N/A)
lts/fermium -> v14.21.3 (-> N/A)
lts/gallium -> v16.20.2 (-> N/A)
lts/hydrogen -> v18.20.3 (-> N/A)
lts/iron -> v20.15.0 (-> N/A)

How did you install nvm?

install script in readme

What steps did you perform?

Installed nvm
Run nvm ls-remote and nvm install 20

What happened?

nvm ls-remote returns N/A
nvm install 20 returns Version '20' not found - try 'nvm ls-remote' to browse available versions.

What did you expect to happen?

NVM should install Node 20

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

export PATH=/opt/BullseyeCoverage/bin:$PATH
export PATH=~/.local/bin:$PATH
export PATH=~/bin:$PATH

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

* Could not resolve host: nodejs.org
* Closing connection 0
curl: (6) Could not resolve host: nodejs.org

[ljharb]

The curl error in your output suggests a DNS issue. That needs to be resolved before nvm can do anything.

[MinaYuni]

I fixed the DNS issue.
Here the new output of curl -I --compressed -v https://nodejs.org/dist/

*   Trying 104.20.23.46:443...
* Connected to nodejs.org (104.20.23.46) port 443 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: self signed certificate in certificate chain
* Closing connection 0
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

[ljharb]

The SSL problem suggests that either your CA files are out of date, your system clock is wrong, or that SSL connections are being blocked. Are you perhaps in a country, workplace, or school that is filtering or blocking public internet traffic?

[MinaYuni]

Yes, I have to install Node 20 for work but it looks like the company's VPN/network blocks some internet traffic.

[ljharb]

You’ll have to get the company to unblock things then, if you want to be able to use the internet properly.