Nvm-windows: nvm install node

[lxiaoixi]

Could not retrieve https://nodejs.org/dist/latest/SHASUMS256.txt.
Get https://nodejs.org/dist/latest/SHASUMS256.txt: net/http: TLS handshake timeout

Can you tell me how to solve it

[ankushgoyal27]

C:\WINDOWS\system32>nvm install 6.11.4 64

**Could not retrieve https://nodejs.org/dist/latest/SHASUMS256.txt.

Get https://nodejs.org/dist/latest/SHASUMS256.txt: dial tcp iPaddress:port: connectex: No connection could be made because the target machine actively refused it.**

This issue occurs on Windows10. Any suggestions.

Thanks,
Ankush

[nithinmohantk]

I too have the same issue persists in Windows 7.

[abhisdeshmukh]

Issue seems when working from behind office proxy. Set proxy before executing install command.
C:\WINDOWS\system32> nvm proxy http://proxy address : port

[LuisaFernandaArango]

You must remove the proxy

[shenqistart]

installation manual ->settings.txt ->enter node_mirror: http://tnpm.oa.com/mirrors/node/ npm_mirror: http://tnpm.oa.com/mirrors/

[js2me]

It is not solving that problem but solving problem with installing nodejs via nvm. May be it can helped to someone.

Manual installation:

• Download your nodeJs version from mirror https://nodejs.org/dist/
• Open nvm folder (on Win10 it is C:\Users\%USERNAME%\AppData\Roaming\nvm )
• Create folder and name it like this v{yourVersion} ( Example: v6.9.4 )
• Extract all files from folder which contains in downloaded acrhive into your folder from third step
  

• Open command line and install node with your version using nvm ( Example: nvm install 6.9.4 )
  

• And next step is set to use your node version nvm use 6.9.4
  

These steps are helped to me to install nodeJs ignoring company proxy

[coreybutler]

There's a chance this issue is occurring because the TLS/SSL certificate of the remote host expired, or it could have been issued by a distrusted CA that is no longer trusted (like certain Verisign CA's). This is a more common issue when using a public or private mirror, but it can happen when certificates are renewed too.

You can force NVM to bypass this using the --insecure flag, i.e. nvm install 6.9.4 --insecure:

[brrogers]

For my environment, all that is required is a system reboot. Then suddenly this is working again. Fails after a few days though. Curl and Google Chrome are both able to retrieve this file just fine when NVM has this issue. Seems like NVM could be caching the certificate and has issues after the site renews?

[vipra17]

For windows 10 nvm install 10.15.0 doesnt work. It gives the following error :
Get https://nodejs.org/dist/latest/SHASUMS256.txt: Parent proxy unreacheable
I tried setting nvm proxy but then it gives proxy authentication error.
Also I manually downloaded the version and placed it in C:\Users\xxx\AppData\Roaming\nvm\v10.15.0
Also i tried to set the node_mirror manually but dint help

[artyomilyin]

Can it be possible that you just forgot to enable nvm?
Try nvm on.

[coreybutler]

@vipra17 This sounds like an issue with your proxy. If you're getting a proxy authentication error, then something is either

1. Misconfigured in your proxy address
2. You don't actually have access
3. The credentials aren't being passed to the proxy or the proxy is expecting them in a different form.*

*For that last point: NVM4W is not currently designed to handle anything other than basic auth (it's more of a function of the native HTTP client than NVM4W). Some proxies do not respect the Authorization header sent in an HTTP request. Instead, they expect the Proxy-Authorization header or a custom alternative. NVM4W doesn't support this at the moment. Since Proxy-Authorization is a standard HTTP header, I would like to add support, but it has been a low priority (requires a custom HTTP client within NVM4W). I do not really have a good understanding of how many people are actually using proxies which require this kind of authentication. So, it's on the roadmap, but currently sitting near the bottom of my priority list.

[jovenbarola]

this works for me
nvm off
nvm proxy none
nvm on
nvm install <node_version>
nvm use <node_version>