“This site can’t be reached” in Google Chrome means the browser could not establish a connection to the server hosting the website you requested. The fix depends on the specific error message shown below the main warning, but most cases are resolved by checking your internet connection, clearing the DNS cache, or disabling a conflicting browser extension.
What the Error Actually Means
Chrome displays “This site can’t be reached” when it cannot complete a network request to the website’s server. This is a generic wrapper message; the specific reason appears in smaller text beneath it. Common variations include:
- ERR_CONNECTION_TIMED_OUT – The server did not respond within a set period, often due to firewall blocks or server overload.
- ERR_CONNECTION_REFUSED – The server actively rejected the connection, frequently because the site is down or a local firewall is blocking the port.
- ERR_NAME_NOT_RESOLVED – Chrome could not translate the domain name into an IP address, pointing to a DNS problem.
- ERR_SSL_PROTOCOL_ERROR – The secure connection failed, often due to incorrect system date/time or corrupted SSL state.
- ERR_INTERNET_DISCONNECTED – Your device has no active internet connection.
Each of these has a slightly different cause, so reading the full error text is the first diagnostic step. The same website might work in another browser or on another device, which helps narrow down whether the problem is local to Chrome, your network, or the site itself.
Quick Checks Before Deep Troubleshooting
Before changing settings, run through these basic checks. They resolve a surprising number of cases:
- Open another website like example.com. If that also fails, the problem is your internet connection, not Chrome.
- Try the same URL in a different browser (Firefox, Edge, Safari). If it loads there, the issue is Chrome-specific.
- Restart your router and modem. Unplug them for 30 seconds, then plug back in and wait for lights to stabilize.
- Check if the site is down for everyone using a service like downforeveryoneorjustme.com. If the site itself is down, no local fix will help.
- Disable any VPN or proxy temporarily. Corporate or privacy VPNs can interfere with site connections.
If these steps do not resolve the issue, move on to the Chrome-specific fixes below.
Clear the DNS Cache and Flush the Resolver
A corrupted or outdated DNS cache is one of the most common causes of ERR_NAME_NOT_RESOLVED. Chrome has its own internal DNS cache, and your operating system has another. Clearing both is safe and takes less than a minute.
For Chrome’s internal cache, type chrome://net-internals/#dns in the address bar and click the “Clear host cache” button. Then close and reopen Chrome.
To flush the operating system’s DNS cache:
- Windows: Open Command Prompt as Administrator and run
ipconfig /flushdns. - macOS: Open Terminal and run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. - Linux: Run
sudo systemd-resolve --flush-caches(orsudo resolvectl flush-cacheson newer systems).
After flushing, restart Chrome and try the site again. If the problem persists, you can also change your DNS server to a public one like Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1) to rule out your ISP’s DNS being the bottleneck.
Disable Extensions and Hardware Acceleration
Extensions that modify network requests—ad blockers, privacy tools, VPN extensions, or security suites—can block connections to specific sites. Chrome extensions run with significant permissions, and a misbehaving one can cause ERR_CONNECTION_REFUSED or ERR_BLOCKED_BY_CLIENT.
To test this, open Chrome in Incognito mode (Ctrl+Shift+N or Cmd+Shift+N). Extensions are disabled by default in Incognito unless you explicitly enabled them there. If the site loads in Incognito, an extension is the culprit. Disable extensions one by one via chrome://extensions to find the offender.
Hardware acceleration can also cause connection issues on some systems, particularly with older graphics drivers. Go to Settings → System and toggle off “Use hardware acceleration when available.” Restart Chrome and test. This is a less common fix, but it has resolved intermittent connection failures for some users.
Reset Chrome’s Network Settings and Socket Pools
If the error persists, Chrome’s internal network state may be corrupted. The chrome://net-internals page offers deeper controls:
- Go to chrome://net-internals/#sockets and click “Flush socket pools.” This closes all idle network connections that may be stuck.
- Go to chrome://net-internals/#dns and clear the host cache again.
- Close Chrome completely and reopen it.
If that does not help, you can reset Chrome to its default state. This removes extensions, clears temporary data, and restores default settings, but it does not delete your bookmarks, history, or saved passwords. Go to Settings → Reset settings → Restore settings to their original defaults. This is a more drastic step, so use it as a last resort before reinstalling.
Check System Date, Time, and Firewall Rules
An incorrect system clock is a frequent cause of ERR_SSL_PROTOCOL_ERROR. SSL certificates have validity periods, and if your computer’s date or time is off by more than a few minutes, Chrome rejects the certificate as expired or not yet valid. Check your system date and time settings and enable automatic time synchronization.
Firewalls and antivirus software can also block Chrome’s connections. Windows Defender Firewall occasionally flags Chrome after an update. To check, temporarily disable your firewall (not recommended for long) and try the site. If it loads, add Chrome as an allowed app in the firewall settings. On Windows, go to Control Panel → Windows Defender Firewall → Allow an app through the firewall and ensure Chrome is checked for both private and public networks.
On macOS, check System Settings → Network → Firewall and ensure Chrome is not blocked. Third-party antivirus suites often have their own web protection that can interfere; check their settings for a whitelist or temporarily disable the web shield to test.
Frequently Asked Questions
Why does the site work on my phone but not my computer?
This points to a device-specific issue rather than a site outage. The most likely causes are a corrupted DNS cache on the computer, a firewall rule blocking Chrome, or a Chrome extension interfering. Try the DNS flush and extension disabling steps above. If the computer uses a different network (e.g., Ethernet vs. Wi-Fi), check that connection’s settings too.
Can a VPN cause “This site can’t be reached”?
Yes. VPNs route your traffic through remote servers, and if that server is blocked by the website or has connectivity problems, you will see this error. Disconnect the VPN and try the site directly. If it loads, the VPN server is the problem—try a different server location or contact your VPN provider.
What does ERR_CONNECTION_RESET mean?
ERR_CONNECTION_RESET means the server closed the connection before completing the response. This often happens when a firewall (local or network-level) interrupts the connection, or when the server is overloaded. Try a different browser to confirm it is not Chrome-specific, then check your firewall and antivirus settings.
Will clearing my browsing data fix this error?
Sometimes. Corrupted cookies or cached files for a specific site can cause connection issues. Go to Settings → Privacy and security → Clear browsing data, choose “All time,” and check cookies and cached images. This is a low-risk step, but you will need to log into sites again.
Is it safe to use public DNS servers like 8.8.8.8?
Yes. Google Public DNS and Cloudflare DNS are widely used, reliable services. They can improve speed and sometimes resolve sites that your ISP’s DNS fails to find. Changing DNS is reversible and does not affect your browsing security, though your DNS queries will be visible to the DNS provider rather than your ISP.
Should I reinstall Chrome if nothing else works?
Reinstalling is a reasonable final step. Uninstall Chrome (your bookmarks and passwords are usually synced to your Google account, but verify this first), then download the latest version from the official Google Chrome website and install it. This replaces all program files and clears any corrupted installation data. Before reinstalling, try the reset option in settings, which achieves a similar effect without reinstalling.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- MacBook Charger Not Working? Fix It Now
- Fix Windows Cannot Be Installed to This Disk
- Zoom on iPhone & iPad: Host or Join a Meeting
- Fix iPhone SE 4 Unable to Activate: Step-by-Step
- Keep Important Emails From Getting Buried in iPhone Mail Categories
- How to Clear RAM on iPhone: Speed It Up