You open a site through your proxy and Chrome shows ERR_TUNNEL_CONNECTION_FAILED instead of the page. It means Chrome could not set up a tunnel through the proxy to that website.
The usual cause is on the proxy side, such as the wrong host, port or protocol, a missing login or a used-up traffic allowance. Check those before you change anything in Windows. If you see ERR_PROXY_CONNECTION_FAILED instead, start with whether the browser can reach the proxy at all, then check browser and system settings.
What ERR_TUNNEL_CONNECTION_FAILED and ERR_PROXY_CONNECTION_FAILED mean
Chromium's network error definitions separate the two:
- ERR_TUNNEL_CONNECTION_FAILED means a tunnel through the proxy could not be established.
- ERR_PROXY_CONNECTION_FAILED means resolving the proxy hostname or connecting to its socket failed. Failures during HTTP CONNECT are excluded from it.
For an HTTPS website through an HTTP proxy, the browser first asks the proxy for a tunnel with CONNECT, then sends the website's encrypted connection through it. Chromium's proxy documentation explains this flow. Neither error points to one unique cause, so work through the checks in order.
How to fix ERR_TUNNEL_CONNECTION_FAILED in Chrome
Step 1
Check the host, port and proxy string
Copy the current endpoint from your provider's configuration page. Put the hostname, port, username and password in their matching fields, remove accidental spaces and use the documented port. If an app has separate fields, pasting the whole connection string into its host field won't fill them. See proxy formats explained. A CDK activates the service. It is not a proxy password.
Step 2
Match HTTP, HTTPS or SOCKS5 to the endpoint
Pick the protocol the provider documents for that host and port. The website's address doesn't decide it, and an HTTPS website can work through an HTTP proxy. Choosing HTTPS for the proxy adds TLS to the browser-to-proxy connection, so it needs an endpoint built for that.
SOCKS5 uses a different handshake, and entering a SOCKS5-only endpoint as HTTP won't make it accept HTTP requests. Chromium also states that Chrome's native SOCKS5 implementation has no authentication support. If your plan is SOCKS5 with a login, Chrome can't use it directly. Use a client that handles SOCKS5 authentication, or the provider's compatible HTTP endpoint.
Step 3
Verify authentication and provider allowance
Check the generated proxy credentials, including any location or session parameters in the username. Chrome ignores credentials embedded in manual proxy settings and uses its separate authentication flow for HTTP proxies. If your plan uses IP allowlisting, check that the provider authorizes the public address of the network sending the requests.
An HTTP 407 response means the proxy needs valid authentication, and the 407 troubleshooting guide covers that case.
Then check the remaining traffic and, if the plan uses sub-accounts, the allowance assigned to yours. An exhausted allowance can stop service even when every setting is right, but more traffic won't correct a wrong endpoint. NovProxy Residential Traffic, for example, is a GB-based product, and NovProxy states that its traffic plan is billed by volume. Its setup guide explains configuration.
Step 4
Compare the connection with curl
Run a request outside the browser to separate endpoint access from browser configuration. It takes a short text file and one command. On Windows PowerShell, use curl.exe. First create a private local file named proxy-check.conf containing this line:
noproxy = ""
That line clears curl's proxy exclusions, including no_proxy or NO_PROXY. Then run this HTTP-proxy command with the provider's host and port:
curl.exe -q --config "proxy-check.conf" --proxy "http://PROXY_HOST:PROXY_PORT" --connect-timeout 10 --max-time 30 https://example.com/
Keep -q first so curl skips its default configuration file. The 10-second connection and 30-second transfer limits are troubleshooting values picked for this check. Connection setup includes DNS resolution and the requested TCP and TLS handshakes. For SOCKS5, use socks5h://PROXY_HOST:PROXY_PORT, which lets the proxy resolve the destination hostname.
If the proxy needs a login, add proxy-user = "USERNAME:PASSWORD" as a separate line in that file and replace both placeholders locally. In quoted config values, escape a literal backslash as \\ and a double quote as \". Keep the file private and remove it afterward. The curl manual documents these options and advises against clear-text credentials on command lines.
A connection refusal points to the host and port you addressed. A timeout can come from connection setup or the transfer. A proxy authentication response points to access settings. If example.com works, repeat with the failing HTTPS URL. If curl gets the expected page while the browser fails on that URL, compare the browser's configuration and authentication support.
What each comparison tells you
Also try another public HTTPS page through the same proxy. Where direct access is permitted, load the same pages with your optional proxy switched off, then restore the intended proxy.
| What happens | What to check next |
|---|---|
| Direct access works, several sites fail through the proxy | Endpoint, protocol, authentication and allowance |
| curl works, the browser fails | Browser proxy selection, authentication support or extension settings |
| Browser and curl both fail through the proxy | Shared proxy configuration, provider access or network reachability |
| Several sites also fail directly | Local network connection before proxy settings |
| One destination fails, others work | Destination-specific restrictions or a proxy-to-site connection problem |
Browser extensions and Windows proxy settings
Step 5
Check which setting controls the browser
Look at your proxy extension and system settings. A local address such as 127.0.0.1 points to software on your own computer. If that forwarding app is stopped, restart it, or remove its stale configuration when you no longer need it. Then turn off a proxy-controlling extension for a moment and compare. Google's Chrome troubleshooting advice includes checking extensions. Note which route each comparison used, then restore your intended setup.
Step 6
Remove an obsolete Windows proxy
On your own unmanaged Windows 11 device, open Settings > Network & internet > Proxy. If the manual proxy is obsolete, edit Use a proxy server, switch it off and save. If an old script controls routing, review Use setup script too. Microsoft documents these settings, and our Windows 11 proxy settings guide covers turning a proxy off. On an organization-managed device, ask IT first.
Step 7
Reserve network reset for wider connection failures
If direct browsing also fails after basic network troubleshooting, Windows 11 has Network & internet > Advanced network settings > Network reset. Select Reset now only when you're ready to set networking up again. Microsoft describes reset as a last step. It removes network adapters and their settings, then reinstalls them with default settings after the PC restarts. VPN software may need reinstalling and setting up again.
Why has the proxy tunnel failed for one website?
If one site fails while several others work, look at that destination. Ask the provider whether it permits that destination and can reach it. An access-denied page the website sends over HTTPS is a different problem from a failed tunnel, because the connection got through and the site refused it.
If the website restricts proxies, follow its access rules. Use permitted direct access, its authorized API or the site's support channel.
Start with the proxy string and protocol, because you control those. If they match the provider's page and curl still fails, check the remaining traffic. If it has run out, more traffic codes are under residential GB plans.
FAQ
What is the difference between ERR_TUNNEL_CONNECTION_FAILED and ERR_PROXY_CONNECTION_FAILED?
They fail at different stages. The tunnel error is about establishing the tunnel, while the proxy-connection error is about reaching the proxy, and HTTP CONNECT failures are excluded from it.
Can a wrong port cause a proxy connection error?
Yes. A wrong port can reach no service or the wrong one. Compare it with the provider's endpoint configuration, not the browser code alone.
Should I choose HTTPS because the website uses HTTPS?
No. HTTP proxies can tunnel HTTPS websites through CONNECT. Choose HTTPS only for an endpoint that accepts TLS on the browser-to-proxy connection.
Can Chrome use a SOCKS5 proxy with a username and password?
Not natively. Chrome's built-in SOCKS5 support can't authenticate, so use a client with SOCKS5 authentication support or the provider's compatible HTTP endpoint.
Do these checks also apply to Microsoft Edge?
Yes. The reachability, protocol and authentication comparisons apply to Edge too. Use Edge's own extension and proxy controls, then compare the same destination inside and outside the browser.
Drafted with AI help from our notes, then checked and edited by Nazmul I.
