Fix ERR_ADDRESS_UNREACHABLE in Chrome (10 Solutions)

ERR_ADDRESS_UNREACHABLE appears in Chrome when the browser can’t reach the website’s server. The problem is usually on your end, not the website’s. Here are the fixes, starting with the quickest.

#Fix 1: Restart Your Router

Power cycle your router to clear temporary network issues. Unplug the router from power, wait 30 seconds, then plug it back in and allow 2-3 minutes for it to fully boot before trying the website again.

According to Google’s Chrome help page, network connectivity issues are the most common cause of address unreachable errors. In our testing, a simple router restart resolved this error in the majority of straightforward cases.

If that doesn’t work, factory reset the router using the small recessed button on the back. Press it with a pin for 5-10 seconds. This resets your Wi-Fi name and password to the factory defaults printed on the router’s label, so have those ready. You’ll need to reconnect all devices after the router reboots, which takes about 2 minutes.

The factory default credentials are usually printed on a sticker underneath the router.

#Fix 2: Clear Chrome’s DNS Cache

Chrome maintains its own DNS cache separate from your operating system. Clearing it can fix stale DNS entries. Open Chrome and type chrome://net-internals/#dns in the address bar, click “Clear host cache,” then go to chrome://net-internals/#sockets and click “Flush socket pools.”

This fix works when Chrome has cached an old IP address for a website that has since moved to a new server. In our testing, this resolved the error for websites that had recently changed hosting providers.

#Fix 3: Flush System DNS

Your operating system also caches DNS records. Flush them through Command Prompt:

On Windows: Press Windows + R, type cmd, press Enter, then run ipconfig /flushdns. You’ll see the message “Successfully flushed the DNS Resolver Cache” when it works.

On Mac: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your password when prompted.

According to Microsoft’s DNS troubleshooting guide, flushing DNS forces your computer to look up fresh IP addresses for every website you visit. We tested this on Windows 11 and the error cleared immediately after flushing.

#Fix 4: Disable Proxy or VPN

Proxy servers and VPNs route your traffic through intermediate servers, which can cause connection failures:

Disable proxy on Windows: Press Windows + R, type inetcpl.cpl, go to the Connections tab, click “LAN settings,” uncheck “Use a proxy server for your LAN,” and click OK. Restart Chrome after.

Disable VPN:

Turn off your VPN application or disconnect from the VPN server. Try loading the website without the VPN active.

According to Chrome’s proxy documentation, misconfigured proxy settings are a common cause of connection errors. If you need the VPN, try connecting to a different server location.

#Fix 5: Change DNS Servers to Google or Cloudflare

Your ISP’s DNS servers might be slow or down. Switch to public DNS servers:

On Windows: Go to Control Panel > Network and Internet > Network and Sharing Center, click “Change adapter settings,” right-click your active connection and select Properties. Select “Internet Protocol Version 4 (TCP/IPv4),” click Properties, choose “Use the following DNS server addresses,” and enter 8.8.8.8 as primary and 8.8.4.4 as secondary. Click OK and restart Chrome.

Google’s Public DNS documentation states that 8.8.8.8 and 8.8.4.4 are Google’s primary and secondary public DNS resolvers, designed for high reliability. Cloudflare’s 1.1.1.1 is another fast alternative with an average query time of 14 milliseconds.

#Should You Disable Chrome Extensions?

Extensions can interfere with network connections, especially ad blockers, VPN extensions, and privacy tools. Go to chrome://extensions/ and toggle off all extensions, then try loading the website. If it works, re-enable them one by one to find the culprit.

For a faster test, open Incognito (Ctrl + Shift + N). Extensions are off by default there.

#Fix 7: Reset TCP/IP Stack

If multiple fixes haven’t worked, reset your entire network stack:

1. Open Command Prompt as Administrator
2. Run these commands in order:

ipconfig /release
ipconfig /flushdns
ipconfig /renew
netsh int ip reset
netsh winsock reset

3. Restart your computer

This resets all network settings to their defaults. You may need to reconnect to your Wi-Fi network and re-enter the password afterward.

#Fix 8: Disable Chrome’s Preload Feature

Chrome preloads pages it thinks you’ll visit next, which can sometimes cause connection errors:

1. Open Chrome Settings
2. Go to Privacy and Security > Cookies and other site data
3. Turn off “Preload pages for faster browsing and searching”

This prevents Chrome from making speculative connections that might trigger the error.

#What if Only One Website Shows the Error?

If every other website loads fine, the problem is likely on the website’s end:

• The website’s server might be down or overloaded
• The domain name might have expired
• The website might be blocked in your region

Check if the website is down for everyone using a service like downdetector.com or try accessing it from your phone’s cellular data. If it’s down for everyone, wait for the website owner to fix it.

For other Chrome errors, check our guides on ERR_CACHE_MISS, Chrome being slow, SSL errors, plugin not supported in Chrome, or HDMI port not working.

#Bottom Line

Start with restarting your router and clearing Chrome’s DNS cache. These two fixes resolve most ERR_ADDRESS_UNREACHABLE errors. If they don’t work, flush your system DNS, disable proxy/VPN, or switch to Google’s public DNS servers. The TCP/IP reset is a last resort that fixes deeper network issues.

#Frequently Asked Questions