When Chrome fails to open a site, it shows an error code under the message "This site can't be reached". That code shows at which stage the connection failed: looking up the site's address (DNS), connecting to the server, or checking security. Once you know the stage, you don't have to guess.
| Error code | Meaning | Usual culprit |
|---|---|---|
| ERR_INTERNET_DISCONNECTED | The device isn't connected to any network | The device's Wi-Fi or cable |
| DNS_PROBE_FINISHED_NO_INTERNET | Connected to Wi-Fi, but no internet | Router or ISP |
| DNS_PROBE_FINISHED_NXDOMAIN | The site name wasn't found | Spelling, DNS, or the domain itself |
| ERR_NAME_NOT_RESOLVED | The site name couldn't be translated into an IP address | DNS |
| ERR_CONNECTION_TIMED_OUT | The server didn't answer in time | Slow network, the site, or blocking |
| ERR_CONNECTION_REFUSED | The server refused the connection | The site, a proxy, or a firewall |
| ERR_CONNECTION_RESET | The connection was cut midway | Firewall, blocking, or an unstable signal |
| ERR_NETWORK_CHANGED | The network changed while the page loaded | Device switched Wi-Fi or a VPN reconnected |
| ERR_TOO_MANY_REDIRECTS | The page keeps redirecting in a loop | Cookies or site settings |
| NET::ERR_CERT_... and ERR_SSL_PROTOCOL_ERROR | The HTTPS security check failed | Device clock, public Wi-Fi, or the site's certificate |
First steps for any error
- Open another site, such as a search engine. If other sites fail too, the problem is the network, not the site.
- Try another device or mobile data. If that works, the problem is your device or Wi-Fi.
- Turn off VPNs, proxies, and extensions for a moment. Incognito mode helps you test without extensions.
- Restart the router if every device in the house is affected. See also first steps when Wi-Fi is completely down.
How to fix DNS_PROBE_FINISHED_NXDOMAIN and ERR_NAME_NOT_RESOLVED
Both errors mean Chrome couldn't find the site's IP address. DNS works like the internet's phone book, explained in what DNS is and how it works. Work through these in order:
- Check the spelling. One wrong letter is enough to trigger NXDOMAIN.
- Clear the DNS cache. On Windows, open Command Prompt and run
ipconfig /flushdns. In Chrome, openchrome://net-internals/#dnsand click Clear host cache. - Switch DNS to a public DNS service. See how to change DNS on a phone or laptop.
- Check Chrome's Secure DNS (Settings, Privacy and security, Security). If your office network uses internal DNS, this option sometimes stops internal sites from being found.
If you see a message that the DNS server isn't responding, follow how to fix a DNS server that isn't responding. If the owner simply didn't renew the domain, there's nothing to fix on your end.
How to fix ERR_CONNECTION_TIMED_OUT
The site's address was found, but the server didn't answer. If it happens on many sites, the network is probably very slow or dropping out. Measure it first with a speed test and ping and traceroute.
If it's only one site, there are three possibilities: the site is down, it's blocked on your network, or the packet size doesn't suit the network. The last is rare but distinctive: the site starts loading, then stalls. It's explained in what MTU is.
How to fix ERR_CONNECTION_REFUSED and ERR_CONNECTION_RESET
REFUSED means something answered but declined. Most often the site is having trouble, or the device's proxy setting is wrong. On Windows, check Settings, Network & internet, Proxy, and make sure there's no proxy you don't recognize.
RESET means the connection was cut midway. In Indonesia, this error also commonly appears when a site is blocked by the ISP or a network filter. Read why sites get blocked and how it works. If it happens across many sites and apps, an antivirus or firewall on the device may be filtering too. See also certain apps or sites won't open.
How to fix certificate and SSL errors
Errors starting with NET::ERR_CERT mean Chrome isn't sure it's talking to the genuine site. The three most common causes:
- The device clock is wrong. This is the most frequent cause of NET::ERR_CERT_DATE_INVALID. See a wrong device clock breaks websites.
- The public Wi-Fi login page hasn't been completed. Café or hotel Wi-Fi intercepts connections until you log in. Open a plain non-HTTPS address or see the Wi-Fi login page won't appear.
- Someone is intercepting the connection. On unfamiliar Wi-Fi, never click "Proceed" on a banking or email site. Read fake Wi-Fi and evil twins.
ERR_NETWORK_CHANGED and ERR_TOO_MANY_REDIRECTS
ERR_NETWORK_CHANGED appears when the device switches networks mid-load, such as a phone moving from Wi-Fi to mobile data or a VPN reconnecting. If it happens often, read phone keeps switching to mobile data and Wi-Fi keeps dropping.
ERR_TOO_MANY_REDIRECTS is almost always about cookies. Clear cookies for that site only: click the icon left of the address, choose Site settings, then clear data. If it persists, the problem is in the site's configuration and only its owner can fix it.
When to contact your ISP
Contact your ISP if every device in the house shows the same error, restarting the router doesn't help, and mobile data works fine. Mention the error code and your ping results. Details like these get your report handled faster. If problems keep recurring, know your rights as a customer.
Frequently asked questions
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
It means the DNS server couldn't translate the site name into an IP address. Causes include a typo in the address, an expired domain, a stale DNS cache, or a faulty DNS server. Check the spelling, clear the DNS cache, then switch to a public DNS service.
How do I fix ERR_CONNECTION_TIMED_OUT?
This error means the server didn't answer in time. Check whether other sites load. If every site is slow, restart the router. If only one site fails, it's probably down or blocked on that network. Turn off any VPN or proxy, then try mobile data for comparison.
Why does a site load on mobile data but not on Wi-Fi?
Usually because of different DNS settings, blocking on that Wi-Fi network, or a router that needs restarting. Office, school, and public Wi-Fi often block certain categories of sites. Try changing the DNS on your device or ask the network administrator.
Are certificate errors on public Wi-Fi dangerous?
They can be. Errors like NET::ERR_CERT_AUTHORITY_INVALID on public Wi-Fi often appear because the Wi-Fi login page hasn't been completed, but they can also mean someone is intercepting the connection. Never click proceed on a banking or email site. Open the Wi-Fi login page first, and if the error persists, switch to mobile data.
