Chrome “This Site Can’t Be Reached” Error: Fixes

Chrome’s “This site can’t be reached” message usually means the browser could not connect to the website, but the cause may be your connection, device, DNS settings, or the site itself. Check whether other websites load, then work through the steps below—from simple connection checks to troubleshooting Chrome and your network.

1. Check the website and your connection

First, determine whether the problem affects one site or everything. Open a few familiar websites in Chrome. If none load, check your device’s Wi-Fi or Ethernet connection and see whether other devices on the same network can browse. If only one website fails, the site may be unavailable, its address may be wrong, or access may be blocked on that network.

• Check the address bar for spelling errors, missing characters, or an unintended space. If you followed a link, try entering the site’s main address yourself.
• Try another browser or another device. If the site fails everywhere, a problem with the site or network is more likely than a Chrome-specific fault.
• On Wi-Fi, confirm that your device is connected to the intended network. A connection icon does not always mean the internet is working.
• If you use a public Wi-Fi network, open a new tab and check whether it requires a sign-in or terms acceptance.

If the site is down for everyone, there may be nothing to fix on your device. Try again later or contact the site owner if you need access.

2. Restart Chrome and your device

Close Chrome completely and reopen it, then try the page again. If that does not help, restart your computer or phone. Restarting can clear a temporary software or network issue without changing saved settings.

Also restart your router or modem if other devices on your network cannot reach websites. Unplugging network equipment briefly and reconnecting it may restore a connection, but allow it time to restart. Avoid resetting the device to factory settings: that can erase its configuration and is rarely an appropriate first step.

3. Test extensions, private browsing, and stored data

Chrome extensions can interfere with requests, and damaged or outdated site data can cause a page to fail. To test for an extension problem, open an Incognito window using Chrome’s menu or the keyboard shortcut Ctrl+Shift+N on Windows and Linux, or Command+Shift+N on Mac. Incognito mode does not automatically sign you into sites, and extensions are generally not available there unless you have allowed them.

If the site works in Incognito, return to a regular window and temporarily turn off extensions at Chrome menu > Extensions > Manage Extensions. Disable them one at a time and reload the site to identify a possible cause. Turn off only extensions you recognize; if one is managed by an organization, ask its administrator before changing it.

You can also remove data for the affected website without clearing everything. Open the site’s information or settings from the address bar, then look for its site-data or cookie settings. The exact labels can vary by Chrome version. Removing cookies may sign you out or reset preferences, so do this only if you are comfortable signing in again. Clearing all browsing data is not usually the first thing to try.

4. Check VPN, proxy, and security software

A VPN, proxy, firewall, or security application can prevent a connection or route it through a server that cannot reach the site. If you use a VPN, disconnect briefly to test the page, then reconnect afterward. If you are on a work or school network, a proxy or filtering policy may be required; do not bypass it. Contact the organization’s IT support if the problem appears limited to that network.

On a personal device, check whether security software has recently changed or reported a blocked connection. Do not turn off protection permanently or install software from an unfamiliar source to “repair” Chrome. If you test with a protection feature temporarily paused, restore it immediately and use the software’s own help instructions. Some websites are intentionally blocked by network administrators or regional settings; Chrome cannot override those restrictions.

5. Flush DNS and review network settings

DNS translates a website name, such as example.com, into the address computers use to connect. If Chrome cannot resolve the name, an error may mention DNS or show that the site’s address could not be found. A temporary DNS problem may clear after restarting your device or router. On a computer, you can also flush the operating system’s DNS cache using its built-in tools, but the command differs between Windows, macOS, and Linux.

Chrome’s Secure DNS setting can also affect name lookups. In Chrome, open Settings > Privacy and security > Security and find Use secure DNS. If you suspect a conflict, note the current setting and test the other available option, if permitted by your network. Restore the original choice if this does not help. On managed devices, the setting may be controlled by an administrator.

Do not change DNS server addresses at random. A mistaken setting can disrupt browsing, and network policies may require particular servers. If other devices on the same network have the same DNS problem, contact your internet provider or network administrator.

6. Update Chrome and check the error details

Install Chrome updates from Chrome menu > Help > About Google Chrome, then relaunch the browser if prompted. Updates can address browser problems, though they will not bring an offline website back online. If Chrome will not open the update page, use your device’s normal software-update or installation process rather than downloading an installer from an unknown site.

Read the smaller message beneath “This site can’t be reached.” Wording such as “DNS address could not be found,” “connection timed out,” or “connection was reset” points toward different causes. It is a clue, not a definitive diagnosis: DNS issues may come from the device, router, provider, or website, while a timeout can also result from a server outage or filtering.

If the problem persists, note the exact website, error wording, whether other sites work, and whether another device on the same network can connect. That information helps an internet provider, site owner, or IT administrator narrow down the cause. Avoid repeatedly changing several settings at once, because it makes it harder to tell which change mattered.

Frequently Asked Questions

Why does Chrome say “This site can’t be reached” when my internet works?
A single site can fail even when other pages load. The site may be down, its DNS lookup may be failing, or a VPN, extension, firewall, or network policy may be interfering.

How do I know whether the website is down or Chrome is the problem?
Try the address in another browser and on another device or network. If it fails across devices and networks, the site is more likely to be unavailable. If it fails only in Chrome on one device, focus on Chrome settings, extensions, and local network configuration.

Will clearing Chrome’s cache fix the error?
Sometimes, but it is not a universal fix. Try an Incognito window first. If the site works there, test extensions and consider removing data for that site; remember that deleting cookies can sign you out.

Should I change my DNS settings?
Not as a first step. Restart the device and router, check whether other devices are affected, and consult your network administrator or provider if the issue continues. Change DNS only when you understand the setting and are allowed to do so.

Why does the site work on mobile data but not Wi-Fi?
That points toward the Wi-Fi network, router, internet provider, or its DNS or filtering settings. Restart the router if appropriate; for a managed network, ask its administrator rather than trying to bypass restrictions.

Can I fix the error if the website’s server is down?
No local Chrome setting can restore a server that is unavailable. Check again later or contact the website owner if the outage continues.

Related

• Build and Test React Apps with Nx and Cypress
• Keyboard Automatically Typing on Windows: How to Fix It
• Check AI-Generated Spreadsheets Before You Trust Them