---
title: "ERR_CONNECTION_CLOSED in Chrome on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/err-connection-closed"
description: "Chrome on your Mac shows ERR_CONNECTION_CLOSED. The connection ended with a TCP close. Test the network, VPN, proxy and server."
---

# ERR_CONNECTION_CLOSED in Chrome on Mac

ERR_CONNECTION_CLOSED is a Chrome network error. The Chromium source describes it as: “A connection was closed (corresponding to a TCP FIN).”

**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_CONNECTION_CLOSED in Chrome on Mac. Read https://kilobat.app/guides/err-connection-closed.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 “This site can’t be reached” with ERR_CONNECTION_CLOSED.
- The connection opens, then ends before the page loads.
- It may affect one site on a good connection.

## Likely causes

- **The server ends the connection.** The server, a load balancer or a firewall closes the connection after it opens.
- **A proxy or VPN.** A proxy or VPN can close connections that it does not allow.
- **A TLS or protocol mismatch.** The server may close a connection that uses a setting it does not accept.
- **Security software.** A security app can close connections to a site.

## How to check

1. Try the address in a Private window and another browser.
2. Try another network, such as a phone hotspot.
3. Run curl with details to see where the connection ends.

   ```
   curl -v https://example.com
   ```
4. Show the system proxy settings.

   ```
   scutil --proxy
   ```

## How to fix it

1. Turn off the VPN, proxy or security app for a short test. Turn it on again after.
2. Clear the site’s cookies in Chrome, then reload.
3. If you run the site, check the server and firewall logs.
4. If only one network fails, ask its administrator.

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

**Is ERR_CONNECTION_CLOSED the same as ERR_CONNECTION_RESET?**

No. The Chromium source ties a close to a TCP FIN and a reset to a TCP RST.

**Is the problem in my Mac?**

Test curl and another network. If both fail, the cause is likely outside your Mac.

## 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_CONNECTION_RESET in Chrome on Mac](https://kilobat.app/guides/err-connection-reset): ERR_CONNECTION_RESET is a Chrome network error.
- [ERR_EMPTY_RESPONSE in Chrome on Mac](https://kilobat.app/guides/err-empty-response): ERR_EMPTY_RESPONSE is a Chrome network error.
- [ERR_SSL_PROTOCOL_ERROR in Chrome on Mac](https://kilobat.app/guides/err-ssl-protocol-error): ERR_SSL_PROTOCOL_ERROR 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.
