ERR_ADDRESS_UNREACHABLE: How to Fix It on Chrome, Windows, Android, and Local Networks

by

The ERR_ADDRESS_UNREACHABLE error means your browser tried to reach a website or local IP address, but the destination could not be reached from your device or network. In plain terms, the route failed before the page could load.

This problem is common in Chrome and other Chromium-based browsers. It often comes from router issues, wrong local IP addresses, DNS problems, VPN conflicts, broken proxy settings, or a device that is trying to access a network resource that no longer exists.

Quick Fix

  • Refresh the page and try again.
  • Check whether the website address or local IP is correct.
  • Restart your router and your device.
  • Disconnect and reconnect to Wi-Fi or Ethernet.
  • Turn off VPN or proxy temporarily.
  • Try the same address in another browser.
  • If it is a local IP, make sure the target device is powered on and on the same network.
  • Flush DNS cache and renew your IP address.
  • Restart Chrome and disable browser extensions.
  • Test whether other sites or local addresses work.

What Is ERR_ADDRESS_UNREACHABLE?

ERR_ADDRESS_UNREACHABLE is a browser network error. It appears when the browser knows what address it wants to open, but your system cannot actually reach that address.

This is different from a normal “site down” problem. The issue is often between your device and the destination. That destination might be:

  • A public website
  • A local router page such as 192.168.0.1 or 192.168.1.1
  • A NAS, printer, IP camera, or server on your home network
  • A private company resource behind VPN
  • A website tied to a broken DNS or routing path

If you see ERR_ADDRESS_UNREACHABLE, the connection usually fails before a full response comes back. The browser can start the request, but it cannot reach the destination host through the network path currently available.

This error is especially common when users try to:

  • Open a router admin panel
  • Access a local device by IP
  • Load a site after changing DNS or proxy settings
  • Use Chrome after a VPN session
  • Open a server or intranet page that is no longer reachable

Why ERR_ADDRESS_UNREACHABLE Happens

There is no single cause. But in real-world cases, the list is usually short.

1. The IP Address Is Wrong

This is one of the most common reasons. The address you entered may be invalid, outdated, or pointing to a device that is no longer using that IP.

Examples:

  • You typed 192.168.1.1, but your router uses 192.168.0.1
  • A printer or NAS changed IP addresses after reboot
  • A bookmarked local admin page points to an old address
  • The site URL contains a typo

2. The Target Device Is Offline

If you are trying to reach a router, camera, server, NAS, or other local device, that device may simply be off, disconnected, or frozen.

  • The device lost power
  • The Ethernet cable is unplugged
  • Wi-Fi dropped
  • The device crashed or rebooted

3. Your Device Is on the Wrong Network

You may be connected to the internet, but not to the network that contains the destination device.

This happens often when:

  • Your phone switches from Wi-Fi to mobile data
  • Your laptop joins a guest network instead of the main network
  • A mesh system separates devices across isolated networks
  • VLAN or subnet settings prevent direct access

4. DNS Problems

If the error appears on a public website, the issue may be DNS-related. The browser may resolve the address incorrectly, or your system may be using stale DNS cache entries.

Typical cases include:

  • Broken DNS cache
  • Bad custom DNS server
  • DNS changes not fully propagated
  • Router sending incorrect DNS responses

5. VPN or Proxy Conflicts

A VPN can change routes and DNS behavior. A proxy can send browser traffic to a path that no longer works. After the VPN disconnects, Chrome may still try to use old routes or settings.

  • VPN kill switch still active
  • Corporate proxy enabled outside the office
  • Split tunnel routes broken
  • Browser proxy extension interfering with requests

6. Local Network Routing Problems

Home and office networks can develop routing issues. This is more common after router resets, firmware changes, IP conflicts, or using multiple routers at once.

You may see this if:

  • Two routers are handing out IP addresses
  • The default gateway is wrong
  • The local subnet changed
  • A static IP is misconfigured

7. Browser or Extension Issues

If only Chrome shows the problem, the cause may be inside the browser rather than the network.

  • Corrupt browser cache
  • Proxy extension misrouting traffic
  • Privacy or ad-block extension blocking requests
  • Broken Chrome network state

How to Fix ERR_ADDRESS_UNREACHABLE Step by Step

Work through these fixes in order. The goal is to isolate whether the problem is the address, the target device, the browser, or the network path.

1. Check the Address Carefully

Start with the most basic but most effective step: confirm that the address is correct.

