-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[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. #1133
Comments
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.
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. 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:
I installed the node.js versions now manually thats why I have now "Total Node.js Versions: 7" ;) |
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. |
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 |
The problem is Can you run |
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. |
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 ( 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). |
What happened?
I cant install any node,js version (tried 21,20,19,18). I tried also 1.1.11 and 1.1.10 of nvm. See error output beneath.
If i install nvm in the same LAN on my laptop it works... Also with Windows Firewall off, it doesn't work on my Workstation...
and i also have no proxy active or any kind
if i manually open "https://nodejs.org/dist/latest-v18.x/SHASUMS256.txt" in a browser it shows me the list of versions....
What did you expect to happen?
installing node.js version
Version
1.1.11 or newer (Default)
Which version of Windows?
Windows 10 (Default)
Which locale?
Western European
Which shell are you running NVM4W in?
PowerShell
User Permissions?
Administrative Privileges, Elevated
Is Developer Mode enabled?
No (Default)
Relevant log/console output
No response
Debug Output
Anything else?
No response
The text was updated successfully, but these errors were encountered: