JIYIK CN >

This article discusses configuring Git to work with different proxies. It is often difficult to access Git when working behind a corporate firewall.

We'll cover some of the proxies that Git supports, how to configure them, and how to provide the proxy to our command line for a one-time use. Let's jump right in.

Proxy protocols supported in Git

Git supports the following proxies:

1. HTTP
2. HTTPS
3. SOCKS4
4. SOCKS5

Using HTTP Proxy with Git Commands

We usually edit the Git configuration file to use a proxy. However, Git allows us to provide the proxy to the terminal for quick use.

This is an example of an HTTP proxy on the command line.

$ git config --global http.proxy http://username:password@proxy_server.com:port

In a scenario with a specific domain, we will run the command as shown below.

$ git config --global http.http://specific_domain.com.proxy http://username:password@proxy_server.com:port

Notice that we http.proxyadded our domain between and that we provided the full proxy URL. The full URL enables Git to automatically recognize and run the protocol.

Using HTTPS proxy with Git commands

In the scenario where we are working behind a firewall, following is how we will run the commands for the HTTPS proxy protocol.

$ git config --global http.https://specific_domain.com.proxy http://username:password@proxy_server.com:port

The URL is between http.proxy, but note the change from http://specific_domain.comto https://specific_domain.com.

You can disable SSL verification to avoid problems as shown below.

$ git config --global http.https://specific_domain.com.sslVerify false

Permanently configure the proxy in the Git configuration file

We can store the above settings permanently in the Git configuration file. We use --globalthe switch to set the configuration for all users and connections.

Use --Globalthe switch to set the global proxy

If we need all Git operations to go through the proxy, we run:

$ git config --global http.proxy http://username:password@proxy_server.com:port

Setting up a proxy for a specific domain

If we want a specific domain to connect through our proxy, we would run the following command.

$ git config --global http.https://domain.com.proxy http://username:password@proxy_server.com:port

Disable HTTPS Authentication

If you receive this error message 无法访问 'https://...': Unknown SSL protocol error in connection to ...:443, you can turn off SSL verification as shown below.

$ git -c http.sslVerify=false clone https://domain.com/example.git

Alternatively, you can disable it all together as shown below.

$ git config http.sslVerify false

Remove proxy settings for Git repository

We use the command below to list all the proxies connected to our repository.

$ git config --get-regexp http.*

We can use any of the following syntaxes to remove our proxy.

$ git config --unset http.proxy
$ git config --unset http.https://domain.com.proxy

or

$ git config --unset http.sslVerify
$ git config --unset http.https://domain.com.sslVerify

As shown below, we can add globalthe switch to remove the proxy settings from all of our repositories.

$ git config --global --unset http.proxy
$ git config --global --unset http.https://domain.com.proxy

SOCKSConfiguring a proxy in Git

As mentioned earlier, Git supports the socks5://and socks4://protocols.

Run the following command to configure SOCKSthe protocol.

$ git config --global http.proxy socks5://proxy_server.com:port

For a specific domain, run:

$ git config --global http.https://domain.com.proxy socks5://proxy_server.com:port