How to Fix ERR_ADDRESS_UNREACHABLE (2026)

TL;DR

ERR_ADDRESS_UNREACHABLE is Chromium network error -109, and it means your machine got an IP address and then had no route to send packets to it. DNS already worked, so flushing the resolver cache or clearing browser data almost never helps. The real causes are broken IPv6 on a dual-stack network, a LAN address that no longer exists, or a VPN or proxy that left a stale route behind. Test each address family separately, check the routing table, then fix the layer that is actually broken.

Chrome shows ERR_ADDRESS_UNREACHABLE when it has an address for a site and cannot get a packet to it. Most guides treat this as a DNS problem and send you through cache flushes that change nothing, because the name lookup already succeeded before the error was raised. In this article, we'll explore what the error signals, how to locate the hop that breaks, and how to fix it on desktop, mobile, and inside a proxy setup.

What ERR_ADDRESS_UNREACHABLE Actually Means

Chromium assigns this failure the code -109 and describes it as an unreachable IP address, usually meaning there is no route to the specified host or network. Take that wording literally. Name resolution already finished. A hostname that failed to resolve returns ERR_NAME_NOT_RESOLVED (-105), and a server actively rejecting the connection returns ERR_CONNECTION_REFUSED (-102).

That places the failure at the connect stage. Your device picked a destination address, consulted its routing table, and found nothing capable of carrying traffic there. The kernel returns EHOSTUNREACH or ENETUNREACH, and Chrome maps that to -109. Advice about DNS propagation, expired certificates, or corrupted cookies targets other layers and will not move this error.

How to Fix ERR_ADDRESS_UNREACHABLE

Confirm Where the Route Breaks

Prove the route exists before touching browser settings. On Windows, Test-NetConnection with the -DiagnoseRouting switch prints the selected route, the source address, and the reason each candidate route was preferred or blocked.

POWERSHELL

Test-NetConnection -ComputerName example.com -DiagnoseRouting -InformationLevel Detailed

On Linux and macOS, ip route get and route get answer the same question. Then test both address families in isolation:

ABAP

curl -4 -sS -o /dev/null -w '%{http_code}\n' https://example.com
curl -6 -sS -o /dev/null -w '%{http_code}\n' https://example.com

A status code on the first line and an error on the second narrows the problem to IPv6 in one step.

Broken IPv6 on a Dual-Stack Network

This is the most common version of the error. Your router advertises IPv6, the hostname carries an AAAA record, and Chrome prefers the IPv6 address. When the upstream path is dead, the connection fails instantly with no route. Happy Eyeballs races both families and falls back to IPv4, but a router advertising a prefix it cannot actually route breaks the assumption that algorithm depends on. Disabling IPv6 on the adapter clears the symptom. Fixing the advertisement clears the cause.

Local Addresses That No Longer Exist

When the error hits only a LAN address like 192.168.1.50, the target device is powered down, sitting on a different subnet, or holding a new DHCP lease. Bookmarks pointing at router panels and NAS boxes go stale the moment a lease rotates. Reserve a static lease for anything you reach by raw IP.

Stale VPN, Proxy, and Extension Routes

A VPN client that exits badly leaves routes pointing at an interface that is gone. Proxy extensions do the same by holding a rule for a host they can no longer reach. System proxy settings, Chrome flags, and extension rules stack on each other, so check all three rather than assuming the last one you edited is in effect.

Also Read: How to Use a Proxy Server on Any Device

When a Proxy Sits in the Path

With an upstream proxy, the routing question moves to the proxy side. Your machine reaches the proxy fine, the proxy fails to reach the target, and the browser reports the same message. Two cases dominate: the target is IPv6-only and the proxy has no IPv6 route, or the endpoint sits on a network your device cannot reach.

Test the endpoint outside the browser before blaming Chrome.

ABAP

curl -x http://user:pass@gateway.proxyon.io:8000 -sS https://api.ipify.org

An address in the response means the proxy path works and the fault is browser-level. A routing error there means the endpoint or its credentials are wrong, and the proxy formatter converts a list into the syntax your client expects. For IPv6 targets, confirm the exit carries IPv6 with the IPv6 tester before assuming the site is down. Residential proxies and datacenter proxies exit over IPv4 by default, while IPv6 rotating proxies suit destinations reachable only over IPv6.

Also Read: Proxy SwitchyOmega Explained

FAQ Section

What does ERR_ADDRESS_UNREACHABLE mean?

Chrome resolved the hostname to an IP address and your operating system had no route to that address. The failure is in routing, not in name lookup.

Is ERR_ADDRESS_UNREACHABLE a DNS problem?

No. A DNS failure produces ERR_NAME_NOT_RESOLVED. Seeing -109 confirms resolution already succeeded.

Is it a Wi-Fi problem?

Sometimes. A router with a broken IPv6 advertisement or a wrong subnet mask triggers it, which is why the same site often loads over mobile data.

How do I fix it on Android?

Toggle airplane mode to force a fresh DHCP and router advertisement, then forget and rejoin the network. If it persists on one network only, the router is the suspect.

Does disabling IPv6 fix it?

Often, because it forces Chrome onto the IPv4 path. That is a workaround rather than a repair, and it hides a router or ISP misconfiguration that will surface again.

Why does only one site show the error?

That site publishes an AAAA record or lives on an address range your network has no route to. Everything without an AAAA record keeps working over IPv4.

Final Thoughts

ERR_ADDRESS_UNREACHABLE is a routing error wearing a browser error's clothing, and treating it as a DNS issue wastes the first hour of every troubleshooting session. Test IPv4 and IPv6 separately, read the routing table, and the broken layer identifies itself in under a minute. When a proxy is in the path, verify the endpoint with curl before touching browser settings, since the browser only reports what the tunnel hands back.