nvm: curl to install nvm does not work on Windows 10 WSL
Operating system and version:
Windows 10 1903 Ubuntu 18.04
nvm debug output: N/A
nvm ls output: N/A
How did you install nvm?
Curl
What steps did you perform?
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash
What happened?
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 13527 100 13527 0 0 11263 0 0:00:01 0:00:01 --:--:-- 11263
=> Downloading nvm from git to '/home/sachit/.nvm'
=> Cloning into '/home/sachit/.nvm'...
fatal: unable to access 'https://github.com/nvm-sh/nvm.git/': Could not resolve host: github.com
Failed to clone nvm repo. Please report this!
Also ‘command -v nvm’ returns nothing
What did you expect to happen?
Successful installation
Is there anything in any of your profile files that modifies the PATH?
No, .bashrc exists but PATH is not modified inside it
If you are having installation issues, or getting “N/A”, what does curl -I --compressed -v https://nodejs.org/dist/ print out?
* Trying 104.20.23.46:443...
* TCP_NODELAY set
* Connected to nodejs.org (104.20.23.46) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: OU=Domain Control Validated; OU=PositiveSSL Wildcard; CN=*.nodejs.org
* start date: Oct 21 00:00:00 2019 GMT
* expire date: Jan 18 23:59:59 2022 GMT
* subjectAltName: host "nodejs.org" matched cert's "nodejs.org"
* issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x5618f18d1800)
> HEAD /dist/ HTTP/2
> Host: nodejs.org
> user-agent: curl/7.68.0
> accept: */*
> accept-encoding: deflate, gzip, br
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 200
HTTP/2 200
< date: Thu, 14 Jan 2021 14:39:34 GMT
date: Thu, 14 Jan 2021 14:39:34 GMT
< content-type: text/html
content-type: text/html
< set-cookie: __cfduid=d7266bfeb96e95e60a3988ddfc09953531610635174; expires=Sat, 13-Feb-21 14:39:34 GMT; path=/; domain=.nodejs.org; HttpOnly; SameSite=Lax
set-cookie: __cfduid=d7266bfeb96e95e60a3988ddfc09953531610635174; expires=Sat, 13-Feb-21 14:39:34 GMT; path=/; domain=.nodejs.org; HttpOnly; SameSite=Lax
< cache-control: max-age=14400
cache-control: max-age=14400
< cf-cache-status: HIT
cf-cache-status: HIT
< cf-request-id: 07a2ef7a9e0000125a4a081000000001
cf-request-id: 07a2ef7a9e0000125a4a081000000001
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< vary: Accept-Encoding
vary: Accept-Encoding
< server: cloudflare
server: cloudflare
< cf-ray: 61181b70f82c125a-DXB
cf-ray: 61181b70f82c125a-DXB
< content-encoding: br
content-encoding: br
<
* Connection #0 to host nodejs.org left intact
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (8 by maintainers)
One possibility is that you have ipv6 enabled. Could you try disabling it?