ERR_TUNNEL_CONNECTION_FAILED
Chrome asked a proxy server to connect it to the site, and the proxy said no or failed. Without that tunnel, HTTPS sites can't load.
Quick checks
- Do you need a proxy (work network, school)? If not, turn proxies off.
- Did a VPN or debugging tool recently quit? It may have left a proxy configured.
Fixes on Mac
Turn off unwanted proxies
- System Settings › Network › Wi-Fi (or Ethernet) › Details › Proxies.
- Turn off Web proxy, Secure web proxy, SOCKS and Automatic proxy configuration unless you need them; click OK.
Check for apps that set proxies
- Charles, Proxyman, VPN apps and some security tools set system proxies while running. Quit them cleanly or reset their proxy setting.
- Run
scutil --proxyin Terminal to see the active proxy configuration.
Fixes on Windows
Remove the proxy
- Settings › Network & internet › Proxy: turn off Use a proxy server and automatic setup scripts you don't use.
Other devices
Phones
- Wi-Fi network settings › HTTP Proxy: set to Off.
Still not working?
ERR_PROXY_CONNECTION_FAILED is the related error when the proxy itself can't be reached. On a managed (work) Mac, proxy settings come from your organisation; contact IT rather than changing them.
See what’s happening
LightAtom's connections view shows all of Chrome's traffic going to a single proxy address when a proxy is in use.
Frequently asked questions
What does ERR_TUNNEL_CONNECTION_FAILED mean?
Chrome uses a proxy, and the proxy couldn't create the CONNECT tunnel needed for HTTPS to the site, because the proxy failed, blocked the site or isn't configured correctly.
How do I check proxy settings on a Mac?
System Settings › Network › your connection › Details › Proxies, or run scutil --proxy in Terminal to see what's active.
What is the difference from ERR_PROXY_CONNECTION_FAILED?
PROXY_CONNECTION_FAILED: Chrome can't reach the proxy at all. TUNNEL_CONNECTION_FAILED: it reached the proxy, but the proxy couldn't connect onward.