npm ERR! code SELF_SIGNED_CERT_IN_CHAIN — request to https://registry.npmjs.org/ failed, reason: self signed certificate in certificate chain
A corporate proxy or antivirus is intercepting HTTPS, and npm doesn’t trust its certificate.
Seen on:
npm
Meaning
Point npm at the company root CA instead of turning strict-ssl off.
Common causes
- Corporate SSL inspection
- Antivirus HTTPS scanning
- Private registry with internal CA
⚡ Quick fix
- npm config set cafile /path/to/corp-root.pem
- Or set NODE_EXTRA_CA_CERTS for Node processes
- Avoid strict-ssl=false except temporarily
Detailed fix by platform
npm
npm config set cafile /etc/ssl/certs/corp-root.pem
How to diagnose
- Network — Proxy/inspection present?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🧠 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.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026