Error fix · Browser errors

This Site Can't Be Reached: Decode the Error and Fix It

Chrome's umbrella error for network failures. Use the line under the headline and the ERR_ code to find the real cause, then apply the right fix.

Error messageThis site can't be reached

By SiteDownCheck Editorial · Updated October 5, 2026 · 5 min read

"This site can't be reached" is the headline Chrome and Edge show for many different network failures. The headline tells you nothing; the sentence under it and the ERR_ code at the bottom tell you everything. Firefox's equivalents are "Hmm. We're having trouble finding that site" and "Unable to connect," and Safari shows "Safari Can't Connect to the Server" or "Safari Can't Find the Server."

Use this page as a decision table. Read the line under the headline, find it below, and go to the matching page.

Decode the sub-message

What Chrome says under the headlineCodeWhat happenedGo to
"server IP address could not be found"ERR_NAME_NOT_RESOLVED, DNS_PROBE_FINISHED_NXDOMAINDNS lookup failedERR_NAME_NOT_RESOLVED, NXDOMAIN
"refused to connect"ERR_CONNECTION_REFUSEDNothing accepts connections on that portConnection errors guide
"took too long to respond"ERR_CONNECTION_TIMED_OUTNo reply from the serverConnection errors guide
"unexpectedly closed the connection"ERR_CONNECTION_CLOSEDServer or middlebox hung upERR_CONNECTION_CLOSED
"The connection was reset"ERR_CONNECTION_RESETA TCP reset arrivedConnection errors guide
"didn't send any data"ERR_EMPTY_RESPONSEConnection closed with no replyERR_EMPTY_RESPONSE
"address is unreachable"ERR_ADDRESS_UNREACHABLENo route to the IP addressERR_ADDRESS_UNREACHABLE
"A network change was detected"ERR_NETWORK_CHANGEDYour connection changed mid-loadERR_NETWORK_CHANGED
"No internet"DNS_PROBE_FINISHED_NO_INTERNETYour device cannot reach DNSNO_INTERNET
"proxy server" problemsERR_PROXY_CONNECTION_FAILED, ERR_TUNNEL_CONNECTION_FAILEDProxy is down or refusesProxy failed, Tunnel failed
"can't provide a secure connection"ERR_SSL_PROTOCOL_ERROR, ERR_SSL_VERSION_OR_CIPHER_MISMATCHTLS handshake failedSSL protocol error, Cipher mismatch
"redirected you too many times"ERR_TOO_MANY_REDIRECTSRedirect loopToo many redirects

If the headline is "Your connection is not private," the cause is a certificate; go to Your connection is not private.

Step 1: Is it just you?

Spend two minutes on this before anything else. Open a different site, then check the target from outside your network with the Website Health Check or Down From Where. The outcomes:

  • Other sites also fail: the problem is your device or network. Start with the router, then DNS.
  • Only this site fails for you, but outside tools load it: something specific to your network, cache, DNS answer or IP address.
  • Outside tools also fail: the site or its hosting has a problem. See website down for everyone or just me.

If you are a visitor

Do these in order and stop when it works.

  1. Reload and check for typos. Remove www or add it, and try the other scheme if you know the site supports it.
  2. Restart the router. Wait for the lights to settle.
  3. Flush DNS. ipconfig /flushdns on Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS, resolvectl flush-caches on systemd Linux.
  4. Check proxy and VPN. Disable them and retry; leftover proxy settings are a common cause.
  5. Try another network or device. A phone hotspot helps separate a home or office problem from a site problem.
  6. Pause security software with web scanning for a test.
  7. Run Chrome's own diagnostic. The page offers "Running Connectivity Diagnostics" on Windows; use it for local adapter problems.
  8. Wait. If outside tools say the site is down, nothing on your side will help.

If you own the site

Treat a visitor's report as a symptom, and work from the outside in.

  1. Reproduce from a neutral location with curl -v https://example.com/ or the HTTP Status Checker. Note which stage fails: DNS, connect, TLS or HTTP.
  2. DNS: check A and AAAA records at several resolvers with the DNS Checker. Missing or wrong records and expired domains explain most "IP address could not be found" reports.
  3. Port: confirm 80 and 443 are open with the Port Checker. A stopped web server gives "refused," while a firewall that drops packets gives a timeout.
  4. Server health: if the machine is up but the site is not, follow why is my website down. Check disk, memory, the web server and the application process, using commands such as systemctl status nginx and df -h.
  5. Application layer errors appear as HTTP status codes, not as "can't be reached"; see fix 502, 503 and 504.
  6. CDN or security layer: a Cloudflare page with a numbered error is a different failure; see Cloudflare error 1016 and Cloudflare error 1020.
  7. Regional problems: if it fails only from some countries or ISPs, compare vantage points with Down From Where and ask your host about routing.

Communicate while you fix it. A status page lets visitors confirm it is not their device, and our status page guide explains what to publish.

Confirm the fix

  1. Run the Website Health Check and expect DNS, TCP, TLS and HTTP to pass.
  2. Load the site from a phone on mobile data and from a second location with Down From Where.
  3. Put an uptime monitor on the site so you hear about the next failure before visitors do.

Next steps

FAQ

Does "This site can't be reached" mean the site is down?

Not always. It can come from your own network, DNS, VPN or proxy. Check from another network or with an outside tool to find out.

What is the difference between this and a 503 error?

A 503 is an HTTP response from a server that is reachable but unavailable. "Can't be reached" means the browser never completed a connection to get any HTTP response.

Why does it work on my phone but not my laptop?

Different networks, DNS caches and proxy settings. Flush DNS on the laptop, turn off VPN or proxy, and test on the same Wi-Fi to isolate it.

Can I make my own site show something friendlier?

Not for the browser's network errors, since there is no server response to customize. You can reduce incidents by monitoring and by keeping DNS and hosting healthy.

Get notified when this fix updates

Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.

Keep reading

Error fix · Browser errorsERR_CONNECTION_REFUSED: Why Chrome Can't Connect and How to Fix ItChrome shows ERR_CONNECTION_REFUSED when the server answers but rejects the connection. Fix it as a visitor, or find the closed port or stopped service.4 min readError fix · Browser errorsERR_CONNECTION_TIMED_OUT: Causes and Fixes for Visitors and OwnersChrome says the server took too long to respond. Rule out your own network first, then check for dropped packets, firewalls and an overloaded origin.4 min readGuide · Downtime & ErrorsERR_CONNECTION_REFUSED vs Timed Out vs Reset: What Each MeansUnderstand what ERR_CONNECTION_REFUSED, ERR_CONNECTION_TIMED_OUT and ERR_CONNECTION_RESET reveal about TCP, and how to diagnose each with nc, curl, ss and mtr.10 min readGuide · Web BasicsJio or Airtel Broadband: Some Websites Not Opening? Fix ItInternet works but one site will not open on Jio, Airtel or another Indian ISP? Learn how to tell a DNS, IPv6, router or site problem and fix each.6 min readGuide · Downtime & ErrorsWebsite Down? The First 15 Minutes Checklist for OwnersA calm, numbered checklist for the first 15 minutes after your website goes down: confirm it, find the layer that broke, check the usual suspects, and know when to escalate.7 min readError fix · Browser errorsDNS_PROBE_FINISHED_NO_INTERNET: Meaning and How to Fix ItChrome shows DNS_PROBE_FINISHED_NO_INTERNET when it cannot reach any DNS server. Check the connection, router, DNS settings and firewall step by step.5 min read

This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.