Check for:

  • Typos in the URL
  • Wrong IP address
  • Missing or extra characters
  • Old bookmarks pointing to outdated local IPs

If you are opening a router or device page, do not assume the default IP. Many routers use different addresses depending on model or prior setup.

Examples to verify:

  • 192.168.0.1
  • 192.168.1.1
  • 10.0.0.1
  • A hostname like router.local or nas.local

2. Confirm the Destination Device Is Online

If you are trying to reach a local device, make sure it is actually powered on and connected.

  • Check status lights
  • Confirm Ethernet cables are connected
  • Make sure the device joined Wi-Fi successfully
  • Restart the target device if needed

This applies to routers, modems, printers, cameras, NAS boxes, smart hubs, and local servers.

3. Make Sure You Are on the Correct Network

This matters more than many users realize. You can be online but still unable to reach a local address because you are on the wrong network segment.

Check:

  • Are you connected to Wi-Fi, not mobile data?
  • Are you on the main network, not guest Wi-Fi?
  • Is your computer using the same subnet as the target device?

For example, if your device has an IP like 192.168.1.x and the target device uses 192.168.0.x, they may not be on the same reachable subnet unless routing is configured correctly.

4. Restart the Router and Your Device

This clears temporary routing failures, ARP issues, DHCP problems, and stale local sessions.

  1. Shut down your computer or disconnect your phone from the network.
  2. Restart the router.
  3. Wait until the router fully comes back online.
  4. Reconnect your device.
  5. Try the address again.

If you are trying to access a modem, router, or switch admin page, restart the target device only if doing so is safe for your setup.

5. Disconnect VPN and Disable Proxy

If the destination is local or internal, a VPN can break the route. The same applies to a proxy.

Do this:

  • Disconnect from the VPN
  • Close the VPN app fully
  • Turn off any kill switch
  • Disable manual proxy settings
  • Turn off proxy-related browser extensions

This step is especially important if the error started right after using a company VPN or privacy tool.

6. Flush DNS Cache

If the problem involves a website or hostname, clear the DNS cache and try again.

On Windows, open Command Prompt and run:

ipconfig /flushdns

Then reopen the browser and reload the page.

This can help when:

  • A site recently changed IP addresses
  • Your system cached an incorrect address
  • A router gave out bad DNS responses

7. Renew the Local IP Address

Sometimes your device has a bad lease or incorrect route from DHCP.

On Windows, run:

ipconfig /release
ipconfig /renew

Then test again.

This is useful when the local network changed, the router rebooted, or the system woke from sleep in a bad state.

8. Clear Chrome Cache and Test Without Extensions

If the error appears only in Chrome, strip the browser down before changing deeper system settings.

  1. Open Chrome in Incognito mode.
  2. Try the same address.
  3. If it works, disable extensions one by one.
  4. Clear browser cache.
  5. Restart Chrome.

Pay close attention to:

  • VPN extensions
  • Proxy switchers
  • Security extensions
  • Ad blockers
  • Privacy tools

9. Test the Address in Another Browser or Device

This step tells you whether the problem is browser-specific, device-specific, or network-wide.

  • If another browser works, Chrome is the issue.
  • If another device works, your current device is the issue.
  • If nothing works, the destination or network path is the issue.

This is one of the fastest ways to avoid guessing.

10. Check Your Default Gateway

If you cannot reach your router or local devices, your default gateway may be wrong.

On Windows, run:

ipconfig

Then look for:

  • Your IPv4 address
  • Your subnet mask
  • Your default gateway

If the gateway looks wrong, blank, or outside your network range, the local routing path may be broken.

11. Reset the Network Stack

If the route is broken at the system level, reset the local networking components.

On Windows, open Command Prompt as Administrator and run:

netsh winsock reset
netsh int ip reset

Restart the computer after running these commands.

This can fix:

  • Corrupt Winsock configuration
  • TCP/IP problems
  • Old routes left behind by VPN or security tools

12. Check for IP Conflicts or Static IP Problems

If a device uses a manual static IP that does not match the network, it may become unreachable.

Look for these problems:

  • Two devices using the same IP
  • Manual IP outside the router range
  • Wrong subnet mask
  • Wrong gateway on a static client

This is common with printers, cameras, NAS devices, and old PCs configured manually years ago.

13. Change DNS Servers

If a public website triggers ERR_ADDRESS_UNREACHABLE, test a different DNS provider.

  • Google DNS: 8.8.8.8 and 8.8.4.4
  • Cloudflare DNS: 1.1.1.1 and 1.0.0.1

