Site icon ni18 Blog

Fix npm Error Code UNABLE_TO_GET_ISSUER_CERT_LOCALLY

Nitin

Encountering the npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY error can feel like hitting a brick wall in your development workflow. As an expert software developer, I’ve seen this issue pop up often, especially when working behind corporate firewalls or on systems with tricky network configurations. But don’t worry—this guide will walk you through everything you need to know about this error in 2025, from what causes it to the safest and most effective ways to fix it. We’ll keep it clear, engaging, and optimized for search engines, so you can get back to coding fast.

What Is the npm UNABLE_TO_GET_ISSUER_CERT_LOCALLY Error?

The UNABLE_TO_GET_ISSUER_CERT_LOCALLY error happens when npm (Node Package Manager) can’t verify the SSL/TLS certificate of a server it’s trying to connect to, usually the npm registry (https://registry.npmjs.org). In simple terms, npm is saying, “I don’t trust this server because I can’t confirm its identity.”

This error typically shows up when you run commands like npm install, npm update, or npm publish. The error message might look something like this:

npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm ERR! unable to get local issuer certificate
npm ERR! request to https://registry.npmjs.org/<package> failed

It’s frustrating, but it’s usually caused by a hiccup in how your system handles SSL certificates. Let’s break it down and fix it step by step.

Why Does This Error Happen?

Before jumping to solutions, it’s worth understanding the root causes. This error is tied to SSL/TLS, the tech that keeps internet connections secure. When npm tries to fetch a package over HTTPS, it checks the server’s certificate to ensure it’s legit. If it can’t verify the certificate’s issuer (the Certificate Authority, or CA), it throws this error. Here are the most common reasons in 2025:

Understanding the cause helps you pick the right fix—and avoid breaking something else!

How to Fix npm UNABLE_TO_GET_ISSUER_CERT_LOCALLY Error

Let’s dive into the solutions, starting with the safest and most recommended approaches. I’ll also warn you about risky workarounds and explain why they’re not ideal for production environments. Follow these steps in order, testing after each one to see if the issue is resolved.

1. Update Node.js and npm to the Latest Versions

Outdated versions of Node.js or npm can struggle with modern SSL/TLS requirements. In 2025, Node.js and npm are regularly updated to handle certificate chains correctly.

  1. Check your current versions:
    bash node -v npm -v
  2. Update Node.js to the latest stable version (e.g., v20.x or v22.x as of 2025). Use a version manager like nvm for flexibility:
    bash nvm install node nvm use node
  3. Update npm globally:
    bash npm install -g npm@latest

2. Verify Your Network and Disable VPN (Temporarily)

If you’re behind a corporate firewall or using a VPN, it might be swapping certificates or blocking HTTPS traffic.

  1. Temporarily disconnect from your VPN (if safe to do so).
  2. Try running npm install on a different network (e.g., a personal hotspot) to isolate the issue.
  3. If you’re in a corporate environment, contact your network admin to confirm if a proxy like Zscaler is in use.

3. Add Your Company’s CA Certificate

If you’re behind a corporate proxy, it might use a custom certificate. You can tell Node.js to trust it by adding it to the trusted certificate store.

  1. Ask your network admin for the proxy’s root CA certificate (usually a .pem or .cer file).
  2. Set the NODE_EXTRA_CA_CERTS environment variable to point to the certificate:
    • Linux/macOS:
      bash export NODE_EXTRA_CA_CERTS="/path/to/your/cert.pem"
    • Windows (CMD):
      bash set NODE_EXTRA_CA_CERTS=C:\path\to\your\cert.pem
    • Windows (PowerShell):
      bash $env:NODE_EXTRA_CA_CERTS="C:\path\to\your\cert.pem"
  3. To make this permanent, add it to your .bashrc, .zshrc, or system environment variables.
  4. Alternatively, configure npm to use the certificate:
    bash npm config set cafile /path/to/your/cert.pem

4. Update System CA Certificates

Your system might be missing or have outdated CA certificates, especially on older Linux distributions or stripped-down environments.

5. Switch to HTTP Registry (Temporary Workaround)

If you can’t resolve the certificate issue immediately, you can tell npm to use the HTTP version of the registry instead of HTTPS.

  1. Set the npm registry to HTTP:
    bash npm config set registry http://registry.npmjs.org
  2. Run your npm command (e.g., npm install).
  3. After resolving the issue, switch back to HTTPS for security:
    bash npm config set registry https://registry.npmjs.org

6. Disable Strict SSL (Risky, Avoid in Production)

You can tell npm to skip strict SSL validation, but this is a temporary and insecure fix.

  1. Disable strict SSL:
    bash npm config set strict-ssl false
  2. Run your npm command.
  3. Re-enable strict SSL after fixing the issue:
    bash npm config set strict-ssl true

7. Disable TLS Rejection (Very Risky, Development Only)

As a last-ditch effort, you can disable TLS certificate validation entirely for Node.js.

  1. Set the NODE_TLS_REJECT_UNAUTHORIZED environment variable:
    • Linux/macOS:
      bash export NODE_TLS_REJECT_UNAUTHORIZED=0
    • Windows (CMD):
      bash set NODE_TLS_REJECT_UNAUTHORIZED=0
    • Windows (PowerShell):
      bash $env:NODE_TLS_REJECT_UNAUTHORIZED="0"
  2. Run your npm command.
  3. Re-enable validation afterward:
    bash export NODE_TLS_REJECT_UNAUTHORIZED=1

8. Clear npm Cache and Reset Configurations

Sometimes, a corrupted npm cache or misconfigured .npmrc file causes issues.

  1. Clear the npm cache:
    bash npm cache clean --force
  2. Check your .npmrc file for incorrect settings (located at ~/.npmrc or %USERPROFILE%\.npmrc):
    bash npm config list
  3. If you see a cafile or other suspicious settings, remove them:
    bash npm config delete cafile npm config delete registry npm config delete strict-ssl
  4. Reset to default settings if needed:
    bash npm config set registry https://registry.npmjs.org npm config set strict-ssl true

Best Practices to Avoid This Error in 2025

Once you’ve fixed the error, here’s how to keep it from coming back:

When to Contact Your Network Admin

If none of these solutions work, the issue is likely tied to your network setup. Reach out to your IT or network admin if:

They can provide the right certificates or adjust proxy settings to unblock npm.

FAQs About npm UNABLE_TO_GET_ISSUER_CERT_LOCALLY

Why does this error only happen at work?

It’s likely your company’s firewall or proxy is swapping SSL certificates to monitor traffic, which npm doesn’t trust by default.

Is it safe to disable strict SSL or use HTTP?

No, these are insecure and should only be used temporarily in trusted environments. Always revert to HTTPS and strict SSL for security.

Can I fix this without admin access?

Some fixes (like updating npm or clearing cache) don’t require admin rights, but adding CA certificates or updating system CAs might.

Does this error affect Yarn too?

Yes, Yarn uses similar SSL/TLS mechanisms and can hit the same issue. Most fixes here apply to Yarn as well.

Conclusion: Get Back to Coding with Confidence

The npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY error can be a pain, but it’s fixable with the right approach. By updating your tools, adding trusted certificates, or tweaking network settings, you can resolve it safely and securely. In 2025, staying on top of Node.js updates and working closely with your IT team will keep these issues at bay.

Got a stubborn case of this error? Drop a comment or check the resources below for more help. Now, go install those packages and build something awesome!

Resources

Exit mobile version