Git Behind A Proxy Server

Git Behind A Proxy Server
0

#1

Use-cases

You might need to modify git commands that access (to update and read from) remote repositories if your internet access is through a proxy server.

Proxy servers are common in college and business type environments.

You can locate your proxy settings from your browser’s settings panel.

Using Proxy with Git

Once you have obtained the proxy settings (server URL, port, username and password); you need to configure your git as follows:

$ git config --global http.proxy http://<username>:<password>@<proxy-server-url>:<port>

You would need to replace <username>, <password>, <proxy-server-url>, <port> with the values specific to your proxy server credentials. These fields are optional. For instance, your proxy server might not even require <username> and <password>, or that it might be running on port 80 (in which case <port> is not required).

Once you have set these, your git pull, git push or even git fetch would work properly.

When Not to Use

You should not have to use git commands with proxy settings, if either of the following happens

  • Your system administrator or corporate policy does not allow you to access remote git repositories from GitHub, BitBucket etc.
  • The remote repository in question is not in your machine, but it’s within the internal network. An instance of GitLab deployed internally at your company is a good example.

Unset Proxy Settings

Use this Stack Overflow discussion to unset your proxy settings.

Resources

You may use the following for further reading on this:


#2

Why don’t you use a proxy server like Hidester that do it all this configurations for you. It is completely free and it is very reliable. https://hidester.com/proxy/


#3