Error guide / This site can't be reached

This site can't be reached

This site can't be reached is Chrome's generic screen for when the browser couldn't connect to the server. A more specific reason hides underneath: DNS didn't resolve, the server didn't answer, or it dropped the connection. Look at the small code under the heading, that's what tells you what actually broke.

What causes it

The cause depends on the code below: DNS_PROBE_FINISHED_NXDOMAIN and ERR_NAME_NOT_RESOLVED point to the domain's DNS, while ERR_CONNECTION_TIMED_OUT or ERR_CONNECTION_REFUSED mean the server is unreachable or rejecting connections. So it's either DNS, the site's server, or your own network.

How to fix it

1. Read the small error code under the message; it drives the whole plan.
2. If it's NXDOMAIN or NAME_NOT_RESOLVED, check the domain's DNS records (an A record pointing to the server IP).
3. If it's TIMED_OUT or CONNECTION_REFUSED, check that the web server is running and the firewall isn't blocking the port.
4. Open the site from another network or mobile data to rule out a local problem.
5. Flush the DNS cache (ipconfig /flushdns) and restart the browser.
6. Run the domain through the check below to see whether it resolves and whether the server responds.

Related errors

• DNS_PROBE_FINISHED_NXDOMAIN DNS_PROBE_FINISHED_NXDOMAIN error
• ERR_NAME_NOT_RESOLVED ERR_NAME_NOT_RESOLVED error
• DNS_PROBE_FINISHED_NO_INTERNET DNS_PROBE_FINISHED_NO_INTERNET error
• Домен не резолвиться після зміни NS Domain not resolving after an NS change or migration