The short answer
To load an HTTPS site through an HTTP proxy, Chrome sends a CONNECT request asking the proxy to open a tunnel. This error means the proxy said no, or the tunnel broke while opening.
Usual causes
- Missing or wrong credentials (the proxy answered 407).
- The provider blocks that site or port, for example banking or government sites on some residential networks.
- The proxy only supports HTTP, not CONNECT.
- A local firewall or antivirus intercepting the connection.

Also known as
Tunnel connection failed, CONNECT failed, HTTPS proxy tunnel error.
Learn more
- What is HTTP CONNECT?
- What does 407 mean?
- Browser proxy settings
- Common proxy errors
- MDN on the CONNECT method
- RFC 9110, HTTP semantics
- The Chromium project
- RFC 8446, TLS 1.3
Affiliate disclosure: Team of Monkeys is an affiliate of Geonode, Webshare and Rayobyte. Links and banners marked as sponsored, and links to Geonode, Webshare and Rayobyte in the text, use our referral links, and we may earn a commission if you buy through them, at no extra cost to you. Our explanations and comparisons are written to be useful whichever provider you choose.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.
Editorial note: Proxy providers change their pools, features and prices often, so treat any figures here as typical ranges at the time of writing and confirm current terms with the provider before you buy.