Getting Git to work with a proxy server - fails with "Request timed out"

Question

How do I get Git to use a proxy server?

I need to check out code from a Git server, but it shows "Request timed out" every time. How do I get around this?

Alternatively, how can I set a proxy server?

Comprehensible

Wouldn't this be a git client configuration item? The only aspect of this that seems like would involve cmd.exe is that the git client may allow you to specify a proxy in an environement variable. – Mothball

I have edited the original question to remove all Windows references, as this problem is git-specific per se. – Comprehensible

Note that you will be able toon to setup a proxy per git repo url! – Desk

This question is very similar to "How do I pull from a Git repository through an HTTP proxy?". – Farrison

Most of the answers in this question go about HTTP proxies. If you have a SOCKS proxy, see this question for the HTTP/S protocols and this one for the git:// protocol. – Sothena

Duplicate foud stackoverflow.com/questions/128035/… – Baldheaded

Another reason is a DDoS attack (I don't think it is covered in the existing answers). It is a merge candidate. – Queri

Answer 1

The command to use:

git config --global http.proxy http://proxyuser:[email protected]:8080

• change proxyuser to your proxy user
• change proxypwd to your proxy password
• change proxy.server.com to the URL of your proxy server
• change 8080 to the proxy port configured on your proxy server

Note that this works for both HTTP and HTTPS repositories.

If you decide at any time to reset this proxy and work without proxy:

The command to use:

git config --global --unset http.proxy

Finally, to check the currently-set proxy:

git config --global --get http.proxy

Jennelljenner

Thanks Salim. Mine worked without the proxyuser:proxypwd in the URL. – Elastin

Noy at all Kwex, we're welcome. RedX your proposal is more convinient so I add your answer to the post – Jennelljenner

Thanks,guys. For me it was NTLM based authentication and just updating my .gitconfig didn't work :( . So I had to get CNTLM which uses NTLM authetication. All I had to do was point my CNTLM to my network's proxy server and then point my software update manager(like yum,apt-get or ssh) to the local proxy. In case of git operations like clone,pull the http.proxy was my locally configured proxy with the local server. – Shipe

@SalimHamidi I'm using TOR for proxy. there is no username or special link! or even password! What can i do? – Delaney

@Johan Karlsson can this help you ?: stackoverflow.com/questions/10274879/… – Jennelljenner

In my case, it didn't work until I tried removing http:// for both http and https. – Bricker

For me, the (non global) proxy settings were old and were shadowing the global settings. Not until I did git config --unset https.proxy and git config --unset http.proxy did it work – Rendering

use git config --local http.proxy http://... to store the proxy information in the current git repository. This is useful if you need to use the proxy only for some repositories. – Reindeer

Hello, how can I set proxypass if it have "@" character? I know I must scape this character but I don't know how.. Thank you – Baptist

How to specify hosts that Git should not route through the proxy? – Rubino

Did not work on my Ubuntu 14.04. The corkscrew solution below worked for me. – Germinant

@Baptist You can use %40 as a replacement for the @ in username/ password string, though I've not tested this myself. Hope it helps. :-) – Commensurate

Something that worked first time... I'm struggling to come to terms with that. Makes a refreshing change. – Fann

@Baptist I can confirm that using %40 as a replacement for @ works. It seems if a special character isn't working you should try URL encoding it. The encodings are found here: w3schools.com/tags/ref_urlencode.asp – Loudish

looks like setting https.proxy does not work, but if you set http.proxy then https repositories accessing work – Woody

@Sergei is right in his comment. There is no documentation of https.proxy in the git-config(1) manual. It doesn't work. The http.proxy is the only documented option for HTTP proxy that works for both HTTP and HTTPS clone URLs. – Captivity

If you're getting "self signed certificate in certificate chain" errors, set http.sslVerify to false in the configuration – Pretty

I have to point out that using --global when you are using username@password is a bad idea as you are then letting every other user of the machine use your username & password. Use --user for any "global" setting that are specific to a user and --local for any that are specific to the checked out repo that you are currently in the directory for omitting the scope implies --local but it is nice to be specific. – Psychopathy

in addition to @Steve Barnes' comment the gitconfig or .gitconfig file will save what you entered in plaintext: including your network username and password – Grudge

You may need to add the domain in the form DOMAIN\\proxyuser:[email protected]:8080 – Mihrab

You might want to use the proxy system-wide for git. git config --system http.proxy proxyuser:[email protected]:8080 I had to use it to set up git for Checkmarx. – Leffert

If you are in a Linux machine, simply setting the environment variable should work, like the one I did on this page: note.tianhaoz.com/linux-tricks/bashrc.html – Hendeca

This is the easiest way to config proxy. – Esemplastic

I had to add git config --global http.sslVerify false afterwards. – Crematory

Does anyone know if this passes your Username:Password as plain text in the HTTP/S request? (Is git sending http requests or https requests to my proxy?) – Tardiff

the proxy address may not always be HTTP protocol, In my case, I use socks protocol, so git config --global https.proxy 'socks://127.0.0.1:1088' works for me – Chancechancel

Answer 2

This worked for me, in Windows XP behind a corporate firewall.

I didn’t have to install any local proxy or any other software besides git v1.771 from http://code.google.com/p/msysgit/downloads/list?can=3

git config --global http.proxy http://proxyuser:[email protected]:8080
git config --system http.sslcainfo /bin/curl-ca-bundle.crt
git remote add origin https://mygithubuser:[email protected]/repoUser/repoName.git
git push origin master

proxyuser = the proxy user I was assigned by our IT department. In my case, it is the same Windows user I use to log in to my PC, the Active Directory user.

proxypwd = the password of my proxy user

proxy.server.com:8080 = the proxy name and port, I got it from Control Panel, Internet Options, Connections, LAN Settings button, Advanced button inside the Proxy Server section, use the servername and port on the first (http) row.

mygithubuser = the user I use to log in to github.com

mygithubpwd = the password for my github.com user

repoUser = the user owner of the repository

repoName = the name of the repository

Medford

Hooray, thanks! git config --global http.sslcainfo MY_NEW_CERTS_BUNDLE.crt plus certificates downloaded as described in simplicidade.org/notes/archives/2011/06/… (thanks to: https://mcmap.net/q/13487/-how-do-i-pull-from-a-git-repository-through-an-http-proxy) did it for me! – Gallard

@Pablolic Doing the first two steps itself did the trick for me. Thank you so much. +1 – Creaky

Seems to work for me, but git still doesn't work when I ask it to clone a repository using the git:// protocol. – Dinadinah

A couple of clarifications to pablolic's information, based on what worked for me: 1) If proxyuser is a Windows login, leave out the AD domain, just include the user name without the domain; 2) Spaces in the proxypwd should be encoded as "+". eg "My Password" should be entered as "My+Password". – Natural

@SimonTewsi any idea what to do if your password contains @ – Scallion

@Ajedi32: Firewalls are often specific about which ports allow traffic. Git protocol uses port 9418 which may not be allowed. Try https or http if available from the remote Git repo allows. – Lobito

@EdmundYeung99: I'd suggest replacing the @ symbol with %40. Haven't tried it but I believe that is standard URL encoding. – Natural

@SimonTewsi What about dollar signs in the password? My http.proxy does not seem to save right because of this character – Conglomerate

@demongolem: I suspect you may need to URL encode your password (haven't tried it, this is just an educated guess). See UrlEncoded column in the table in the following answer: https://mcmap.net/q/13942/-url-encoding-using-c In your case that would mean replacing the $ with %24. – Natural

What if then I want to disable the proxy in config? Can't set it to empty – Scalise

Found a way, not too sure if it is the best, git config --global http.proxy "" – Scalise

You have posted this exact answer numerous times. If it truly applies to all the other posts, you should have flagged them as duplicates. Your recent unnecessary, minor edits brought these to light. I am leaving this one as it is the highest-voted of them. – Sophiesophism

so what if i want to use tor to work with git? how i should configure git proxy to tor??? – Fao

Answer 3

Set a system variable named http_proxy with the value of ProxyServer:Port. That is the simplest solution. Respectively, use https_proxy as daefu pointed out in the comments.

Setting gitproxy (as sleske mentions) is another option, but that requires a "command", which is not as straightforward as the above solution.

References: Use Git behind a proxy

Comprehensible

Or use 'https_proxy' if you're connecting to a https-repository. – Mercola

@daefu: Not sure if you need to set https_proxy. I'm connected to an https repository and followed the first step of pablolic's instructions (ie adding http.proxy to the git config file). That was all it took for me. – Natural

https_proxy was required for me. Setting only http_proxy did not allow it to clone an HTTPS repo – Pernickety

@Mercola +1 this also works with widows github - related question : stackoverflow.com/questions/16216176/… – Unsupportable

@SimonTewsi @explunit While setting environment variables http_proxy is required for HTTP URLs and https_proxy is required for HTTPS URLs. Alternatively, one could just set all_proxy for all URLs. See ENVIRONMENT section in curl(1). However, while setting git-config options, http.proxy is used for both HTTP and HTTPS URLs. See http.proxy in git-config(1). – Captivity

This gave me The requested URL returned error: 501. – Dwelt

Answer 4

As an alternative to using git config --global http.proxy address:port, you can set the proxy on the command line:

git -c "http.proxy=address:port" clone https://...

The advantage is the proxy is not persistently set. Under Bash you might set an alias:

alias git-proxy='git -c "http.proxy=address:port"'

Monahon

For me this only worked if I included the scheme (="http://") in the variable value, so git -c "http.proxy=http://address:port" – Yong

Answer 5

If the command line way of configuring your proxy server doesn't work, you can probably just edit .gitconfig (in the root of your profile, which may hide both in C:\Documents and Settings and on some network drive) and add this:

[http]
    proxy = http://username:[email protected]:8080

Your mileage may vary though. This only covers the first step of the command line configuration. You may have to edit the system Git configuration too and I don’t have any idea where they hid that.

Zareba

"You may have to edit the system git configuration too". No, usually not. The system and user config are combined; setting the proxy in one of the two should be enough. – Kop

In my case it's located on my Windows machine in [git home]\etc\gitconfig - after editing it works like a charm! – Mucoid

This is especially useful if the command line doesn't like your password due to special characters. – Tarsia

Answer 6

If you are using Ubuntu, then do the following...

Step 1: Install Corkscrew

sudo apt-get install corkscrew

Step 2: Write a script named git-proxy.sh and add the following

#!/bin/sh

exec corkscrew <name of proxy server> <port> $*

# <name_of_proxy_server> and <port> are the ip address and port of the server
# e.g. exec corkscrew 192.168.0.1 808 $*

Step 3: Make the script executable

chmod +x git-proxy.sh

Step 4: Set up the proxy command for Git by setting the environment variable

export GIT_PROXY_COMMAND="/<path>/git-proxy.sh"

Now use the Git commands, such as

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Numerate

You should probably use "$@" instead of $*. See your shell manual for more details. – Chicken

Identical answer at How to configure Git to clone a repository from GitHub behind a proxy server – Queri

Answer 7

Faced same issue because of multiple .gitconfig files in Windows, followed below steps to fix the same:

Step 1: Open Git Bash

Step 2: Look for .gitconfig, executing following command:

git config --list --global --show-origin

Step 3: Copy the below content in .gitconfig:

[http]
    proxy = http://YOUR_PROXY_USERNAME:[email protected]:YOUR.PROXY.SERVER.PORT
    sslverify = false
[https]
    proxy = http://YOUR_PROXY_USERNAME:[email protected]:YOUR.PROXY.SERVER.PORT
    sslverify = false
[url "http://github.com/"]
    insteadOf = git://github.com/

[user]
    name = Arpit Aggarwal
    email = [email protected]

Essence

Answer 8

There's something I noticed and want to share here:

git config --global http.proxy http://<proxy address>:<port number>

The method above will not work for SSH URLs (i.e., [email protected]:<user name>/<project name>.git):

git clone [email protected]:<user name>/<project name>.git // will not use the http proxy

And things will not change if we set SSH over the HTTPS port (https://help.github.com/en/articles/using-ssh-over-the-https-port) because it only changes the port (22 by default) the SSH connection connects to.

Enrage

Answer 9

Try to put the following in the ~/.gitconfig file:

[http]
    proxy = http://proxy:8080
[https]
    proxy = http://proxy:8080
[url "https://"]
    insteadOf = git://

Vicariate

I tried all the stuff above. It wasn't until I added the https entry listed here that I was able to work. – Cleaner

What is it supposed to do? Why is this necessary? How does it work? An explanation would be in order. What is the idea/gist? From the Help Center: "...always explain why the solution you're presenting is appropriate and how it works". Please respond by editing (changing) your answer, not here in comments (but ****** ****** ****** without ****** ****** ****** "Edit:", "Update:", or similar - the answer should appear as if it was written today). – Queri

Answer 10

For the Git protocol (git://...), install socat and write a script such as:

#!/bin/sh

exec socat - socks4:your.company.com:$1:$2

Make it executable, put it in your path, and in your ~/.gitconfig set core.gitproxy to the name of that script.

Edeline

Works for windows with cygwin's SOCAT too. using socat STDIO PROXY:%proxy%:%1:%2,proxyport=%PROXYPORT% – Doorbell

Can use set GIT_PROXY_COMMAND=path\to\script to make GIT use the proxy without messing with git config. – Doorbell

Yes! Finally the right hint! I also needed authentication: exec socat STDIO PROXY:<proxy>:$1:$2,proxyport=<port>,proxyauth=<user>:<passwd> Found here: gist.github.com/sit/49288 – Pfeifer

Answer 11

I work on Windows XP at work (state/government), so I did my research and found this here and it worked for me.

The http_proxy Environment Variable

If you use a proxy server or firewall, you may need to set the http_proxy environment variable in order to access some URL from the commandline.

Example: Installing PPM for Perl or applying an RPM file in Linux, updating Ubuntu

Set the http_proxy variable with the hostname or IP address of the proxy server:

http_proxy=http:// [proxy.example.org]

If the proxy server requires a user name and password, include them in the following form:

http_proxy=http:// [username:[email protected]]

If the proxy server uses a port other than 80, include the port number:

http_proxy=http:// [username:[email protected]:8080]

Windows XP

1. Open the Control Panel and click the System icon.
2. On the Advanced tab, click on Environment Variables.
3. Click New in the System variables panel.
4. Add http_proxy with the appropriate proxy information (see examples above).

Linux, Solaris or HP-UX

Set the http_proxy environment variable using the command specific to your shell (e.g., SET or export). To make this change persistent, add the command to the appropriate profile file for the shell. For example, in Bash, add a line like the following to your .bash_profile or .bashrc file:

1. http_proxy=http:// [username:password@hostname:port];
2. export $http_proxy

Cuthbertson

tanx--> :) C:\Users\AT>echo %https_proxy% 172.20.4.55:808 – Reitareiter

Answer 12

In addition of these answers, I found helpful to consider these two points:

One may need to enforce an authentication scheme:

[http]
    # https://github.com/git/git/blob/master/Documentation/config.txt
    proxyAuthMethod = anyauth|basic|digest|negotiate|ntlm

Also, typically with an NTLM authentication schema, one may need to provide the AD domain explicitly.

In Git Bash:

echo %userdomain%

And update the http.proxy accordingly:

git config --global http.proxy http://DOMAIN\\proxyuser:[email protected]:8080

Anyway, investigation may be helped by adding CURL logs:

export GIT_CURL_VERBOSE=1

Mihrab

I needed to add proxyAuthMethod using git config --global http.proxyAuthMethod basic. Git gersion 2.8.3 didn't send in any authentication until I set this config parameter. – Miramontes

Answer 13

If you have tsocks or proxychains installed and configured, you can do

tsocks git clone <your_repository>

or

proxychains git clone <your_repository>

To make it shorter, I created a symbolic link, /usr/bin/p, for proxychains, so I can use it like this

p git clone <your_repository>

And I can use it to proxy any command,

p <cmd-need-be-proxied>

By the way, proxychains has not been updated for a long time, and you may want to try proxychians-ng instead.

Medley

Answer 14

Setting the Git proxy in the terminal

If

• you do not want set a proxy for each of your Git projects manually, one by one, and
• always want to use same proxy for all your projects

Set it globally once:

git config --global http.proxy username:password@proxy_url:proxy_port
git config --global https.proxy username:password@proxy_url:proxy_port

If you want to set a proxy for only one Git project (there may be some situations where you may not want to use same proxy or any proxy at all for some Git connections):

// Go to the project root
cd /bla_bla/project_root
// Set proxy for both HTTP and HTTPS
git config http.proxy username:password@proxy_url:proxy_port
git config https.proxy username:password@proxy_url:proxy_port

If you want to display the current proxy settings:

git config --list

If you want to remove the proxy globally:

git config --global --unset http.proxy
git config --global --unset https.proxy

If you want to remove the proxy for only one Git root:

// Go to the project root
cd /bla-bla/project_root
git config --unset http.proxy
git config --unset https.proxy

Antlion

https.proxy is invalid config 🙃. Only the configuration item named http.proxy exists. see: git-scm.com/docs/git-config/2.9.5#Documentation/… – Juristic

Answer 15

Here is the proxy setting:

git config --global http.proxy http://<username>:<pass>@<ip>:<port>
git config --global https.proxy http://<username>:<pass>@<ip>:<port>

Seeress

How is that different from previous answers? – Queri

Answer 16

I followed the most of the answers which was recommended here. First I got the following error:

fatal: unable to access 'https://github.com/folder/sample.git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.

Then I have tried the following command by @Salim Hamidi

git config --global http.proxy http://proxyuser:[email protected]:8080

But I got the following error:

fatal: unable to access 'https://github.com/folder/sample.git/': Received HTTP code 407 from proxy after CONNECT

This could happen if the proxy server can't verify the SSL certificate. So we want to make sure that the ssl verification is off (not recommended for non trusted sites), so I have done the following steps which was recommended by @Arpit but with slight changes:

1.First make sure to remove any previous proxy settings:

git config --global --unset http.proxy

2.Then list and get the gitconfig content

git config --list --show-origin

3.Last update the content of the gitconfig file as below:

[http]
sslCAInfo = C:/yourfolder/AppData/Local/Programs/Git/mingw64/ssl/certs/ca-bundle.crt
sslBackend = schannel
proxy = http://proxyuser:[email protected]:8080
sslverify = false
[https]
proxy = http://proxyuser:[email protected]:8080
sslverify = false

Pinnate

Answer 17

I have tried all the previous answers and nothing worked for me, as there was a proxy password encoding issues.

This command worked:

git config --global http.proxy http://[email protected]:PortNumber

Do not enter the password in your command. It will dynamically ask for when you try to connect to any Git repository.

Burton

Thanks, this worked for me. Although the git config setting should be http.proxy – Selfexplanatory

username is not enough.Password also required. – Esemplastic

use this code {git config --global http.proxy proxyuser:[email protected]:8080} – Esemplastic

Answer 18

For Windows users: if git config or set http_proxy= doesn't work, this answer may help:

Replace the git:// protocol of the Git repository with http://. Note, you'll have to set the http_proxy first, anyway.

Zarathustra

Answer 19

After tirelessly trying every solution on this page, my workaround was to use an SSH key instead!

1. Open Git Bash
2. ssh-keygen.exe -t rsa -C <Your username>
3. Open your Git provider (GitHub, Bitbucket, etc.)
4. Add copy the id_rsa.pub file contents into Git provider's input page (check your profile)

Justiciable

Answer 20

To change https.proxy config for a single repository (not global git config) before a new clone (you can not change repo git config before repository exists)

cd /path/to/new/clone/
git init .
git config http.proxy http://...myProxy.com:myPort
git config https.proxy https://...myProxy.com:myPort
git remote add origin https://github.com/opencv/opencv.git
git fetch origin
git checkout -b master --track origin/master

Note: I needed https.proxy (not http.proxy) to have it working.

Note: you can find your proxy settings on Windows 10 at Settings -> Network&Internet -> Proxy -> Address + Port

Gregor

Answer 21

An alternative to using a proxy is to use SSH

In the Git configurations, configure the origin remote on the SSH address. Then use the ssh-keygen command, which gives you a public key that you can set in your GitLab or Gitab account settings and login accordingly done...

1. Verify which remotes are using by running git remote -v in your Git client.

2. If this is http(s) URL, changed it to ssh address , run: git remote set-url <remote name, e.g. origin> <new SSH URL>. For example,

    git remote set-url [email protected]:example/myproject.git
   

3. To generate SSH key for login, run: ssh-keygen -o. This command generate public (id_rsa.pub file) and private keys.

4. Copy public key contents. (from id_rsa.pub file)

5. Go to GitLab, GitHub, etc. profile section → setting/ssh-key. Create a new SSH key and paste the public key contents

Lesh

What is this "Gitab" you speak of? Do you have a reference? – Queri

@PeterMortensen There is ssh doc for GitLab docs.gitlab.com/ee/user/ssh.html – Lesh

Answer 22

Since no one mentioned this way, I`ll share what worked for me:

git config --global http.proxy 'socks5://127.0.0.1:1080' 
git config --global https.proxy 'socks5://127.0.0.1:1080'

Changing 127.0.0.1 to the IP/URL for the proxy and the port.

Irick