getaddrinfo EAI_AGAIN registry.npmjs.org error while npm install

[RakeshInfy]

npm install not working when trying to install typescript or angular-cli.
PFB some error logs from npm-debug file

163 verbose request no auth needed
164 info attempt registry request try #1 at 4:52:55 PM
165 http request GET https://registry.npmjs.org/zone.js
166 info retry will retry, error on last attempt: Error: getaddrinfo EAI_AGAIN registry.npmjs.org:443
167 info retry will retry, error on last attempt: Error: getaddrinfo EAI_AGAIN registry.npmjs.org:443
168 info retry will retry, error on last attempt: Error: getaddrinfo EAI_AGAIN registry.npmjs.org:443
169 info retry will retry, error on last attempt: Error: getaddrinfo EAI_AGAIN registry.npmjs.org:443

[thataustin]

getting the same error just now when I run npm install from a Docker container. Funny thing is that it's not happening on my local machine (mac) when I run it for the same package.json.

[legodude17]

Do you have a stable internet connection? Do you have a proxy or VPN?

[thataustin]

Ok, so I walked to a local coffee shop and now it's working. I think the problem was with the DNS settings at the place I was working. Talked to the Network admin and he said he changed some stuff recently. It was right around the time he changed it last night that I started having issues. I'm going to withdraw my issue here. I think that whatever he did interfered with my Docker container's network settings.

[RakeshInfy]

@legodude17 I am on corporate proxy.pac

[legodude17]

Does it work without the proxy?

[MuhammadTaha]

try explicitly update the package.json file in dist as well as in the root

[ackvf]

Got this error on hyper-v virtual machine. Disabling "IPsec task offloading" in the Network Adapter, Hardware Acceleration tab did the job.

[blafasel-cc]

Get still the same here. It turns out to be an issue at fastly.com. registry.npmjs.org is only reached through fastly's reverse proxies. Which proxy you get is decided by a geolocation based DNS strategy.

All DNS servers seam to have the same CNAME record for registry.npmjs.org: a.sni.fastly.net. But for a.sni.fastly.net my telco providers DNS server gives me 151.101.12.162 while google's 8.8.8.8 gives me 4 totally different addresses.

If I stick to my telco's server the error occurs reproducibly. If I configure 8.8.8.8 everything works fine. This also makes the influence of proxy settings plausible.

[spaced-out-mvc]

I was having the same problem just now, i guess its a dns lookup which is failing.
i added this line to /etc/hosts and it now works perfectly in a split second.

151.101.16.162 registry.npmjs.org

I guess this fixes a major dns issue as now it installs npms blazing fast.
I wonder if this could help with github / composer by adding the github ip address as well.

I think when package installers do so many dns lookups it probaly times out.
so its best to set it manually in /etc/hosts if you have this type of problem happening.

Thanks
Daniel

[spaced-out-mvc]

So why stop there i say lol...

151.101.16.162 registry.npmjs.org
192.30.253.113 github.com
104.192.143.1 bitbucket.org
87.98.253.214 packagist.org

p.s. double check the ip address as some sites have regional cloud servers / load balancers

[louisdauvois]

Restart computer worked for me