This Site Can’t Be Reached? 12 Proven Fixes That Work Instantly

Mid-meeting, mid-deadline, mid-checkout — and suddenly, a white screen appears on Chrome, displaying this error: “This site can’t be reached.” No explanation. No clues. Just a blank page where your website was supposed to be.

The This Site Can’t Be Reached error is Google Chrome’s catch-all message for any situation where your browser completely fails to connect to a website.

It’s one of the most searched browser errors in 2026 — and one of the most misunderstood, because it can appear alongside a dozen different error codes, each pointing to a different root cause.

The correct solution depends on which error code appears beneath the message. This guide provides 12 proven solutions, arranged from the quickest to the most advanced—so that you can stop guessing and start fixing this problem right now.

ERR_CONNECTION_TIMED_OUT: Complete Fix Guide

Instant Fixes — Try These First

Before changing any settings, complete these quick checks. These checks resolve the “Chrome can’t reach website” issue for most users immediately:

Check the URL carefully — A typo, missing “s” in https, or wrong domain (.com vs .net) triggers this instantly.

Test another website — Open Google or YouTube. If those load, the issue is specific to that site.

Try Incognito mode — Press Ctrl + Shift + N. Bypasses cache and extensions at once.

Restart your router — unplug it for 30 seconds, then plug it back in. This immediately fixes the problem in over 40% of cases.

Switch to mobile data — If the site loads on data, your Wi-Fi network is the cause.

Disable VPN or proxy — These are the #1 hidden cause of this error in 2026.

What Does “This Site Can’t Be Reached” Mean?

Definition: "This Site Can't Be Reached" is Google Chrome's generic error message displayed whenever the browser fails to establish a connection with a website's server. It is not a single error — it is a wrapper that covers multiple underlying connection failures. 

This is precisely what makes it so confusing—this single error, depending on the underlying cause, can convey entirely different meanings. Listed below are the most common error codes that appear alongside this message:

Error Code	Meaning
DNS_PROBE_FINISHED_NXDOMAIN	Domain not found in DNS — usually a DNS or typo issue
ERR_CONNECTION_TIMED_OUT	Server took too long to respond — network or server overload
ERR_CONNECTION_RESET	Connection was forcibly cut — VPN, firewall, or TCP issue
ERR_CONNECTION_REFUSED	Server actively rejected the connection — firewall or server down
ERR_EMPTY_RESPONSE	Server connected but sent no data — server crash
ERR_NAME_NOT_RESOLVED	DNS couldn’t translate domain to IP — DNS server failure

DNS_PROBE_FINISHED_NXDOMAIN: Complete Fix Guide

Why Does This Error Occur?

The ‘site can’t be reached’ error occurs due to glitches at various points in the connection chain. All known causes for this are listed here:

• DNS resolution failure — Browser can’t translate the domain name into an IP address.
• Unstable or no internet connection — the most obvious, yet most overlooked reason.
• Corrupted Browser Cache — Outdated cache data causes failed connection attempts.
• VPN or Proxy Misconfiguration — Redirected traffic reaches an inactive or blocked endpoint.
• Firewall or Antivirus Blocking — Security software blocks legitimate outgoing connections.
• Corrupt TCP/IP or Winsock Stack — A corrupt network stack sends malformed requests.
• Wrong hosts file entry — Manual domain mappings that override DNS incorrectly.
• Outdated or faulty network drivers — outdated drivers make data transmission unreliable.
• ISP throttling or blocking — Your internet provider restricts access to specific websites.
• Server-side downtime — The website itself is unreachable for everyone, not just you.

12 Step-by-Step Fixes For “This Site Can’t Be Reached”

1. Restart Your Router and Device

Simply restarting the router clears the DNS cache and refreshes your network connection—instantly resolving the issue of websites not loading in Chrome for most users.

• Unplug your router from the power socket completely.
• Wait for a full 30 seconds—do not rush this step.
• Plug the router back in and wait 60 seconds for it to fully reconnect.
• Restart your computer or phone as well. Then test the site.

2. Clear Browser Cache and Cookies

Corrupted cached files are the primary cause of the ‘Chrome can’t reach website‘ error. Deleting them forces Chrome to establish a completely new connection.

• Press Ctrl + Shift + Delete in Chrome (or Cmd + Shift + Delete on Mac).
• Set Time Range to “All time.”
• Check Cookies and other site data and Cached images and files.
• Click Clear data and reload the site.

3. Flush DNS Cache (Windows)

An outdated DNS cache is the primary cause of the DNS resolution errors that trigger this message. Flushing it initiates a completely fresh DNS lookup from scratch.

• Press Win + R, type cmd, run as Administrator.
• Run: ipconfig /flushdns → press Enter.
• Then run: ipconfig /release and ipconfig /renew
• Restart Chrome and test the site again.

4. Flush DNS Cache (Mac)

• Open Terminal (Applications → Utilities).
• Run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• Enter your password and press Return. Retest the website.

5. Change DNS Server to Google or Cloudflare

