“This site can’t be reached” is a generic Chrome error that appears when the browser cannot establish any connection to the web server. Unlike specific error codes like ERR_CONNECTION_REFUSED or ERR_NAME_NOT_RESOLVED, this message is a catch-all that can have multiple underlying causes, from DNS failures to firewall blocks.
This error affects Chrome specifically, though the same underlying problem will show different messages in Firefox (“Unable to connect”) and Edge (“Hmmm… can’t reach this page”). The root cause is always the same: your browser’s connection request never reaches the destination server. Here are all the proven fixes in order of effectiveness.
Fix 1: Flush Your DNS Cache
Stale or corrupted DNS cache entries are the #1 cause of “This site can’t be reached.” Your system caches DNS lookups to speed up repeat visits, but when a site changes its IP address or your cache becomes corrupted, connections fail. Open Command Prompt as Administrator on Windows and run “ipconfig /flushdns.” On macOS, open Terminal and run “sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.” Also clear Chrome’s internal DNS cache: navigate to chrome://net-internals/#dns and click “Clear host cache.”
Fix 2: Change DNS Servers
Your ISP’s default DNS servers may be slow, unreliable, or blocking certain domains. Switch to Google Public DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1 and 1.0.0.1) for faster, more reliable name resolution. On Windows 10/11, go to Settings, Network & Internet, Change adapter options, right-click your active connection, select Properties, double-click Internet Protocol Version 4, and enter the DNS addresses. Restart your browser after changing DNS settings.
Fix 3: Reset TCP/IP and Winsock
Corrupted network stack settings can prevent all browser connections. Open Command Prompt as Administrator and run these commands in order: “netsh winsock reset” then “netsh int ip reset” then “ipconfig /release” then “ipconfig /renew.” Restart your computer after running all commands. This resets your network configuration to defaults, fixing issues caused by malware, VPN remnants, or corrupted network drivers.
Fix 4: Disable Proxy Settings
Misconfigured proxy settings route your traffic through a non-existent proxy server, preventing all web access. In Chrome, go to Settings, System, Open your computer’s proxy settings. On Windows, make sure “Automatically detect settings” is ON and “Use a proxy server” is OFF (unless you intentionally use a proxy). On macOS, go to System Settings, Network, your active connection, Proxies, and uncheck all proxy protocols unless you need them.
Fix 5: Disable Firewall and Antivirus Temporarily
Windows Firewall or third-party security software may block Chrome’s network access. Temporarily disable your firewall: go to Windows Security, Firewall & network protection, and turn off the firewall for your active network profile. If the site loads, add Chrome to your firewall’s allowed applications list and re-enable the firewall. For antivirus programs, check if they have web filtering or HTTPS inspection features and try disabling those specifically rather than the entire antivirus.
Fix 6: Reset Chrome Flags
Experimental Chrome flags can break network connections. Type “chrome://flags” in the address bar and click “Reset all to default” at the top of the page. Restart Chrome. Specific flags that commonly cause connection issues include Experimental QUIC protocol, Async DNS resolver, and various network-related experiments. After resetting, Chrome uses its default stable network configuration.
Fix 7: Check Your Hosts File
The hosts file can redirect domain names to wrong IP addresses, causing connection failures. On Windows, open Notepad as Administrator and open the file at C:\Windows\System32\drivers\etc\hosts. On macOS, open Terminal and run “sudo nano /etc/hosts.” Look for any entries pointing the problematic domain to 127.0.0.1 or 0.0.0.0 and remove them. Malware and parental control software sometimes modify the hosts file to block websites.
Fix 8: Reinstall Network Adapter Driver
A corrupted network adapter driver can cause intermittent connection failures. Open Device Manager (right-click Start, Device Manager), expand Network adapters, right-click your active adapter (WiFi or Ethernet), and select “Uninstall device.” Check the box to delete the driver software if prompted. Restart your computer, and Windows will automatically reinstall the correct driver. If you use WiFi, download the latest driver from your laptop manufacturer’s website before uninstalling, in case automatic reinstallation fails.
Frequently Asked Questions
Why does “This site can’t be reached” only affect certain websites?
When only specific sites are unreachable, the cause is usually DNS-related or involves targeted blocking. Your DNS cache may have a corrupt entry for that domain, your ISP may block it, or the site’s DNS servers may be down. Switching to Google DNS (8.8.8.8) and flushing your cache resolves most single-site connection failures.
Why does this error appear on WiFi but not mobile data?
This indicates a problem with your WiFi network’s DNS configuration, router settings, or ISP. Your WiFi and mobile data use different DNS servers and network paths. Try restarting your router, changing your WiFi connection’s DNS to Google or Cloudflare, or resetting your router to factory defaults if the problem persists across all devices on that network.
Can browser extensions cause “This site can’t be reached”?
Yes. VPN extensions, ad blockers, and privacy tools can intercept network requests and cause connection failures. Test in Chrome Incognito mode (Ctrl+Shift+N), which disables all extensions by default. If the site loads in Incognito, disable extensions one by one in normal mode to identify the culprit.
