-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
nvm install
not work
#3583
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
Comments
The curl command didn’t complete, unless perhaps the full output wasn’t provided? Also, what happens when you try to install node? |
the curl output is complete indeed. |
it looks like you're overriding the default node mirror source, and pointing to http://npm.taobao.org/mirrors/node - but that URL 404s. |
Thank u. After But as chinese users , we often use china mirrors to improve download speed. So if i want to use |
By the way, i have another pc, curl output is ❯ curl -I --compressed -v https://nodejs.org/dist/
* Uses proxy env variable no_proxy == '192.168.0.0/16,127.0.0.1,172.0.0.0/8,10.0.0.0/8'
* Trying 172.66.128.116:443...
* Trying 2606:4700:10::6814:306:443...
* Immediate connect fail for 2606:4700:10::6814:306: 网络不可达
* Trying 2606:4700:10::ac42:8074:443...
* Immediate connect fail for 2606:4700:10::ac42:8074: 网络不可达
* connect to 172.66.128.116 port 443 failed: 没有到主机的路由
* Trying 104.20.3.6:443...
* Connected to nodejs.org (104.20.3.6) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /usr/local/share/anaconda3/ssl/cacert.pem
* CApath: none
* 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: CN=*.nodejs.org
* start date: Mar 12 00:00:00 2025 GMT
* expire date: Apr 12 23:59:59 2026 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 multiplexing
* 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 0x55e5db1e99b0)
> HEAD /dist/ HTTP/2
> Host: nodejs.org
> user-agent: curl/7.78.0
> accept: */*
> accept-encoding: deflate, gzip
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 200
HTTP/2 200
< date: Fri, 09 May 2025 03:10:11 GMT
date: Fri, 09 May 2025 03:10:11 GMT
< content-type: text/html
content-type: text/html
< cache-control: public, max-age=3600, s-maxage=14400
cache-control: public, max-age=3600, s-maxage=14400
< last-modified: Fri, 09 May 2025 00:00:19 GMT
last-modified: Fri, 09 May 2025 00:00:19 GMT
< cf-cache-status: HIT
cf-cache-status: HIT
< age: 11282
age: 11282
< vary: Accept-Encoding
vary: Accept-Encoding
< strict-transport-security: max-age=31536000; includeSubDomains; preload
strict-transport-security: max-age=31536000; includeSubDomains; preload
< x-content-type-options: nosniff
x-content-type-options: nosniff
< server: cloudflare
server: cloudflare
< cf-ray: 93ce009b8cf47c21-LAX
cf-ray: 93ce009b8cf47c21-LAX
< content-encoding: gzip
content-encoding: gzip
<
* Connection #0 to host nodejs.org left intact I found |
To use a mirror, the mirror has to have the exact same structure as nodejs.org - a URL, followed by I'll close this, but if you find a correctly structured mirror and still have trouble, I'm happy to reopen this. |
Operating system and version:
nvm debug
output:nvm ls
output:How did you install
nvm
?What steps did you perform?
What happened?
can't install node
What did you expect to happen?
Is there anything in any of your profile files that modifies the
PATH
?If you are having installation issues, or getting "N/A", what does
curl -I --compressed -v https://nodejs.org/dist/
print out?The text was updated successfully, but these errors were encountered: