-
Notifications
You must be signed in to change notification settings - Fork 6.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
Web Server not bound to IPv6 address #244
Comments
could you try again please @thedufer, they should be good to go now |
I'm seeing the same issue. After a curl, it just hangs trying to connect:
Eventually it just times out. Both http and https work with the |
Fails directly for me (http and https),
curl 7.30.0 (x86_64-apple-darwin13.0) libcurl/7.30.0 SecureTransport zlib/1.2.5 |
Works for me
curl 7.26.0 (x86_64-pc-linux-gnu) libcurl/7.26.0 OpenSSL/1.0.1e zlib/1.2.7 libidn/1.25 libssh2/1.4.2 librtmp/2.3 |
Ah, sorry. Works for me as well, IPv6 was disabled on my local router. 😓 |
@thedufer Can you please check if the problem is fixed for you, so we can close this issue? |
Sorry for the slow response. Yeah, it looks better now. I think my most recent comment was after running while I was on a VPN that doesn't play nicely with IPv6, so that may have been a false negative. |
nodejs.org is advertising both IPv4 and IPv6 addresses:
However, connections to the IPv6 addresses simply hang until the client times out. This means that remote
nvm
commands, whencurl
chooses to try v6, take a minimum of 2 minutes. This is true of the newestnvm
(0.29.0).The text was updated successfully, but these errors were encountered: