---
title: "ERR_TUNNEL_CONNECTION_FAILED in Chrome on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/err-tunnel-connection-failed"
description: "Chrome on your Mac shows ERR_TUNNEL_CONNECTION_FAILED. The proxy did not open a tunnel to the site. Check the proxy reply and its rules."
---

# ERR_TUNNEL_CONNECTION_FAILED in Chrome on Mac

ERR_TUNNEL_CONNECTION_FAILED is a Chrome network error. The Chromium source describes it as: “A tunnel connection through the proxy could not be established.”

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

My Mac has this problem: ERR_TUNNEL_CONNECTION_FAILED in Chrome on Mac. Read https://kilobat.app/guides/err-tunnel-connection-failed.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Applies to: Google Chrome and other Chromium browsers (Edge, Brave, Arc) on all current macOS versions. · Checked: 29 October 2026

## Symptoms

- Chrome shows “Unable to connect to the proxy server”.
- The error is ERR_TUNNEL_CONNECTION_FAILED.
- HTTPS sites fail. HTTP sites may load.

## Likely causes

- **The proxy refuses the host.** The proxy can deny a CONNECT request to a host or port.
- **Proxy credentials are missing.** The proxy can require a sign-in that Chrome did not send.
- **A proxy rule or filter.** A company policy can block the site.
- **A wrong proxy type.** An HTTP proxy is set where the network needs another type.

## How to check

1. Show the proxy that macOS uses.

   ```
   scutil --proxy
   ```
2. Test the tunnel with curl through the proxy.

   ```
   curl -v -x http://proxy.example.com:8080 -I https://example.com
   ```
3. Read the proxy’s reply code in the curl output.
4. Try the same page without the proxy on another network.

## How to fix it

1. If the reply is 407, sign in or correct the credentials.
2. If the reply is 403, ask the administrator to allow the host.
3. Turn off a proxy that you do not need.
4. See [Proxy settings stop apps from connecting on a Mac](https://kilobat.app/guides/proxy-settings-breaking-apps).

## With Kilobat

1. Kilobat's connection doctor tests the address layer by layer: network, proxy, DNS, rules, IPv4, IPv6, TLS and the server. It names the layer that failed.

   ```
   kilobat why https://example.com
   ```
2. These Kilobat checks are free. AI agents run them through MCP with `diagnose_connection` and `diagnose_network`. See [Find why one site or API won't connect](https://kilobat.app/guides/recipes/why-cant-it-connect).

## Questions

**What does a 407 reply mean?**

The proxy requires credentials that the client did not send.

**Why do only HTTPS sites fail?**

HTTPS goes through a tunnel that the proxy must allow. Plain HTTP does not use one.

## Sources

- [Chromium source: net_error_list.h](https://chromium.googlesource.com/chromium/src/+/main/net/base/net_error_list.h)
- [Chrome Help: Fix connection errors](https://support.google.com/chrome/answer/95669)

Checked on 29 October 2026.

## Related guides

- [ERR_PROXY_CONNECTION_FAILED in Chrome on Mac](https://kilobat.app/guides/err-proxy-connection-failed): ERR_PROXY_CONNECTION_FAILED is a Chrome network error.
- [Proxy settings stop apps from connecting on a Mac](https://kilobat.app/guides/proxy-settings-breaking-apps): A proxy setting sends traffic through another server.
- [Corporate proxy certificates break Terminal tools on a Mac](https://kilobat.app/guides/corporate-proxy-certificates): Some company networks inspect HTTPS traffic.
- [“Safari can’t connect to the web proxy server” on Mac](https://kilobat.app/guides/safari-cant-connect-proxy-server): A web proxy is set in the network settings, and Safari cannot reach it.
