Error AtlasError Documentation and Resolution
Back to searchMore npm errors

npm

npm is behind an SSL-intercepting proxy

SSL-intercepting proxy

npm is encountering TLS and certificate problems because network traffic is being intercepted and re-signed by a proxy between the client and the npm registry.

SSL-intercepting proxynetworking

Observed message

SSL-intercepting proxy

Why it happens

  • A corporate or managed proxy is intercepting SSL traffic.
  • The proxy's certificate chain is not trusted by the npm client environment.
  • Registry TLS settings and local CA configuration do not match the inspected connection path.

How to fix it

  1. Confirm whether the network path includes an SSL-intercepting proxy.
  2. Configure npm to trust the appropriate CA chain if policy allows.
  3. Review proxy-specific configuration instead of only toggling strict SSL settings.

Official reference

npm Docs: Common errors

Related errors

npm only uses git: and ssh+git: URLs for GitHub repos, breaking proxiesnpm GitHub git and ssh URLs are breaking behind a proxyCERT_UNTRUSTED / UNABLE_TO_VERIFY_LEAF_SIGNATUREnpm SSL certificate is untrusted or leaf signature cannot be verifiedSELF_SIGNED_CERT_IN_CHAINnpm SSL self signed certificate in chainSSL23_GET_SERVER_HELLO:unknown protocolnpm SSL unknown protocol error

Explore more

npmBrowse more npm errorsnetworkingBrowse more networking errors
npm SSL-intercepting proxy problems: causes and fixes | Error Atlas