Connection errors

[SharakPL]

➜ ~ fnm list-remote
error: HttpError: error sending request for url (https://nodejs.org/dist/index.json): error trying to connect: dns error: failed to lookup address information: Try again
➜ ~ fnm install 14
error: Having a hard time listing the remote versions: error sending request for url (https://nodejs.org/dist/index.json): error trying to connect: dns error: failed to lookup address information: Try again

Maybe it uses wrong protocol or something. curl https://nodejs.org/dist/index.json got the output right away.

Installed on Termux (Android 11). Shell: zsh

[nickjwilde]

@SharakPL I had the same issue using termux android 12. I downloaded the linux binary from daily releases and installed manually

fnm list-remote

Gave me

error: error sending request for url (https://nodejs.org/dist/index.json): error trying to connect: dns error: failed to lookup address information: Try again

Curl was successful hitting https://nodejs.org/dist/index.json from termux.

I was able to get this working with a little tweak. Disclaimer: I am not a rust developer so there may be a better way to do this that's not so monkey patched.

• I downloaded the source using 'git clone'.
• I modified src/system_info.rs and pulled 2 functions out of [#cfg] blocks

pub fn platform_name() -> &'static str {
  "linux"                                            
}

And

pub fn platform_arch() -> &'static str {         "arm64"
}

• Then run 'cargo build'
• run 'cargo run -- list-remote' worked for me
• I then installed locally using 'cargo install --path /path/to/fnm_source'

@Schniz not sure if any of this helps. I'm not super familiar with rust so I sorta hacked the solution to the problem.

Let me know if you have any questions about this.

[donaldxdonald]

same issue
WSL( Ubuntu 20.04 )
Shell: zsh

Update
I had clone the repo and run cargo intall --path . and cargo build. Then replace ~/.fnm/fnm with ./target/release/fnm. It works. So maybe it is the install script issue.

[Schniz]

I don't have any Android devices. What OS arch is it? maybe there's a feature flag we need to provide by default? Another build pipeline in CI?

[acemasterjb]

I am also having the same issue @donaldxdonald is having.

System: WSL, Ubuntu 20.04
Shell: fish

if I wget the urls it is timing out on, it downloads the files fine, e.g.

fnm list-remote
error: error sending request for url (https://nodejs.org/dist/index.json): operation timed out

[tredmon]

If you use the patch by @nickjwilde it will successfully download node but the version it downloads will fail to run. To get it to work would require downloading node built specifically for Android, for which there are currently no official builds. Supporting android would thus also require either hosting node pre-built for android, or building node from source.

Also, if you want to use the correct cfg in that patch so it looks for the correct pre-built you would add

#[cfg(target_os = "android")]
pub fn platform_name() -> &'static str {
    "android"
}

My tests were from termux

$ uname -a
Linux localhost 4.9.292-g5f518a30d143-ab8080176 #0 SMP PREEMPT Fri Jan 14 10:23:32 UTC 2022 aarch64 Android

[latipun7]

I don't have any Android devices. What OS arch is it? maybe there's a feature flag we need to provide by default? Another build pipeline in CI?

@Schniz, I have this exact error when trying to install node in termux android. My android is aarch64, so, it should successfully downloading and installing node from this https://nodejs.org/dist/v16.17.0/node-v16.17.0-linux-arm64.tar.xz (arm64 / ARMv8).

From termux with zsh shell:

% uname -m
aarch64

Running curl -fsLS https://nodejs.org/dist/index.json is success.

[nikolalukovic]

I have this issue on fish in wsl2 ubuntu as well when trying to download x64 node versions...

[acemasterjb]

I have this issue on fish in wsl2 ubuntu as well when trying to download x64 node versions...

I actually had this issue as well on Windows 10, but due to some non-related circumstances I've since updated to Windows 11 and for some reason I was able to use fnm install <NODE_VERSION> just fine.

I'm not suggesting this as a solution, there is clearly something wrong with fnm on Windows 10 w/ wsl2. Just so that fnm contributors can see as well @nikolalukovic , which Ubuntu release are you on?

[Livb-VRC]

still having this issue

[t-botz]

Same issue here. I am on WSL 2, Ubuntu 22.10, installed fnm with the standard script installation.
fnm ls-remote or any other command gives operation timed out.

curl'ing the url that time out for fnm works fine.
I am on zsh (shouldn't make any difference...).

[t-botz]

The operation timed out is definitely linked to musl. Same code base compiled for gnu, no problem, compiled for musl, timeout.

No idea why musl make it fail but I think compiling for musl is wrong (not needed and not well supported).

#882 Should fix this issue

[jmsherry]

This is still happening for me. (cURLing the URL for node distributions works)

Version: fnm 1.33.1
OS: Mac OS Ventura 13.1 (22C65)

fnm ls-remote

error: error sending request for url (https://nodejs.org/dist/index.json): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known