ERR_ADDRESS_UNREACHABLE Browser Origin: On your device Last updated 15 Oct 2026

Chrome: This site can’t be reached — The webpage at https://… might be temporarily down. ERR_ADDRESS_UNREACHABLE

The computer has no route to the server’s IP address — often an IPv6 problem, a wrong local-network address, or a VPN routing issue.

Exact message you may see might be temporarily down
Explore the map of this error Full error map →
Seen on: Chrome Edge

Meaning

"Unreachable" means the network stack could not find any path. It is typical for an IPv6 address on a network without IPv6, an internal (192.168.x.x) address opened from outside the LAN, or a VPN split-tunnel that does not include the subnet.

Common causes

  • Site resolves to an IPv6 address but your network has no IPv6 route
  • Opening a private LAN address from outside that network
  • VPN route missing for that subnet
  • Firewall blocking the destination
  • Typo in the IP address

⚡ Quick fix

  1. Test with IPv4: curl -4 -I https://example.com
  2. Connect to the right network/VPN for private addresses
  3. Disable IPv6 on the adapter only as a test

Detailed fix by platform

Linux

  1. ip route get <ip> shows whether a route exists; ping -4 vs ping -6 compares IPv4/IPv6

Windows

  1. route print lists routes; ipconfig /all shows the gateway; test ping <ip>

How to diagnose

  1. Address — IPv4, IPv6 or private?
  2. Route — Does ip route / route print contain a path?
  3. VPN — On or off?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

captive portal — Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites (Browser)captive portalDNS_PROBE_FINISHED_NO_INTERNET — Chrome: No internet — DNS_PROBE_FINISHED_NO_INTERNET (DNS probe finished, no internet) (Browser)DNS_PROBE_FINISHED_NO…DNS_PROBE_FINISHED_NXDOMAIN — Chrome: This site can’t be reached — server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN (Browser)DNS_PROBE_FINISHED_NX…ERR_CONNECTION_ABORTED — Chrome: The connection was aborted — ERR_CONNECTION_ABORTED (software on your computer caused it) (Browser)ERR_CONNECTION_ABORTEDERR_CONNECTION_CLOSED — Chrome: This site can’t be reached — example.com unexpectedly closed the connection. ERR_CONNECTION_CLOSED (Browser)ERR_CONNECTION_CLOSEDERR_CONNECTION_TIMED_OUT — ERR_CONNECTION_TIMED_OUT: This site can’t be reached — example.com took too long to respond (Browser)ERR_CONNECTION_TIMED_…ERR_INTERNET_DISCONNECTED — Chrome: No internet — ERR_INTERNET_DISCONNECTED (You are not connected to the internet) (Browser)ERR_INTERNET_DISCONNE…ERR_NAME_NOT_RESOLVED — net::ERR_NAME_NOT_RESOLVED (This site can't be reached — server IP address could not be found) (JavaScript)ERR_NAME_NOT_RESOLVEDERR_ADDRE…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.