Unable to install packages behind corporate proxy #322
Comments
|
Could you try running |
|
They seem fine to me and i haven't changed them between versions. |
|
Same here when trying to install |
|
Hmm, I see the command was spawned with Are either of you building Atom from source? I just added support for enabling verbose output from So if you build Atom yourselves and then ran |
|
Same problem here: Iam also behind a proxy |
|
For me this problem started today, Atom was updated to 0.189.0 (installed via webupd8 ppa) and when I tried to update my packages I got this error. |
|
Installing a new package with --verbose |
This comment has been minimized.
This comment has been minimized.
|
Getting this as well. Im behind a proxy and have correct config. I can browse packages from atom but install throws the gyp error. |
|
Same here. Can browse and search packages, but not install. The error is the same of everybody. Seems to me that this error is not because the proxy. Apm can search packages, which means that it's passing the proxy normally. Trying to install any packages and gyp gives a "Parse Error" as the cause of not being able to make the connection:
|
|
Same here. Seems like gyp forgets proxy after redirection. |
|
@fujisaks Can you detail how you got this to work? I'm on severly outdated packages now because I can't upgrade. |
|
@noseglid OK. Here is what I typed: It bypasses redirection and should make apm work until next atom-shell release. |
|
@fujisaks Thanks so much. I modified your command for linux and it worked. This is what I did (Ubuntu 14.04): |
|
Thanks @fujisaks Works like a charm here! The only thing I needed to change was the proxy. |
|
Thanks @fujisaks This fixes my issue #337. HOME=~/.atom/.node-gyp/ /usr/share/atom/resources/app/apm/bin/node /usr/share/atom/resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js "install" "--target=0.22.0" "--dist-url=http://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist" "--arch=x64" "--ensure" "--verbose" "--proxy=http://proxy:80" |
|
Thanks for the workaround guys, having the same problem here after coming back from vacation. So this issue has been around for a month now, any way to give this some priority? I know, only enterprises suffer from this problem, but not being able to install a single atom package kind of sucks. |
|
+1 (and referenced 2 other duplicates) |
|
I have been dealing with this issue for a week now and @fujisaks just saved me a total OS reinstall. I can confirm this is working for Windows 7 x64 also. Had to change the paths of course but it works. Here is the command I used using GIT BASH (won't work in CMD or Powershell without some work to update the paths but that should be easy) Make sure you replace the {...} with your username and proxy settings. HOME=/c/Users/{your_user}/.atom/.node-gyp/ /c/Users/{your_user}/AppData/Local/atom/app-0.192.0/resources/app/apm/bin/node /c/Users/{your_user}/AppData/Local/atom/app-0.192.0/resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js "install" "--target=0.22.0" "--dist-url=http://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist" "--arch=x64" "--ensure" "--verbose" "--proxy=http://{your_proxy}:{proxy_port}" |
|
Since atom 0.194.0 im unable to update packages through |
|
Seems that node-gyp isn't following the 302 Redirect sent by atom.io. @fujisaks Thanks for pointing to the problem! I've been able to workaround the issue by setting the ATOM_NODE_URL env variable to the new url (after redirect ). This should also be working after you update Atom. However, remove the entry when the bug gets fixed! Windows temporary: Windows permanently: Linux |
|
Thanks TedThiCo, this workaround worked for me (Win7x64). |
|
It looks like the root cause of this problem has not been pointed out. Here's what going on: It looks like that when supplied an https URL that returns a redirect to an http address, apm uses a CONNECT method on the proxy instead of issuing a GET. As expected, most proxies will reject this. |
|
❤️ @TedThiCo, that did the trick! |
|
@TedThiCo respect, It solved the problem. |
|
I have the same problem with the just-downloaded stable package under Windows 7 x64. NPM works, APM doesn't with the very same configuration. The output is: If I set I can download the requested url with Chrome. In my case |
|
As for my case, even the workaround I used stopped working. How about reopening the issue? |
|
I would like to confirm that the workaround (adding proxy info to .apmrc) doesn't work anymore since ATOM has been updated to 1.15. I believe reopening the issue is good idea. |
|
It also stopped working for me, but I can't remember if it was before or after I upgraded to Atom 1.15. My setup could be different, but FWIW I had to remove proxy info in my |
|
I have a local proxy (Cntlm) that redirects to my corporate proxy to solve authentication problems. And in my .apmrc config file: |
|
@nxtzero Did you set Cntlm on Windows? I tried it before on 0.93.2 but the it freezes most of the time. I couldn't update/install any Atom packages. (sad) |
|
I have version Cntlm 0.92.3 on Windows 7 (64 bits) with no problems. Just changed proxy, username, domain and password... Very rarely, like once a month, it crashes and I have to restart the service. I believe it is still the last version on Cntlm Authentication Proxy |
|
cntlm does not fix for me. I think the problem is the atom registry redirects to https even if asking for http. |
|
Is it possible to set the atm registry like you can with npm? |
|
@neclepsio Have you tried to set/unset Atom check on Settings > Core > Use Proxy Settings When Calling APM ? |
|
@nxtzero Yes. I always get "socket hang up". |
|
yep, same error behind a corporate proxy. |
|
I can confirm the same error on 1.15 not sure, but I believe it worked with cntlm before that version. |
|
1.16 has just been released. I could confirm that the workaround of setting proxy in .apmrc and environment variable works on Windows 10. Note that, "use proxy setting when calling APM" is disabled. It seems there is a regression in 1.15 release. |
|
would you please explain what you mean by "use proxy setting when calling APM" @wattachai? If use of apmrc can be controlled during runtime that would fix the issue for portable version. I'll be testing 1.16 momentarly. |
|
The portable installation (from ZIP file) still does not respect ENV variables on Windows and requires a use of .apmrc file inside .atom folder (and that file is not present there by default). |
|
@ethernal "use proxy setting when calling APM" is a setting you can find on setting page of atom itself.
Let me describe what I did. After that, package update worked but I couldn't see any package detail, no. of download or package thumbnail. Not giving up, I added a system environment variable: I will try to enable "use proxy setting when calling APM" without those workaround later with a hope that it would just work. (finger crossed) |
|
well this is good. but why apm can not supporting SSL checks? i have CA for the proxy and curl is working just fine when i point it to the right directory... |
|
+1 for this issue still existing... 407 error no matter that I try from this thread. |
|
407 means unauthorized. You need to provide your proxy with credentials. |
|
I've tried that as well as every other iteration in this thread. |
|
Chad try either cntlm or install on an other machine all u need and then
transfer everything onto the problematic on.
…On 27 Jul 2017 9:36 a.m., "chadflorian" ***@***.***> wrote:
I've tried that as well as every other iteration in this thread.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#322 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AExz3fXldtLuY8UkKOXclPqV3JAIY2fEks5sSJJDgaJpZM4DuUCu>
.
|
|
cntlm workaround works... but man.. what a PITA |
|
I hear you . Nobody wants to invest time to deal with proxies - no money ,
no fame.
…On 27 Jul 2017 10:42 a.m., "chadflorian" ***@***.***> wrote:
cntlm workaround works... but man.. what a PITA
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#322 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AExz3RfWqB7Fc9nCSEfP-Hf8kJXUoQTLks5sSKG6gaJpZM4DuUCu>
.
|
|
One solution that has worked for me. Install Fiddler on your machine, have it open and ensure Rules > Automatically Authenticate is set. Set your https-proxy to 127.0.0.1:8888 All traffic will then route via Fiddler and handle all NTLM negotiations. |
|
The comment by gabo2000git (Sep 6, 2016) helped |
|
I have read and tried to reproduce a few links similar to the following: But so far without results. However Rstudio does it perfectly!!! |
and others
I get the following error when trying to install a package with apm behind a corporate proxy.
All proxy settings should be correct and it worked perfectly in earlier versions.
The text was updated successfully, but these errors were encountered: