Atom编辑器安装插件报错：无法验证第一个证书，寻求解决方案

Hey there, I've run into this exact issue before when working behind a corporate proxy—super frustrating, right? Let's walk through the fixes step by step to get your Atom plugins installed smoothly:

1. Quick Test: Skip SSL Verification Temporarily #

If you just need to get that one plugin installed right now, you can bypass the certificate check for a single install command:

apm install emmet --no-verify-ssl

This works for one-off installs, but it's not ideal for long-term use.

2. Permanent Fix: Disable Strict SSL Validation #

To make the fix stick for all future plugin installs, update your apm and npm configs to turn off strict SSL verification:

• First, update apm's setting:

  apm config set strict-ssl false
  

• Then do the same for npm (since apm relies on npm's underlying config):

  npm config set strict-ssl false
  

Restart Atom after running these commands, and you should be able to search and install plugins without the certificate error.

3. More Secure Fix: Trust Your Proxy Certificate #

If you don't want to disable SSL entirely (which does carry minor security risks), you can configure apm and npm to trust your network's root certificate:

1. Locate your proxy's root certificate file (usually in .pem format).
2. Run these commands, replacing /path/to/your/certificate.pem with the actual file path:

   apm config set cafile "/path/to/your/certificate.pem"
   npm config set cafile "/path/to/your/certificate.pem"
   

This tells both tools to trust your network's certificate, so you don't have to turn off strict validation.

4. Double-Check Your Proxy Settings #

Sometimes the error pops up because of incorrect proxy configs. Let's verify and fix that:

• Check your current apm proxy settings:

  apm config get proxy
  apm config get https-proxy
  

• If you don't need a proxy (or the existing one is wrong), clear them:

  apm config delete proxy
  apm config delete https-proxy
  

• Repeat the same steps for npm:

  npm config delete proxy
  npm config delete https-proxy
  

A quick note: Disabling strict-ssl is convenient, but if you're on a corporate network, using the certificate trust method is the safer option.

内容的提问来源于stack exchange，提问作者Mark