• March 3, 2024

Received 503 From Proxy After Connect

Received HTTP code 503 from proxy after CONNECT – Stack …

I am trying to clone from a corporate git repo, but always receive this error message after a while:
fatal: unable to access URL: Received HTTP code 503 from proxy after CONNECT
I have the following. gitconfig file:
sslVerify = false
proxy = []
proxy =
asked Jan 29 ’17 at 16:39
If it is a corporate repo, you might want to ignore proxy settings. One possible solution to your problem is here:
Ignore proxy: export no_proxy=YOUR_CORP_DOMAIN_ON_GITHUB, where the domain name might be in the form of
Ignore SSL verification: git config –global lVerify “false”
You could then clone the repo w/ git clone YOUR_HTTPS_CLONE_URL
answered Mar 10 ’17 at 2:31
srctahasrctaha1, 3061 gold badge14 silver badges15 bronze badges
In my case I needed to disable both the proxy and authenticating SSL certificates, I don’t really like this solution as it doesn’t sit well with me – turning off verifying SSL certificates doesn’t sound wise!
But here’s the command I ran to get it to work:
git clone –config –config lVerify=false
answered Apr 23 ’18 at 13:02
EM-CreationsEM-Creations3, 8803 gold badges38 silver badges55 bronze badges
If you want to ignore proxy for a single git command you can use -c option, for example:
git clone –config
answered Sep 10 ’17 at 10:34
you can add in your. gitconfig file for ignore your corporate proxy:
[ “]
answered Dec 5 ’18 at 9:01
Even I had the similar problem while pushing my code changes into corporate gitlab after I set “HTTP_PROXY” and “HTTPS_PROXY” into my environment variable to use the proxy for accessing other sites that are blocked by the company. I ran the following command in Git Bash console to ignore the proxy before pushing the code and it worked for me.
where the domain name might be in the form of (I didn’t put any or)
answered Aug 18 ’20 at 23:54
I faced the same issue and don’t want to bypass SSL verification.
I make it work thanks to these steps (Windows):
1. Launch in a console:
Réponse ne faisant pas autorité:
2. In order to clone:
Replace by the original instead of alias:
git clone
answered Feb 25 ’19 at 9:50
DelphineDelphine8377 silver badges19 bronze badges
use git ssh command
git clone “ssh:/
answered Mar 9 at 5:00
Not the answer you’re looking for? Browse other questions tagged git github proxy git-config corporate or ask your own question.
curl: (56) Received HTTP code 503 from proxy after CONNECT

curl: (56) Received HTTP code 503 from proxy after CONNECT

In my case the problem was in env and
< HTTP/1. 1 503 Service Unavailable < Mime-Version: 1. 0 < Date: Wed, 06 Feb 2019 13:44:00 GMT < Content-Type: text/html;charset=utf-8 < Content-Length: 3564 < X-Squid-Error: ERR_CONNECT_FAIL 111 < Vary: Accept-Language < Content-Language: en < * Received HTTP code 503 from proxy after CONNECT * Closing connection 0 curl: (56) Received HTTP code 503 from proxy after CONNECT After adding url to the env of the no_proxy, port 443 failed We verified that '' was not configured on the destination server, after adding the certificate tag and adjusting the vhost the connection could be made. 503 Service Unavailable - What really it means? - Super User

503 Service Unavailable – What really it means? – Super User

I developed a website and it loads in every other system but certainly not in mine… WHen i used firebug my request show 503 Service Unavailable
My response was,
Server squid/ABLE21
Date Sat, 27 Mar 2010 12:25:18 GMT
Content-Type text/html
Content-Length 1163
Expires Sat, 27 Mar 2010 12:25:18 GMT
X-Squid-Error ERR_DNS_FAIL 0
X-Cache MISS from xavy
X-Cache-Lookup MISS from xavy:3128
Via 1. 0 xavy:3128 (squid/ABLE21)
Proxy-Connection close
quack quixote40. 2k13 gold badges101 silver badges127 bronze badges
asked Mar 27 ’10 at 12:28
Perhaps you have weird proxy settings. 503 usually signifies a temporary outage and has more possible causes than you can poke a stick at.
If it’s just your machine that’s failing, then maybe something is misconfigured in your browser, or your browser is the only one pointing to a misconfigured proxy. The squid warnings are a tell-tale. Are you running the browser on the same box as the proxy? That often causes problems due to squid’s default ACLs.
answered Mar 27 ’10 at 12:30
Marcelo CantosMarcelo Cantos1, 3812 gold badges11 silver badges16 bronze badges
It’s hard to tell from the message what the reason is. It could be that you are behind a proxy that is unable to connect to your web site (in that case, you may see the name of a proxy application somewhere on the page); or it could be that your web site somehow can’t be served to you, for whatever reason.
If it really is a server error and not a Proxy error, you would have to consult your server’s error log files to find out the reason for the problem. You will usually find a detailed explanation of the problem there.
If you’re on shared hosting, and the problem is definitely with the site, this is a case for your provider’s technical support staff.
PekkaPekka2, 3596 gold badges34 silver badges56 bronze badges
If this is a site hosted in IIS, you should check the Windows Application event log. You’ll find details why your web app is crashing.
Are the other machines on the same LAN or are they coming in from the internet
That implies that there is a DNS faliure on the part of squid. what address are you using?
Reading this im a little confused as to your setup, is the squid server yours? is it running as a forward or reverse server? Is the squid box on the same LAN as your Computer?
answered Apr 20 ’10 at 14:18
ArcathArcath4897 silver badges17 bronze badges
I had the same (in tortoisesvn), and it was definitely after I setup the proxy to access a repos. on the web, and forgot to add exceptions for internal websites:
Add exceptions for in House servers!
answered Mar 8 ’13 at 9:48
Not the answer you’re looking for? Browse other questions tagged proxy web-development squid or ask your own question.

Frequently Asked Questions about received 503 from proxy after connect

Leave a Reply

Your email address will not be published. Required fields are marked *