Your ISP’s DNS server may be slow, down, or blocking certain websites. Switching to a public DNS server immediately resolves this network connection problem.

• Go to Control Panel → Network & Sharing Center → Change adapter settings.
• Right-click active connection → Properties → IPv4 → Properties.
• Select “Use the following DNS server addresses.”
• Google DNS: Preferred 8.8.8.8 / Alternate 8.8.4.4
• Or Cloudflare DNS: Preferred 1.1.1.1 / Alternate 1.0.0.1
• Click OK, flush DNS (Method 3), and test the site again.

6. Disable VPN and Proxy Settings

VPNs and misconfigured proxy settings are the biggest hidden causes of the ‘This Site Can’t Be Reached‘ error. Therefore, always test without them first.

• Disconnect your VPN app completely — don’t switch servers.
• Press Win + R → type inetcpl.cpl → Connections → LAN Settings.
• Uncheck “Use a proxy server for your LAN.”
• Enable “Automatically detect settings” → click OK.
• Reload the site and check if the error is gone.

7. Disable Firewall and Antivirus Temporarily

Security software sometimes blocks legitimate web traffic — producing a browser connection error even on completely safe websites.

• Right-click your antivirus icon → Disable temporarily.
• Go to Control Panel → Windows Defender Firewall → Turn off temporarily.
• Test the site. If it loads — add the site to your antivirus whitelist.
• Re-enable all security software immediately after testing.

8. Disable Browser Extensions

Ad blockers, VPN extensions, and privacy tools frequently cause the site can’t be reached error by intercepting connection requests silently.

• Go to chrome://extensions in your address bar.
• Toggle all extensions off at once and reload the site.
• If it loads—then, to identify the culprit, restart them one by one.

9. Reset TCP/IP and Winsock 

A corrupted TCP/IP or Winsock stack causes malformed network packets that servers immediately reject. This deep reset fixes persistent cases of this site can’t be reached Windows 10 errors.

• Open Command Prompt as Administrator.
• Run: netsh winsock reset
• Run: netsh int ip reset
• Run: ipconfig /flushdns
• Restart your computer. Note: Some antivirus programs may need reinstalling after this.

10. Check and Fix the Windows Hosts File

This is a solution that most general guides completely overlook. A corrupted or modified hosts file can manually redirect or block specific domains—potentially leading to immediate ERR_NAME_NOT_RESOLVED errors or connection failures.

• Navigate to: C:\Windows\System32\drivers\etc\hosts
• Open with Notepad (right-click → Run as Administrator).
• Look for any entries containing the domain you’re trying to reach.
• Delete or comment out any suspicious lines (add # at the start).
• Save the file and reload Chrome.

⚠️ Only edit the hosts file if you see suspicious entries. Do not delete default localhost lines.

11. Update or Reinstall Network Drivers

Outdated or faulty network adapter drivers cause unstable connections—and on Windows laptops, especially following OS updates, they are a common and hidden cause of browser connection errors.

• Press Win + X → select Device Manager.
• Expand Network Adapters → right-click your active adapter.
• Click Update driver → Search automatically for drivers.
• If no update is found — right-click → Uninstall device → restart PC to auto-reinstall.

12. Fix on Android and iPhone

Seeing this site can’t be reached on Android or iPhone? The fix is simpler than on desktop — follow these steps:

• Toggle Airplane mode on for 10 seconds, then off — instantly resets your network stack.
• Clear Chrome app cache: Settings → Apps → Chrome → Storage → Clear Cache.
• Change DNS on Android: Settings → Network → Private DNS → type 1.1.1.1 (Cloudflare).
• On iPhone: Go to Wi-Fi settings → tap your network → configure DNS → add 8.8.8.8.
• Disable any VPN apps and retest. Update Chrome from the Play Store or App Store.

ERR_EMPTY_RESPONSE: Complete Fix Guide

How to Prevent “This Site Can’t Be Reached”

• Use Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) as your permanent DNS servers.
• Clear your browser cache every month — set a reminder to avoid the accumulation of corrupt files.
• Keep Chrome, Windows, and network drivers updated at all times.
• Audit Chrome extensions every few months — remove any you don’t actively use.
• Avoid toggling the VPN on or off while pages are actively loading—doing so immediately severs the connection.
• If you own a website — monitor your DNS records and server uptime with tools like UptimeRobot (free).

Pro Tips & Best Practices

Always read the error code below the main message — it's the fastest diagnostic tool you have. DNS_PROBE_FINISHED_NXDOMAIN points to DNS. ERR_CONNECTION_REFUSED points to firewall or server. ERR_CONNECTION_TIMED_OUT points to network. Each code has a specific fix — don't guess.

The Hosts file fix (Method 10) is one of those solutions that is often overlooked—especially for users who have installed third-party software or browser extensions that surreptitiously modify the Hosts file. Before performing a full TCP/IP reset, always be sure to check this.

Use downforeveryoneorjustme.com before any local troubleshooting. If the site is down globally — no local fix will help and you'll save yourself 30 minutes of unnecessary work.

Frequently Asked Questions