ERR_ADDRESS_UNREACHABLE: Fix for Router, Mac & Android

What Is ERR_ADDRESS_UNREACHABLE?

ERR_ADDRESS_UNREACHABLE is the Chrome and Edge error that says "This site can't be reached. http://192.168.1.1/ is unreachable." (or whatever address you typed). In Chromium it's net error -109, and the source code explains it plainly: "The IP address is unreachable. This usually means that there is no route to the specified host or network" (net_error_list.h).

Most connection errors mean the browser found a path to the server and something went wrong on the way. This one means the operating system said there's no way there: Chrome shows -109 whenever the system reports "No route to host", "Network is unreachable" or "Host is down" (Chromium). Your device doesn't know how to get packets to that address, nothing on the local network answered for it, or the system refused to let the browser try.

That's why it mostly happens with local, private addresses: your router's admin page, a NAS, a printer, a security camera, Home Assistant, a Raspberry Pi, or a dev server on another computer. Those addresses only exist inside one network, so you can reach them only when you're actually on that network with nothing blocking the way.

Why It Happens: The 8 Usual Causes

Fix 1: Make Sure You're on the Same Network

Start here. To reach a router or local device, your phone or computer must be connected to that network's Wi-Fi or Ethernet:

• Phones: turn mobile data off while you test. Some phones switch to mobile data when the Wi-Fi has no internet, which makes local addresses unreachable.
• Laptops: check which Wi-Fi network you're actually on. Many homes have several (the main network, guest, a 5 GHz name, an extender).
• Compare addresses: your device's local IP and the target usually share the first three numbers, for example 192.168.1.23 and 192.168.1.1. If yours is 192.168.0.23, you're on a different subnet and 192.168.1.1 isn't reachable from there. The Subnet Calculator shows exactly which addresses are in the same subnet.

Fix 2: Find the Router's Real IP Address

Not every router uses 192.168.1.1. Common defaults include 192.168.0.1, 10.0.0.1, 192.168.1.254 and 192.168.100.1 (often a cable modem). Your router's address is shown as the default gateway:

# Windows (Command Prompt): look for "Default Gateway"
ipconfig

# macOS: the "gateway:" line
route -n get default

# Linux: the address after "default via"
ip route | grep default

On an iPhone, go to Settings → Wi-Fi → tap the (i) next to your network: the Router field is the address to open. On Android, open Settings → Network & internet → Internet → tap the gear next to your Wi-Fi network: the gateway is listed under network details (exact menu names vary by brand). Our router login guide lists the default address and login for 80+ routers and internet providers. The What Is My IP page shows your public IP, which is a different address from these private ones.

Fix 3: On a Mac, Allow Chrome Local Network Access

Starting with macOS 15 Sequoia, apps need permission to talk to devices on your local network (Apple TN3179). If Chrome, Edge or Brave was denied (or never asked), every local address shows ERR_ADDRESS_UNREACHABLE in that browser (Firefox shows its own error page), while Safari (whose traffic is exempt) and your iPhone reach it fine. It often shows up right after upgrading to macOS 15, when a NAS or router page stops loading in Chrome only.

To fix it:

• Open System Settings → Privacy & Security → Local Network.
• Turn the switch on for Google Chrome (and any other browser you use).
• Quit the browser completely (Cmd + Q) and reopen it, then try the address again.

Fix 4: Turn Off the VPN (or Allow LAN Access)

A full-tunnel VPN either sends traffic for local addresses into the tunnel, where the VPN server can't reach your home network, or blocks local traffic outright as part of its kill switch. Disconnect the VPN and try again.

If you need the VPN on, look in its settings for an option such as Allow LAN access, Local network sharing, or Bypass VPN for local network. Many consumer VPN apps have one. Workplace VPNs often block local access deliberately, so ask your IT team.

Fix 5: Leave the Guest Network or Turn Off Client Isolation

Guest Wi-Fi networks are designed to keep visitors away from your devices. They use client isolation (also called AP isolation), so devices on the guest network can reach the internet but not the router's admin page, your printer or your NAS. Some mesh systems and ISP routers enable it on the main network too.

Connect to the main network instead. If the setting is on for your main network, log in to the router from a wired computer and turn off AP isolation or client isolation in the wireless settings.

Fix 6: Check That the Device Is On and Still Has the Same IP

Routers hand out local addresses with DHCP, and after a reboot a NAS, camera or printer can come back with a different one. Your bookmark then points to an address that no longer exists.

• Ping it: ping 192.168.1.50. "Destination host unreachable" or no replies means nothing is answering at that address.
• Find its new IP: check the router's connected-devices list, or run arp -a to list devices your computer has recently talked to. A MAC address identifies the device even when its IP changes, and the MAC Lookup tool shows the manufacturer.
• Stop it happening again: create a DHCP reservation for the device in the router so it always gets the same IP.

Fix ERR_ADDRESS_UNREACHABLE on iPhone and Android

• iPhone, Local Network permission: browsers on iPhone load pages through Apple's WebKit, which doesn't need Local Network permission, so if Safari or Chrome can't open the address, look at the network, not a setting. Apps that talk to the device directly, such as a camera, NAS or smart-home app, do need it: Settings → Privacy & Security → Local Network.
• iPhone, check the subnet: Settings → Wi-Fi → tap (i) shows your IP Address and the Router address. If the first three numbers differ from the address you're opening, you're on the wrong network.
• Android: turn off mobile data while testing, turn off any VPN or ad-blocking app, and make sure you're not on the guest network.
• Both: forget the Wi-Fi network and rejoin it, which refreshes the IP address and route.

For Developers: net::ERR_ADDRESS_UNREACHABLE in Apps and Emulators

Developers usually see this error in an Android emulator or WebView, on a phone testing a local dev server, or from a server whose firewall rejects the connection:

• Android emulator: localhost inside the emulator is the emulator itself. Use 10.0.2.2 to reach your computer's localhost (Android).
• Real phone to dev server: the phone must be on the same Wi-Fi (not guest) and use the computer's LAN IP, for example http://192.168.1.23:3000. next dev already listens on all interfaces, but Vite listens only on localhost until you start it with vite --host; a server bound to localhost gives a refused connection instead.
• Mac on Sequoia or later: a dev server accepting connections from your phone doesn't need Local Network permission, and tools run from Terminal or over SSH are allowed automatically (Apple). A browser on the Mac does need it to open LAN addresses, as in Fix 3.
• Docker and WSL2 sit on their own virtual subnets that other devices can't reach. For Docker, publish the port (-p 3000:3000) and connect to the host's LAN IP, not the container's internal IP. For WSL2, turn on mirrored networking (Windows 11 22H2 or later) or forward the port with netsh interface portproxy (Microsoft).
• Linux servers with a reject rule: if a server's firewall blocks the port with an ICMP "host prohibited" or "administratively prohibited" reply, a Linux or Android client gets "No route to host" and Chrome shows ERR_ADDRESS_UNREACHABLE, even for a public server whose network is fine. Check the server's rules (sudo nft list ruleset or sudo iptables -S) and open the port.

ERR_ADDRESS_UNREACHABLE vs Similar Errors

If you can reach local devices but no websites, see Wi-Fi connected but no internet. For public websites that hang, see ERR_CONNECTION_TIMED_OUT, and for DNS failures, ERR_NAME_NOT_RESOLVED. A traceroute or the tracert command shows exactly where the path to an address ends.