Not able to connect to atom.io for themes and packages

Question

I believe my work proxy is preventing me from being able to add themes and packages to Atom. From the preferences menu, I get:

Fetching featured packages and themes failed. Hide output…

tunneling socket could not be established, cause=140499728967552:error:140770FC:SSL  routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:766:

Is it possible to make it use my $https_proxy variable? Is there some way to configure it to not use https?

Answer 1

You can configure your proxy settings in ~/.atom/.apmrc (or Atom\resources\app\apm\node_modules\atom-package-manager\.apmrc in Windows). Per the apm README:

If you are using a proxy you can configure apm to use it by setting the https-proxy config in your ~/.atom/.apmrc file like so:

https-proxy = https://9.0.2.1:0

Answer 2

It seems that as of Atom 1.0, there are some components that respect the http-proxy and https-proxy variables, and others that don't. For example, the initial check for the version of Atom works, but the check for packages doesn't seem to respect the http-proxy or https-proxy settings.

I was able to get Atom working with Fiddler as my proxy (on 127.0.0.1:8888) by running the following commands (on Windows):

apm config set proxy http://127.0.0.1:8888
apm config set strict-ssl false

I did not need to set http-proxy or https-proxy. I don't know if these settings have been deprecated or not, but they don't seem to work reliably in 1.0. The setting proxy works (and upgrades itself to TLS 1.2 automatically).

The entirety of my %USERPROFILE%\.atom\.apmrc file is:

strict-ssl=false
proxy=http://127.0.0.1:8888/

Answer 3

I was getting this error on Windows 7 fro Atom 1.0, when trying to look up packages. In my case the issue was resolved by setting https-proxy variable to use http protocole instead of https. so both of the following parameters have exact same value.

here are the values from ~.atom.apmrc file

proxy=http://[host]:[port]/ https-proxy=http://[host]:[port]/

the answer by @NYCdotNet below that suggested to use

strict-ssl=false

didn't work as i was able to lookup some packages but installation failed with timeout error from GIT.