This can help if your ISP DNS is unstable or your router is handing out bad DNS responses.

14. Restart or Update the Target Network Device

If the unreachable address belongs to a router, switch, printer, NAS, or camera, the problem may be on that device.

Try:

  • Restarting the device
  • Checking whether it received a new IP from DHCP
  • Reviewing its network settings
  • Updating firmware if it often disappears from the network

Advanced Troubleshooting

If the normal fixes do not solve the problem, move to deeper checks.

Ping the Address

Use ping to test basic reachability.

ping 192.168.1.1

Or:

ping example.com

Results matter:

  • If ping fails for a local IP, the device may be offline or not on the same network.
  • If ping works but the browser fails, the issue may be browser-specific or service-specific.
  • If hostname ping fails but IP ping works, DNS may be the real problem.

Trace the Route

If the destination is remote, use route tracing to see where the path breaks.

tracert example.com

This can help reveal:

  • Local gateway failure
  • ISP routing problems
  • VPN route interference
  • Network hops that stop responding

Review Router DHCP and LAN Settings

If you cannot reach multiple local devices, the router may be handing out bad addresses or using a different subnet than expected.

Check for:

  • DHCP enabled on more than one router
  • Changed LAN IP range
  • Guest isolation settings
  • AP isolation enabled

Look for Double Router Problems

If you have both a modem-router and a separate Wi-Fi router, local routing can break easily.

Common signs:

  • Some devices are on 192.168.0.x, others on 192.168.1.x
  • Local devices cannot see each other
  • Admin pages work only from one part of the network

In these cases, double NAT or misconfigured LAN routing may be behind the error.

Reset Chrome Settings

If all network tests look normal but Chrome still shows ERR_ADDRESS_UNREACHABLE, reset Chrome settings to default.

This can fix:

  • Damaged browser network preferences
  • Bad extensions
  • Hidden proxy-related changes

Prevention Tips

  • Keep your router firmware updated.
  • Do not rely on old bookmarks for local IP addresses.
  • Reserve static DHCP leases for important local devices.
  • Avoid using multiple routers unless you know the network layout.
  • Disable VPN and proxy when accessing local devices, unless required.
  • Document your router IP, subnet, and device IP assignments.
  • Remove browser extensions you do not need.
  • Use stable DNS servers if your default DNS often fails.

A simple practice helps a lot: when a local device matters, assign it a reserved IP in the router instead of letting it change randomly.

When to Contact Support

Contact your ISP if:

  • Public websites fail across multiple devices
  • Remote addresses become unreachable often
  • The route fails beyond your local network

Contact the device vendor or admin if:

  • A NAS, printer, or camera keeps disappearing from the network
  • The target device no longer responds after firmware changes
  • You cannot access a company server or VPN-only resource

Focus on browser repair if:

  • Other devices work
  • Other browsers work
  • Only Chrome shows ERR_ADDRESS_UNREACHABLE

FAQ

What does ERR_ADDRESS_UNREACHABLE mean in Chrome?

It means Chrome tried to connect to an address, but your device could not reach that destination through the current network path. The problem may be the address itself, the route, the target device, or a local browser or system setting.

Why do I get ERR_ADDRESS_UNREACHABLE when opening 192.168.1.1?

Usually because that is not your router’s current IP address, your device is on the wrong network, the router is offline, or local routing is broken. Many routers use different gateway IPs such as 192.168.0.1 or 10.0.0.1.

Can a VPN cause ERR_ADDRESS_UNREACHABLE?

Yes. A VPN can change routes, DNS behavior, and local network visibility. This is especially common when trying to access local IP addresses while the VPN is active.

How do I fix ERR_ADDRESS_UNREACHABLE on Windows?

Start by checking the address, confirming the target device is online, disconnecting VPN, flushing DNS, renewing IP, and resetting the network stack if needed. Also test another browser to isolate Chrome-specific problems.

Why does ERR_ADDRESS_UNREACHABLE affect only one browser?

If other browsers work, the issue is usually caused by browser cache, extensions, proxy settings, or corrupted network preferences inside that browser.

Final Thoughts

ERR_ADDRESS_UNREACHABLE is usually a routing or reachability problem, not a mysterious browser failure. Most cases come down to a wrong address, offline target device, broken DNS, VPN conflict, or a local network path that no longer makes sense.

Start with the address and the network path. Confirm the target exists, make sure you are on the right network, then move to DNS, VPN, Chrome, and router checks. That sequence solves the issue faster than random trial and error.

Leave a Comment