Git clone error "HTTP code 504 from proxy after CONNECT"

manuelbcd picture manuelbcd · Jan 12, 2016 · Viewed 39.5k times · Source

I'm working in a office behind a corporate firewall. My System is windows7, using componentes consola. Usually I need to set up proxy connections to get GIT working with github.

But when I try to clone a repository sored in a private Stash (Atlassian) I get this error:

Cloning into 'apptest'...
fatal: unable to access 'https://[email protected]:xxxx/apptest/apptest.git
/': Received HTTP code 504 from proxy after CONNECT

I have unsetted git proxy but I'm still facing same problem. Please note that I'm using GITshell over Windows 7

Any help would be appreciated.

Regards

Answer

manuelbcd picture manuelbcd · Jan 12, 2016

Problem solved.

Windows: Before connecting Bitbucket (AKA stash) you need to clean all proxies from both Git and console environment:

SET HTTP_PROXY=
SET HTTPS_PROXY=
git config --global --unset http.proxy
git config --global --unset https.proxy
git clone http://yourUser@stashAddress:stashPort/apptest.git

But if you need to connect to public repositories like github, then it's necessary to define proxies again:

SET HTTP_PROXY=proxyaddress:port
SET HTTPS_PROXY=proxyaddress:port
git config --global http.proxy http://proxyaddress:port
git config --global https.proxy http://proxyaddress:port

I think it may be useful for other developers working behind corporate firewalls.

Linux

unset HTTP_PROXY
unset HTTPS_PROXY
git config --global --unset http.proxy
git config --global --unset https.proxy
git clone http://yourUser@stashAddress:stashPort/apptest.git

To define proxies again:

export HTTP_PROXY=proxyaddress:port
export HTTPS_PROXY=proxyaddress:port
git config --global http.proxy http://proxyaddress:port
git config --global https.proxy http://proxyaddress:port

Take care with uppercase of environment variables. Some OS versions may need lowercase or may have defined lowercase variables by default.