ERR_ADDRESS_UNREACHABLE in Chrome on Mac

ERR_ADDRESS_UNREACHABLE is a Chrome network error. The Chromium source describes it as: “The IP address is unreachable. This usually means that there is no route to the specified host or network.”

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

My Mac has this problem: ERR_ADDRESS_UNREACHABLE in Chrome on Mac. Read https://kilobat.app/guides/err-address-unreachable.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: 10 November 2026

Symptoms

  • Chrome shows “This site can’t be reached” and ERR_ADDRESS_UNREACHABLE.
  • The name resolves, but the Mac has no route to the address.
  • It happens with local addresses and VPNs.

Likely causes

  • The address is on another network. A private address, such as 192.168.x.x, works only on its own network.
  • A VPN is off or has no route. A company address needs the VPN to be on.
  • IPv6 has no route. The name resolves to an IPv6 address that this network does not reach.
  • A wrong subnet. The Mac and the target use different, unrelated network ranges.

How to check

  1. Show the Mac’s addresses and routes.

    netstat -rn -f inet
  2. Test the route to the address.

    route -n get 192.168.1.10
  3. Ping the address.

    ping -c 3 192.168.1.10
  4. Test IPv6 separately.

    curl -6 -I https://example.com

How to fix it

  1. Join the network that holds the address, or connect the VPN.

  2. If IPv6 fails, see IPv6 problems on a Mac.

  3. Fix overlapping network ranges. See Tailscale and another VPN conflict on a Mac.

  4. Check the address with the device’s owner.

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. If the address is on your local network, add the app. Kilobat then says whether its Local Network access is the thing to test.

    kilobat why http://192.168.1.20 --app com.google.Chrome
  3. 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.

Questions

Is this a DNS problem?

No. The name resolved. The Mac has no route to the resulting address.

Why do only local addresses fail?

They exist only on their own network. A VPN or the right Wi-Fi gives a route.

Sources

Checked on 10 November 2026.