---
title: "ERR_PROXY_CONNECTION_FAILED in Chrome on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/err-proxy-connection-failed"
description: "Chrome on your Mac shows ERR_PROXY_CONNECTION_FAILED. Chrome cannot reach the proxy. Check the address, the port and old proxy settings."
---

# ERR_PROXY_CONNECTION_FAILED in Chrome on Mac

ERR_PROXY_CONNECTION_FAILED is a Chrome network error. The Chromium source describes it as: “Could not create a connection to the proxy server. An error occurred either in resolving its name, or in connecting a socket to it.”

**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_PROXY_CONNECTION_FAILED in Chrome on Mac. Read https://kilobat.app/guides/err-proxy-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 “There is something wrong with the proxy server”.
- The error is ERR_PROXY_CONNECTION_FAILED.
- Sites fail that load on another network.

## Likely causes

- **A wrong proxy address.** The name or port of the proxy in the Mac settings is wrong.
- **The proxy is down.** The proxy server is off or not reachable from this network.
- **An old setting.** A proxy from a past network or VPN is still set.
- **A proxy script that fails.** A proxy auto-config (PAC) file can fail to load.

## How to check

1. Show the proxy that macOS uses.

   ```
   scutil --proxy
   ```
2. Open `System Settings › Network`, choose the service, then `Details › Proxies`.
3. Test the proxy host and port.

   ```
   nc -vz proxy.example.com 8080
   ```
4. Try the same page on a phone hotspot.

## How to fix it

1. Turn off proxies that you do not need under `Proxies`.
2. Correct the address and port. Ask the administrator for the right values.
3. Disconnect the VPN or app that set the proxy, then reload.
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

**Where does Chrome read its proxy from?**

Chrome uses the system proxy settings of macOS by default.

**Is the website down?**

No. Chrome could not reach the proxy. The site may be fine.

## 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

- [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.
- [“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.
- [ERR_TUNNEL_CONNECTION_FAILED in Chrome on Mac](https://kilobat.app/guides/err-tunnel-connection-failed): ERR_TUNNEL_CONNECTION_FAILED is a Chrome network error.
- [Corporate proxy certificates break Terminal tools on a Mac](https://kilobat.app/guides/corporate-proxy-certificates): Some company networks inspect HTTPS traffic.
