Troubleshooting · Chrome, Edge

Fix ERR_TUNNEL_CONNECTION_FAILED Error

When you open an HTTPS site through a proxy, your browser sends a CONNECT command asking the proxy to open a "tunnel" to the destination site. ERR_TUNNEL_CONNECTION_FAILED means the browser successfully contacted the proxy, but the proxy refused or failed to open the tunnel. Chrome hides the real error code; uncovering that code is the fastest way to fix the issue properly.

Author: Bùi Toàn · Updated: 19/11/2026

How do you find the real error code behind ERR_TUNNEL_CONNECTION_FAILED?

Run: curl -v -x http://IP:PORT -U user:pass https://trang-bi-loi.com. Look for the line starting with "< HTTP/1.1" immediately after the CONNECT line. The code there reveals what the proxy returned.

Code after CONNECTMeaningSolution
200 Connection establishedTunnel opened successfullyThe issue is in the browser: extensions, configuration, antivirus software
407Incorrect or missing username, passwordSee the 407 error guide
403Proxy refused this destinationPort or service is blocked under the usage policy
502, 503Proxy failed to connect to the siteCheck the destination site, try another site

Why does the ERR_TUNNEL_CONNECTION_FAILED error occur?

This error occurs when the proxy fails to establish a tunnel to the target site, typically due to incorrect credentials, selecting the wrong proxy type, or the target site being unreachable.

  • Incorrect credentials, but the browser does not display the login prompt and throws a tunnel error instead. Commonly happens when the proxy is configured via command-line arguments or in automation software.
  • Selecting a proxy protocol that does not match the active proxy mode, such as SOCKS5 while the proxy is running HTTP, or HTTPS (TLS to proxy) instead of HTTP.
  • The destination site does not exist, the domain is mistyped, or the site is down, so the proxy cannot resolve or connect to it.
  • Connecting to a port that is blocked by policy, such as SMTP email ports which are typically blocked to prevent spam.
  • Antivirus HTTPS inspection interfering between the browser and the proxy.

How to fix

  1. Run the curl command above to identify the real error code.
  2. Code 407: re-enter your username and password exactly as shown in the management portal, with no extra spaces.
  3. Test a major site like https://www.google.com through the proxy. If the major site loads but the target does not, the issue lies with the destination site.
  4. Verify that the proxy protocol in your software matches the active proxy mode under Orders (HTTP, SOCKS5, or HTTP + SOCKS5).
  5. Temporarily disable the HTTPS scanning feature (Web Shield, SSL scanning) in your antivirus software to test.
  6. Completely close the browser and reopen it; flush stale sockets at chrome://net-internals/#sockets.

Don't have a proxy? Buy dedicated proxies with automatic activation

Dedicated IPv4 proxies in 9 countries from 20.000₫/IP/month when buying from 2.000 IPs (39.000₫ for 1 IP) and static ISP proxies in Vietnam, US. HTTP(S) and SOCKS5 with username and password, unlimited bandwidth, automatic activation after payment. Note that Vietnam proxies currently use HTTP(S) protocol, with no SOCKS5 yet.

Buy proxies now

Frequently Asked Questions

Why does ERR_TUNNEL_CONNECTION_FAILED only occur on certain sites?+

The proxy is running but cannot establish a connection to those specific sites: the site is down, the domain is incorrect, or the port is blocked. Use curl -v to see the code returned by the proxy.

Does ONET proxy block any websites?+

Proxies are intended for legitimate use; certain easily abused ports such as outbound SMTP are blocked. Standard websites are fully accessible.