You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These days I have encounter a problem which is related to IPv4 & IPv6, here is the problem:
Commands like npm publish or npm view will fail with error connection timeout (connecting to IP of IPv4 of registry.npmjs.org) after default timeout (5 mins)
DNS resolving works normally, returns IPv4 IPs and IPv6 IPs
ping <IPv4 IP> works
curl -4 https://registry.npmjs.org always timed out
curl -6 https://registry.npmjs.org works
I understand that this is a network issue, not a bug, but I wonder if there is a possibility to add an option like ipv6Only to make npm-registry-fetch and npm only use IPv6 in certain conditions.
If it sounds reasonable, I can make a PR.
Thanks.
The text was updated successfully, but these errors were encountered:
These days I have encounter a problem which is related to IPv4 & IPv6, here is the problem:
npm publish
ornpm view
will fail with error connection timeout (connecting to IP of IPv4 of registry.npmjs.org) after default timeout (5 mins)ping <IPv4 IP>
workscurl -4 https://registry.npmjs.org
always timed outcurl -6 https://registry.npmjs.org
worksI understand that this is a network issue, not a bug, but I wonder if there is a possibility to add an option like
ipv6Only
to makenpm-registry-fetch
andnpm
only use IPv6 in certain conditions.If it sounds reasonable, I can make a PR.
Thanks.
The text was updated successfully, but these errors were encountered: