How to Fix “This Site Can’t Be Reached” Errors

"This site can't be reached" is Chrome's catch-all message for a page that failed to load — and it comes with a cryptic error code that actually tells you a lot about what went wrong. The fix depends on that code. Below is what each of the common ones means and exactly how to fix it, starting with the fastest checks.

First: is it down for everyone, or just you?

Before you troubleshoot, find out whether the site is actually down or the problem is on your end. Run the address through WebsitePulseCheck — it checks the site from our servers, so if it loads for us but not for you, the issue is local (your network, DNS, or device) and the fixes below will help. If it's down for us too, it's the site, and there's nothing to do but wait. Our guide on how to check if a website is down covers this in more detail.

ERR_CONNECTION_TIMED_OUT

The server took too long to respond. Usually a network problem on your side or an overloaded server on theirs.

Fix: reload the page, check your internet connection, restart your router, and temporarily disable any VPN, proxy, or firewall to see if one is blocking the connection. Trying the site on mobile data quickly tells you whether it's your home network.

ERR_CONNECTION_REFUSED

The server actively refused the connection — often because it's down, or something (a firewall, extension, or security tool) is blocking it.

Fix: confirm the site is up with an external checker, disable browser extensions (especially ad blockers and security add-ons), and check your firewall or antivirus isn't blocking the site.

ERR_NAME_NOT_RESOLVED / DNS_PROBE_FINISHED_NXDOMAIN

A DNS problem: your device couldn't translate the domain name into a server address. This is one of the most common causes of "can't be reached."

Fix: flush your DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS), then switch to a fast public DNS like Cloudflare's 1.1.1.1 or Google's 8.8.8.8 in your network settings. If the domain was recently set up or moved, DNS changes can take a few hours to propagate.

ERR_CONNECTION_RESET

The connection was interrupted mid-request — often a flaky network, an overzealous firewall, or a VPN dropping the connection.

Fix: reload, restart your router, and toggle your VPN off (or on) to see if it changes anything.

The universal quick-fix checklist

Whatever the exact code, this sequence clears the large majority of "can't be reached" errors:

1. Reload the page and check your internet connection.
2. Try the site on another device or on mobile data to isolate your network.
3. Open it in an incognito window to rule out extensions and cache.
4. Flush your DNS and switch to 1.1.1.1 or 8.8.8.8.
5. Restart your router.
6. Temporarily disable VPN, proxy, firewall, or antivirus.

When it's a regional block or ISP issue

Sometimes a site is perfectly healthy but unreachable from your specific network — an ISP routing problem, or a geographic block on the content. If a checker shows the site is up for everyone but it still won't load for you, connecting through a VPN often restores access by routing around the block. See the note below.