Change language
English Русский Deutsch Español Français Italiano Українська Tiếng Việt Türkçe Bahasa Indonesia हिन्दी 日本語 Português 中文
Menu
Pricing
Proxies
Solutions
Resources

ERR_TUNNEL_CONNECTION_FAILED: causes and fixes

Topic: Errors and fixes All answers

In short: ERR_TUNNEL_CONNECTION_FAILED means the browser reached the proxy but the proxy would not open the tunnel for an HTTPS page. The common reasons are rejected credentials, an allowlist that does not list your current address, or a proxy that has expired. Test with a plain HTTP page first, to see whether the tunnel or the sign-in is at fault.

For an HTTPS page, the browser first asks the proxy to open a tunnel to the site. This error means the proxy answered that request with a refusal, or the answer was not usable. So the proxy is reachable; the request to open the tunnel is the part that failed, and that points at the proxy’s answer, since the site you wanted was never contacted.

Find your cause

What you seeLikely causeWhat to do
Fails on every HTTPS siteThe proxy refused the CONNECT request, often with a 407 or another refusalCopy the login and password again from your dashboard
Worked yesterday, fails todayIn allowlist mode your public address changedLook up your address and update the list
Fails only on one networkThat network filters the proxy port or tunnelsTest on another network
Fails after a protocol changeClient and proxy protocols differCopy the port again from the row
Fails after a dateThe proxy expiredExtend the order; the address stays

Separate the tunnel from the sign-in

Open a page that uses plain HTTP through the proxy, or run one request from curl with the same details. If it returns 407, the credentials or the allowlist are at fault, and the page on error 407 lists what to check. When the plain request works and only HTTPS fails, look for another proxy, a VPN or a security program that inspects HTTPS traffic, and turn it off for the test.

Check the order itself

In My Proxies in your dashboard, confirm the row is not in Provisioning, and that the Expires time has not passed. Setting an allowlist switches the password off for the whole order, so a client still sending a password gets refused. The post on authentication methods explains how the two modes differ and which one suits a changing home address.

When to write to us

If credentials, expiry and network all check out, write to support@proxyjam.com with the order number and a screenshot, and we will troubleshoot the order. To report a defect, write to billing@proxyjam.com within 24 hours of payment, as section 4 of the Refund Policy asks. A proxy that does not accept a connection with the credentials we issued is a defect once we confirm it (section 1). The proxies themselves, and what a static ISP address is, are described on the ISP proxies page.

Quick answers about this error

How is this different from ERR_PROXY_CONNECTION_FAILED?

There the browser cannot reach the proxy at all. Here it reached the proxy, and the proxy refused to open the tunnel to the site. ERR_PROXY_CONNECTION_FAILED: what it means and how to fix it

Why do only HTTPS sites fail?

An HTTP proxy carries an HTTPS page through a tunnel it opens on request. When the proxy refuses that request, the page fails while the proxy itself is up. Using your static IP

Could the site be blocking me?

A tunnel that will not open is the proxy's refusal. A site that blocks an address answers only after the tunnel is up.

Related pages