Apm: Cannot install packages due to "local issuer" certificate error

Created on 12 Apr 2018  路  7Comments  路  Source: atom/apm

I have a fresh install of Atom on Windows.

Atom : 1.25.1
Electron: 1.7.11
Chrome : 58.0.3029.110
Node : 7.9.0

I cannot install any additional packages due to certificates.

2018-04-12 10_42_44-settings atom

At work, we use Forcepoint for malware protection, and this software presents an FP HTTPS certificate instead of the original site's.

Preliminarily, following install instructions and doing a apm config set strict-ssl false, I am able to see "Featured Packages", but still cannot search Install Packages.

2018-04-12 11_09_50-settings c__users_ptiseo_ atom_ apm atom

Not sure what to do at this point, since official guides and posts on the forum don't seem to solve my specific issue. I feel I need to include the FP cert in a bundle somewhere, but don't know where.

Side note: I have Git separately on my system, and it is able to fetch.

Most helpful comment

I run into the same issue - however it appears to affect only the Atom UI part of it.
If i run apm search javascript in the terminal (powershell, in my case) it seems to work - and also installing using the command-line works.

All 7 comments

I run into the same issue - however it appears to affect only the Atom UI part of it.
If i run apm search javascript in the terminal (powershell, in my case) it seems to work - and also installing using the command-line works.

I am behind a corporate proxy and indeed the Atom UI part show the "local issuer" certificate error. But from command line the apm search and apm install is working correctly.

I am behind a corporate proxy and having the same issue. Funny enough the new proxy doesn't need any bash settings, so I can't really set any option to a proxy address.

Worth to mention that apm works just fine, it only fails when using the UI (Atom->Settings->Install)

Worth to mention that apm works just fine, it only fails when using the UI (Atom->Settings->Install)

I second this. Same issue. And same problem as @paulxtiseo. In Ruby on Windows, we solved this by adding my corporate's Certificate bundle in to the certificate chain.

APM searches and installs stuff fine. NPM searches and installs stuff fine. I thought I'd try to change the node version to my Node 13.x - didn't help.

If I could insert a pem or cer file and have it be used in the cert chain for the UI search and install, that'd be great!

In your init.coffee file you need to add this
process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0

Command to install the script has fixed the certificate issue ($ apm install script ).
Ref: https://hackernoon.com/setting-up-atom-as-a-python-ide-a-how-to-guide-o6dd37ff

Was this page helpful?
0 / 5 - 0 ratings