Accessing Github behind corporate proxy Node.js

Question

I am having an issue with calling the following command from cmd for installing PhoneGap:

npm install -g phonegap

The following error is returned:

Failed to connect to github.com port 443: Timed out

There are a fair amount of questions regarding this topic and they all seem to provide the same answer - make sure the proxy settings for git and nodejs are configured. I set up the node proxy settings like so:

npm config set proxy http://proxyname:8080
npm config set https-proxy http://proxyname:8080

And for git:

git config --global http.proxy http://proxyname:8080
git config --global https.proxy http://proxyname:8080

Both git config --list and npm config list confirm that these proxy settings are in place.

I have also allowed the programs through the fire wall by going to Windows Firewall -> Allow a program or feature through windows firewall. Then I selected the node.exe for Node.js and for git I selected git.exe.

I still however have the issue whereby it is failing to connect to Github. Is there anything else I am missing or forgetting to setup? Both Node.js and Git were installed for the first time for this task.

score 6 · Answer 1 · answered Jun 29 '15 at 11:45

6

In addition to the above settings, it's possible that you're getting this error if some of the downloaded libraries declare their dependencies using the git:// protocol instead of https://. These dependencies then usually fail with the above error.

To fix this, you can run the following:

git config --global url."https://".insteadOf git://

This will add a configuration option to Git, asking Git to use https whenever a URL uses the git:// protocol.

This setting fixed many proxy issues for me.

answered Jun 29 '15 at 11:45

nwinkler

52,665
21
154
168

Thanks a lot for the response, I just tried your suggestion however the issue remains. Strange... – Reece Kenney Jun 29 '15 at 12:37
There might be some more info here: http://stackoverflow.com/questions/783811/getting-git-to-work-with-a-proxy-server – nwinkler Jun 29 '15 at 12:49
awesome! oh lol i just see nwinkler from bash-it repo. bash-it-docker says hello and thanks for the answere :) – bin2hex Feb 08 '17 at 15:11
Solved my problem : behind a proxy, installing custom git repo, hanging at npm-session – aznoqmous Jun 15 '20 at 14:55

score 3 · Accepted Answer · answered Jul 11 '15 at 22:16

3

You need to add proxy authentication to your command application. I assume you are working in windows, the following works for me (I don't need to add the proxy to either npm or git unless running git commands).

In your active command window you need either or both of these for each session including initial instalation adding devices or plugins and on first application build:

set https_proxy=http://username:password@proxy:port

set http_proxy=http://username:password@proxy:port

So mine looks like this:

set https_proxy=http://john.doe:1234@proxy.det.nsw.edu.au:8080

Ben

answered Jul 11 '15 at 22:16

Ben Jones

504
4
18

1

This is it! Thank you so much! – Reece Kenney Jul 13 '15 at 12:19
i have '@' in my password.How can I put it using the command line in git bash? – Raulp Jan 25 '19 at 11:23
@Raulp no it won't parse correctly, you need to remove the "@" from your password – Ben Jones Jan 27 '19 at 23:09
1

@BenJones thanks it worked ! I had to replace @ with %40 – Raulp Jan 29 '19 at 15:08

score 0 · Answer 3 · answered Feb 05 '16 at 11:36

With git 2.8 (March 2016), you don't have to embed in clear text your password in the url.

See commit 372370f, commit ef97639 (26 Jan 2016) by Knut Franke (``).
Helped-by: Junio C Hamano (gitster), Eric Sunshine (sunshinebell28), and Elia Pinto (devzero2000).
^{(Merged by Junio C Hamano -- gitster -- in commit 30f302f, 03 Feb 2016)}

http: use credential API to handle proxy authentication

Currently, the only way to pass proxy credentials to curl is by including them in the proxy URL. Usually, this means they will end up on disk unencrypted, one way or another (by inclusion in ~/.gitconfig, shell profile or history).
Since proxy authentication often uses a domain user, credentials can be security sensitive; therefore, a safer way of passing credentials is desirable.

If the configured proxy contains a username but not a password, query the credential API for one. Also, make sure we approve/reject proxy credentials properly. So:

In addition to the syntax understood by curl, it is possible to specify a proxy string with a user name but no password, in which case git will attempt to acquire one in the same way it does for other credentials.
See gitcredentials for more information.
The syntax thus is:

[protocol://][user[:password]@]proxyhost[:port]

This can be overridden on a per-remote basis; see remote.<name>.proxy.

http: allow selection of proxy authentication method

CURLAUTH_ANY does not work with proxies which answer unauthenticated requests with a 307 redirect to an error page instead of a 407 listing supported authentication methods.
Therefore, allow the authentication method to be set using the environment variable GIT_HTTP_PROXY_AUTHMETHOD or configuration variables http.proxyAuthmethod and remote.<name>.proxyAuthmethod (in analogy to http.proxy and remote.<name>.proxy).

The following values are supported:

anyauth (default)

basic

digest

negotiate

ntlm

Accessing Github behind corporate proxy Node.js

3 Answers3

`http`: use credential API to handle proxy authentication

http: allow selection of proxy authentication method

Accessing Github behind corporate proxy Node.js

3 Answers3

http: use credential API to handle proxy authentication

http: allow selection of proxy authentication method

`http`: use credential API to handle proxy authentication