[Issue]: Get "https://nodejs.org/dist/latest-v18.x/SHASUMS256.txt": write tcp 10.0.0.10:59499->104.20.22.46:443: wsasend: An existing connection was forcibly closed by the remote host. about nvm-windows HOT 10 OPEN

I think the root cause is spelled out in the debug function. The bottom line is your environment cannot connect to nodejs.org. You stated you're using admin/elevated privileges, but the debug console states otherwise.

This line suggests you're behind a proxy.

Get "https://nodejs.org/dist/latest-v18.x/SHASUMS256.txt": write tcp 10.0.0.10:59499->104.20.22.46:443: wsasend: An existing connection was forcibly closed by the remote host.

Are you sure there is no proxy? Remember, even though you may not have a proxy setup on your computer, that doesn't mean there isn't a corporate proxy blocking traffic.

from nvm-windows.

I think the root cause is spelled out in the debug function. The bottom line is your environment cannot connect to nodejs.org. You stated you're using admin/elevated privileges, but the debug console states otherwise.

This line suggests you're behind a proxy.

Get "https://nodejs.org/dist/latest-v18.x/SHASUMS256.txt": write tcp 10.0.0.10:59499->104.20.22.46:443: wsasend: An existing connection was forcibly closed by the remote host.

Are you sure there is no proxy? Remember, even though you may not have a proxy setup on your computer, that doesn't mean there isn't a corporate proxy blocking traffic.

thanks for the response.

nodejs.org is reachable via browser. Also "https://nodejs.org/dist/latest-v18.x/SHASUMS256.txt" as mentioned.
im in my private LAN, and i have full control over all my networking. In fact i made it all by self. So i know im not behind a proxy. i checked also windows, there is no proxy no firewall active.

And as said my laptop is in the same network and there it works, but my laptop has windows 11. this computer here has windows 10.

Same problem also with admin powershell:

Running NVM for Windows with administrator privileges.

Administrator: Windows PowerShell
Windows Version: 10.0 (Build 19045)

NVM4W Version:      1.1.12
NVM4W Path:         C:\Users\flow\AppData\Roaming\nvm\nvm.exe
NVM4W Settings:     C:\Users\flow\AppData\Roaming\nvm\settings.txt
NVM_HOME:           C:\Users\flow\AppData\Roaming\nvm
NVM_SYMLINK:        C:\Program Files\nodejs
Node Installations: C:\Users\flow\AppData\Roaming\nvm

Total Node.js Versions: 7
Active Node.js Version: v18.20.2

IPv6 is enabled. This can slow downloads significantly.

PROBLEMS DETECTED
-----------------
Connection to nodejs.org cannot be established. Check your proxy (none) and your physical internet connection.

I installed the node.js versions now manually thats why I have now "Total Node.js Versions: 7" ;)

from nvm-windows.

I'm not sure what to say, because NVM4W doesn't do anything special when it comes to network requests. It issues standard HTTP requests for downloads, and that's it. I'm not aware of anything specific to Win10 vs Win11 that would cause this type of issue... and I know it works on Win10.

I suppose firewalls could play a factor, but you said you didn't have a firewall enabled. I'm not sure why nodejs.org would forcibly close the connection, but it looks like it is indeed nodejs.org (remote host) closing the connection (not NVM4W).

I can't really see anything in the info provided hinting that NVM4W can actually do anything about this... especially if it is working on another machine.

from nvm-windows.

I thought about maybe is the error misleading or wrong, and it happens something different in the background.

look this issue #1123 he had the same error and it was something different than a connection issue.

well i will dive deeper with my opensense and track the connection

from nvm-windows.

ok the connection is perfect there is no issue... so i assume there is no problem going on on the network level..

from nvm-windows.

The problem is An existing connection was forcibly **closed by the remote host**., meaning nodejs.org is closing the connection. NVM4W doesn't control that.

Can you run nvm ls available? This makes a request to a different endpoint on nodejs.org.

from nvm-windows.

The problem is An existing connection was forcibly **closed by the remote host**., meaning nodejs.org is closing the connection. NVM4W doesn't control that.

Can you run nvm ls available? This makes a request to a different endpoint on nodejs.org.
ah yeah you're right

i tried your hint, same result :(

PS C:\Users\flow> nvm ls available

Could not retrieve https://nodejs.org/dist/index.json.

Get "https://nodejs.org/dist/index.json": write tcp 10.0.0.10:52879->104.20.22.46:443: wsasend: An existing connection was forcibly closed by the remote host.

from nvm-windows.

Something has to be happening on the network (including the remote end) to cause nodejs.org to close your connection. The code for downloading the index.json file is here (req, err := http.NewRequest("GET", url, nil). It's a standard Go HTTP request with absolutely nothing special about it. We can't get any more fundamental than that in Go. Plus, I can't recreate this error and I haven't seen anyone else post anything like this.

Ultimately, I don't think this is NVM4W issue. Since it works on one machine and not the other, I would recommend using something like Wireshark on both machines to compare the successful requests to the failed ones (to nodejs.org).

from nvm-windows.