Nvm-windows: Unable to connect to hard-coded nodejs.org
This appears to be a result of the hard-coded url for the Node SHA256 file being hosted behind CloudFlare. The DNS resolves to a CloudFlare IP address (below), which does not support direct connections. Thus nvm cannot download a list of node versions and crashes.
I am not sure how to work around this, or if it is even possible from the nvm end. Is this an artifact of being behind a proxy?
$ nvm install 0.10.4
Could not retrieve http://nodejs.org/dist/latest/SHASUMS256.txt.
Get http://nodejs.org/dist/latest/SHASUMS256.txt: dial tcp 104.20.22.46:80: ConnectEx tcp: No connection could be made because the target machine actively refused it.
corsairmarks
>All comments
Looks like the issue was caused by a lack of proxy configuration.
For anyone else experiencing this issue:
Be sure to set your proxy url with nvm proxy <myurl> before attempting nvm install - it does not pick up on system settings. This may be a feature of the Go language and not an issue with nvm-windows specifically.
corsairmarks
on 12 Oct 2015
👍8
😄3
Was this page helpful?
0 / 5 - 0 ratings
Related issues
keylowgee
路
6Comments
thany
路
4Comments
SufyanParkar
路
4Comments
hsali
路
4Comments
martijnsenden
路
3Comments
Most helpful comment
Looks like the issue was caused by a lack of proxy configuration.
For anyone else experiencing this issue:
Be sure to set your proxy url with
nvm proxy <myurl>before attemptingnvm install- it does not pick up on system settings. This may be a feature of the Go language and not an issue withnvm-windowsspecifically.