ERR_ADDRESS_UNREACHABLE means Chrome could not find a route to the specific address you asked for, not that your whole internet connection is down. The three most common causes are a macOS or Windows permission blocking Chrome from reaching devices on your local network, a DNS or IPv6 resolution problem that only affects some sites, or a network-level block on a school, work, or hotel Wi-Fi. Which one applies to you depends on whether the failure is limited to local devices, limited to a handful of sites, or tied to one specific network.
Before you start
Applies to: Google Chrome. Not version-specific. No account sign-in is required for this fix. You may need access to your operating system’s privacy settings, and possibly your router if the issue turns out to be network-side.
Why ERR_ADDRESS_UNREACHABLE happens
This error fires when Chrome’s networking layer decides a destination address cannot be routed to at all, which is different from a timeout or a refused connection. One Google Chrome Community user described a version of this that only affected local devices: “This error only occurs when trying to access resources on my local network. I can browse everything on the internet just fine.” Another reported the opposite pattern: most websites unreachable while a few, like YouTube, kept working, which is a strong sign of a partial DNS or IPv6 problem rather than a hard network outage.
There are three branches, each with its own signal:
- Only local network resources fail (a printer, a NAS, a router’s admin page, an internal work tool), while the wider internet loads fine. Signal: other browsers on the same machine can reach the same local address without trouble.
- Most sites fail, but a few still load. Signal: the sites that keep working tend to be large, well-known ones, which points to a DNS or IPv6 resolution issue rather than a full outage.
- Only certain destinations fail, and only on one specific network (school, work, a hotel, a coffee shop). Signal: the same sites load fine the moment you switch to mobile data or a different Wi-Fi network.
How to fix ERR_ADDRESS_UNREACHABLE
If only local network resources fail (macOS and Windows)
On a Mac, this is very often a local-network permission Chrome does not have, not a bug. One thread traced it to exactly this after trying nearly everything else first.
- Open the Apple menu and go to System Settings.
- Select Privacy & Security in the sidebar.
- Click Local Network.
- Find Google Chrome in the list and make sure the toggle next to it is on. If it is already on, toggle it off, wait a moment, then toggle it back on.
- Quit and reopen Chrome, then try the local address again.
On Windows, the equivalent check is your firewall’s private-network rules. Open Windows Security > Firewall & network protection, select your active network, and confirm Chrome is allowed through on private networks.
If most sites fail but a few still load (DNS or IPv6)
This pattern usually means Chrome’s DNS results or IPv6 handling are inconsistent for your network.
- Type chrome://net-internals/#dns in the address bar and press Enter.
- Click Clear host cache.
- Reload the site that was failing.
- If it still fails, change your device’s DNS server to a public one like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) in your network settings, then try again.
If it only happens on one network (school, work, or public Wi-Fi)
Confirm this by switching to mobile data. If the same site loads instantly, the block is coming from that network’s firewall or content filter, not from your device or Chrome. On a managed school or work Chromebook or laptop, this is usually intentional, and the fix is on the administrator’s side, not yours. Contact your network administrator or IT department with the exact site and error, since they can usually see which rule is blocking it.
What does not fix this
One especially thorough Google Chrome Community report is useful here precisely because of what the person tried and ruled out. Before finding the real fix, they had already rebooted the Mac, rebooted and updated firmware on the router and switch, disabled their firewall, cleared the browser cache, deleted every extension, cleared the DNS host cache, cleared bad proxies, flushed socket pools, and even fully uninstalled and reinstalled Chrome. None of it worked, because the actual cause was an OS-level permission, not anything inside Chrome.
- Reinstalling Chrome. This resets Chrome’s own files and settings, but it cannot touch an operating-system permission or a network-level firewall rule, so the error returns immediately after reinstalling.
- Clearing cache, cookies, or extensions alone. These affect stored site data and browser behavior, not routing or permissions, so they rarely change anything for this specific error.
- Restarting your router. This can fix a genuinely dead connection, but if the router and every other browser can already reach the address, restarting it again will not change a Chrome-specific permission or a targeted network block.
Frequently asked questions
Why does ERR_ADDRESS_UNREACHABLE only affect local sites like my printer or router?
Modern operating systems ask apps for permission before they can discover or reach devices on your local network. If Chrome’s local network permission was turned off, denied by accident, or reset by a system update, it loses access to local addresses while normal internet browsing keeps working, since that traffic does not need the same permission.
Does flushing DNS actually fix ERR_ADDRESS_UNREACHABLE?
It helps specifically in the partial-failure pattern, where some sites resolve and others do not. It will not do anything for the local-network-permission cause or for a network-level block, which is why matching the fix to the right branch matters more than working through a generic list.
Is ERR_ADDRESS_UNREACHABLE the same on Android as on desktop?
The error itself means the same thing on every platform: Chrome cannot route to the address. On Android, the local-network-permission cause is less common, and a partial-DNS pattern or a carrier or Wi-Fi-level block is the more frequent explanation, so start with the network-based checks first on mobile.
ERR_ADDRESS_UNREACHABLE almost always points to something outside Chrome itself, a permission, a DNS quirk, or a network policy, which is why reinstalling the browser rarely helps. Work out which of the three patterns matches what you’re seeing before you change any settings.
