Proxy settings are not respected in some places

[izuzak]

Noticed two Halp tickets about this so far:

• support/a10f96d4b08f11e3934b3dfc0d230d46
• support/45b5441aa86911e39c8bef69aceed9d5

Finally, I didn't find any way to set my proxy info in the settings of your app, and I'm not sure you are respecting the proxy settings of the OS. So my first attempt to send feedback failed.

...

I tried to submit this via the built-in feedback but it didn't say it was successful, it seemed to time out just like fetching packages or themes:
Built-in package and theme fetching doesn't work when proxies are required. "Fetching featured packages and themes failed. connect ENETUNREACH". DNS resolves on this corporate network, but connections must use http or https proxies.
Self-updating Atom itself works.

So, it seems that proxy settings are not respected, and it's not possible to set them in Atom.

[Khoulaiz]

The same is true for the linux version. I've set my proxy via environment variables following the format: http://user:password@proxy.fully.qualified:port (for https, too), but I get

Fetching featured packages and themes failed.
tunneling socket could not be established, cause=Parse Error

[Karunamon]

Worth mentioning that I can't work around this with tsocks either. We go from ECONNREFUSED to tunneling socket could not be established, cause=socket hang up

[probablycorey]

Based on this issue electron/electron#183 it looks like we have to manually set the proxy for all node calls. Is this correct @zcbenz?

[zcbenz]

Yes, manually setting proxy for node calls is required.

[pritambaral]

Relevant upstream PR: request/request#844

[aldanor]

request/request#844 has been merged in a while ago, any updates on setting proxies in Atom?

[muescha]

on windows:

add in Atom\resources\app\apm\node_modules\atom-package-manager\.apmrc this line (host and port obfuscated):

http-proxy = http://1.2.3.4:1234 

atom also not respect this line

note if i setup an environment variable then it works:

rem -- File: atom.bat
set HTTP_PROXY=http://user:pass@server.url:port
atom.exe

[lijunle]

I don't think apm has leverage the merge request/request#844, which is merge on July 8. But apm is still using request 2.30 (which is release Dec 14, 2013)

[duncanmapes]

this works in the .apmrc for me, thanks @lijunle
proxy = http://HOST:PORT
strict-ssl = false

[tatsuyafw]

👍

[windgaucho]

@duncanmapes Thanks!! this work for me too

[JPvRiel]

@duncanmapes strict-ssl = false implies being insecure and not validating TLS?

[damieng]

Atom automatically sets the environment variables when calling out to apm itself in 1.14 and beyond.

[tiankongmumian]

My problem is still unsolved！！！

[damieng]

Please open a new issue with the details necessary to investigate.

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!