npm ERR! code ENOTFOUND — request to https://registry.npmjs.org/x failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
npm couldn’t resolve the registry hostname.
Exact message you may see
npm ERR! code ENOTFOUNDgetaddrinfo ENOTFOUND registry.npmjs.org
Seen on:
npm
Meaning
No internet, broken DNS, a wrong custom registry URL, or proxy settings needed.
Common causes
- Offline/DNS failure
- Typo in a custom registry URL
- Proxy required
⚡ Quick fix
- Check npm config get registry
- Test DNS: nslookup registry.npmjs.org
- Configure the proxy
Detailed fix by platform
npm
npm config get registry && npm config set registry https://registry.npmjs.org/
How to diagnose
- Registry — Correct URL?
- DNS — Resolves?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in npm
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026