This Site Can't Be Reached: What It Means and How to Fix It

What the sub-error codes mean

Chrome always shows a specific error code beneath the main heading. Match yours to the list below before applying fixes:

• ERR_NAME_NOT_RESOLVED — DNS failed: the domain couldn't be converted to an IP. Fix: flush DNS, change DNS servers.
• ERR_CONNECTION_REFUSED — DNS worked but the server sent a TCP RST: it's down or a firewall is blocking the port.
• ERR_CONNECTION_TIMED_OUT — DNS worked but no response arrived within the timeout: server unreachable or overloaded.
• ERR_NETWORK_CHANGED — Your network connection changed while loading. Reload; it usually fixes itself.
• ERR_ADDRESS_UNREACHABLE — Routing failure: your network can't route packets to the destination IP.

Most likely causes (ranked)

1. DNS failure — stale cache, ISP DNS outage, or wrong DNS server configured
2. No internet connection — router, modem, or ISP issue
3. Firewall or proxy blocking Chrome or the specific domain
4. Server-side issue — the website itself is down (affects only that site)
5. Corrupted network stack on Windows

How to fix This Site Can't Be Reached

Step 1: Note the sub-error code and reload

Before anything else, read the error code Chrome shows (e.g. ERR_NAME_NOT_RESOLVED). Press Ctrl+Shift+R to hard-reload — transient errors from brief network hiccups clear immediately.

Step 2: Flush DNS cache and renew IP

Windows (Command Prompt as admin):

ipconfig /flushdns
ipconfig /release
ipconfig /renew

macOS:

sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder

This resolves most ERR_NAME_NOT_RESOLVED cases caused by stale DNS entries.

Step 3: Switch to a public DNS server

Change your DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google):
Windows: Network adapter → Properties → IPv4 → Use the following DNS server addresses.
macOS: System Settings → Network → [connection] → Details → DNS → add 1.1.1.1.

Step 4: Reset TCP/IP stack and Winsock (Windows)

Open Command Prompt as admin:

netsh int ip reset
netsh winsock reset

Restart your computer. This fixes a corrupted network stack causing ERR_CONNECTION_TIMED_OUT or ERR_CONNECTION_REFUSED across all sites.

Step 5: Check firewall, proxy, and VPN

Verify Windows Firewall allows Chrome (see ERR_NETWORK_ACCESS_DENIED guide). Check chrome://settings/system → Open proxy settings — disable any proxy not intentionally configured. Temporarily disable your VPN to rule it out.

Frequently Asked Questions

What does the sub-error code tell me?

ERR_NAME_NOT_RESOLVED: DNS failed — flush DNS and change servers. ERR_CONNECTION_REFUSED: server sent RST — it's down or firewalled. ERR_CONNECTION_TIMED_OUT: no response — server unreachable or overloaded. ERR_NETWORK_CHANGED: connection switched during load — just reload.

Why does this affect only one site vs. all sites?

One site failing: almost certainly server-side or that domain's DNS. All sites failing: your local network, DNS resolver, or ISP is the problem. All sites fail but ping works: DNS is broken — switch to 1.1.1.1. Nothing at all works: check your physical network connection and router.