Is there any proxy settings?


#62

Could you please elaborate on your CNTLM configuration ? I set it up and it works for wget but not with apm :
Request for package information failed: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND (5 attempts) (ECONNRESET)


#63

For basic configuration, you only need to set this configuration

Username yourusername
Domain yourdomain
Password yourpassword
Proxy yourproxy


#64

I have put the proxy settings ( HTTP_PROXY and HTTPS_PROXY ) in .bash_profile and restarted terminal. Then tried ATOM and it worked.


#65

On Linux and with proxychains4, to install a package via proxy, following would do:

proxychains4 apm install atom-beautify


#66

Thanks bro… it’s working just fine


#67

This works fine in the last version {1.12.3}

$ apm config set https-proxy https://user:password@domain:port


#68

Is there an apm log I can check to see what it’s trying to connect to?

I’m behind a Websense proxy and even with correct proxy settings apm is failing with…

“Peer disconnected after first handshake message: Possibly SSL/TLS Protocol level is too low or unsupported on the server”

Cursory research suggests the Websense proxy may not be configured to support the TLS protocol used by whatever apm is trying to connect to, but the HTML error message displayed by apm doesn’t even indicate what url it is trying to connect to that has failed, which makes it impossible to progress towards a solution.


#69

On Windows 7 I did the following to make it work,

Inside the atom.cmd file located under ~\AppData\Local\atom\bin i added

@echo off
set HTTP_PROXY=http://:
"%~dp0…\app-1.12.7\resources\cli\atom.cmd" %*

Then I launched atom using this cmd


#71

The .apmrc file already exists in my Win7 installation. After adding those lines, saving the file and restarting Atom, the .apmrc file is overwritten back to its default state (the lines are removed).


#73

I have also been using CNTLM for authenticating through our corporate proxy for installing npm packages, among other things. I’m currently writing up my experience using CNTLM and I won’t go into it here but its pretty straight forward to install and configure.

If, like me you are already using CNTLM for npm then the .apmrc proxy configuration is the same as .npmrc proxy configuration. Basically, create the file C:\Users_username_.atom.apmrc and add your cntlm proxy details

This is how my .apmrc looks in my (now) working configuration.

proxy=http://localhost:3128
https-proxy=http://localhost:3128

My cntlm instance lives on my local host and listens on port 3128


#74

If your Username or Password contains any characters that need to be URI encoded, you will need to do that manually.

Here is an example
if your username was Universe\Jonathon.Mckay
your password was P@ssword!
your proxy url was 10.35.28.14:8080

then your .apmrc configuration would look like this
proxy=http://Jonathon.Mckay:P%40ssword!@10.35.28.14:8080/


#75

In Windows 7 I opened the cmd apm config edit
I added a new line proxy=http://proxy.com:80/, I didn’t set https-proxy
Restarted Atom and it worked.


#76

In some corporate environments, the proxy is configured is some way that secure connections can go through but are intercepted back and prevent from getting the response from server.
I do believe I’m in this case, and this also explain why
strict-ssl=false
or
http-proxy=http://proxy.bloomberg.com:80
doesn’t work. Regadless the config I put in the .apmrc file, the request sent is still over SSL, while I’d need the request to go though http only. That way, http communication can go through proxy and captured by the program.
I’ll keep looking at finding a way to do that, but if anyway can point me in this direction, thanks in advance!


#77

I finally went for the offline installation mode and followed this procedure.
Pretty neat. Enjoy


#78

Is there an easier way to do this these days or are we still having to manually edit files somewhere on our system?


#79

I’m having trouble with the Hydrogen package. I’ve read quite some threads about proxys and tried the solutions from apm’s README, but I still can’t get the package to install.

Initially I was getting an error concerning proxy but after fiddling around with the .apmrc file I now get this error:

Request for package information failed: tunneling socket could not be established, cause=getaddrinfo EAI_AGAIN host:80 (5 attempts) (ECONNRESET)

Now, I don’t know anything about proxys, so I’m not sure exactly what I have to type to make this work. apm’s README says one should type this:
apm config set https-proxy https://9.0.2.1:0
but it didn’t work. In this thread I read about different approaches. How can I get my proxy’s port and address?

I’m on Ubuntustudio 17.10 (beta, but I think it’s quite possible that the beta situation here is not really the problem).
Thanks!


#80

Apparently my home router had a firewall which I disabled and the package installed fine. Sorry for the noise…


#81

Hi there,

Í can’t install packages.
Using Win10, working from behing a company firewall and proxy.
Can’t find my mistake, please give me hand:

My Settings:
proxy=http://myproxy.local:1234/:8080
http-proxy=http://myproxy.local:1234/:8080
https-proxy=https://myproxy.local:1234/:8080
strict-ssl=false

Result when trying to install a package:

Searching for “emmet” failed.Hide output…
tunneling socket could not be established, cause=socket hang up

What does it indicate?

cheers Peter


#82

What if the password contains special characters like “!#$%^&”?


#83

Dear All,

I really like Atom.
Well… I’d really like it until I have to work behind a proxy.

Be it on a windows machine or an (L)Ubuntu one, I cannot make it work.
My proxy configuration works well for anything else but Atom.
In other words, the proxy configuration is correctly set in /etc/environment, as far as my Ubuntu box is concerned.
Even though I have run apm config and the ~/.atom/.apmrc file actually contains the proxy configuration and strict-ssl=false.
I still have the famous :
unable to get local issuer certificate
error.

This is really an annoying showstopper point for the use of Atom in a secured environment.
Or perhaps have I missed something ?

Best Regards
J-L