Tech Troubleshooting

How to Fix Common Chrome Errors

Rejaul Karim10 min read

Google Chrome is the most widely used web browser in the world, yet nearly everyone has run into a cryptic error page at some point: "This site can't be reached", "Your connection is not private", "Aw, Snap!" or a string of capital letters starting with ERR_. The messages look intimidating, but most have simple causes and quick fixes. This guide explains what the most common Chrome errors mean and how to fix them, starting with the universal steps that solve a surprising number of problems.

Universal fixes to try first

Before hunting for a specific error, try these quick steps. Together they resolve most browser problems.

  1. Reload the page. Press F5 or Ctrl + Shift + R (a hard reload that bypasses cached files).

  2. Check another site and another device. If every site fails everywhere, the problem is your internet connection or router. If only one site fails, the problem may be the site itself.

  3. Restart Chrome and your computer. This clears temporary glitches and stuck processes.

  4. Update Chrome. Open chrome://settings/help, let Chrome check for updates and click Relaunch if prompted.

  5. Try an Incognito window (Ctrl + Shift + N). Incognito disables most extensions by default, so if the page works there, an extension or cached data is the culprit.

  6. Clear cached files. Press Ctrl + Shift + Delete, choose a time range, tick Cached images and files and, if needed, Cookies and other site data, then clear. Remember that clearing cookies signs you out of websites.

1. "This site can't be reached" and ERR_CONNECTION_TIMED_OUT

What it means: Chrome could not get a response from the website's server in time.

How to fix it:

  • Check your internet connection by opening a different website.

  • Restart your router and modem. Wait 30 seconds before turning them on again.

  • Temporarily turn off your VPN, proxy or firewall, which may be blocking the connection.

  • Check whether the site is down for everyone using a status checker, because the fault may be on their end.

  • Flush the DNS cache (see the DNS section below).

2. ERR_INTERNET_DISCONNECTED and DNS_PROBE_FINISHED_NO_INTERNET

What it means: Chrome thinks your device has no working internet connection, or it cannot reach a DNS server to look up the address.

How to fix it:

  • Make sure Wi-Fi is on, airplane mode is off and that you are connected to the right network.

  • Restart the router, and try another device on the same network.

  • Run the Windows network troubleshooter from Settings > System > Troubleshoot > Other troubleshooters.

  • Change your DNS servers to a public service such as Cloudflare (1.1.1.1) or Google (8.8.8.8).

3. ERR_NAME_NOT_RESOLVED and DNS_PROBE_FINISHED_NXDOMAIN

What it means: Chrome could not translate the website name into an IP address. Either the address is mistyped, the domain does not exist or your DNS is failing.

How to fix it:

  • Check the spelling of the web address.

  • Flush the DNS cache. On Windows, open Command Prompt as administrator and run ipconfig /flushdns. On macOS, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal.

  • Switch to a public DNS server as described above.

  • Restart your router.

4. "Your connection is not private" (NET::ERR_CERT_DATE_INVALID, ERR_CERT_AUTHORITY_INVALID)

What it means: Chrome could not verify that the site's security certificate is valid, so it warns you before connecting. This protects you from fake or insecure sites.

The most common local cause is your computer's clock. If the date or time is wrong, certificates look expired or not yet valid. Correct the date, time and time zone in your system settings and turn on automatic time setting.

Other fixes:

  • Try a different network. Public Wi-Fi networks and some security software can interfere with certificates.

  • Check whether antivirus software that scans HTTPS traffic is causing the problem, and update or adjust it.

  • Clear the browser cache and update Chrome.

A warning: if the error appears on a banking, shopping or login site and your clock is correct, do not click through the warning. It may mean that the site is misconfigured or that someone is intercepting the connection. Only proceed on sites you fully trust, such as your own test server, and never enter passwords or payment details on a page with a certificate error.

5. ERR_SSL_PROTOCOL_ERROR and ERR_SSL_VERSION_OR_CIPHER_MISMATCH

What it means: Chrome and the website could not agree on a secure way to communicate.

How to fix it:

  • Correct the date and time on your device.

  • Clear the browser cache, and in Windows clear the SSL state from Internet Options > Content > Clear SSL state.

  • Update Chrome and your operating system.

  • If you own the website, check that your server supports modern TLS versions and has a valid certificate.

  • If the error is ERR_QUIC_PROTOCOL_ERROR, try disabling the experimental QUIC protocol in chrome://flags, or check for interference from a firewall or VPN.

6. ERR_CONNECTION_RESET and ERR_CONNECTION_REFUSED

What it means: The connection to the server was interrupted or the server actively refused it. This is often caused by firewalls, antivirus software, proxy settings, unstable Wi-Fi or a server problem.

How to fix it:

  • Turn off any VPN or proxy, and check the proxy settings under Settings > Network & internet > Proxy in Windows.

  • Temporarily disable your firewall or antivirus to test, and then turn it back on and add an exception if that was the cause.

  • Try a different network such as your phone's hotspot.

  • Reset your network settings if the problem affects many sites.

7. ERR_TOO_MANY_REDIRECTS ("redirected you too many times")

What it means: The site keeps sending your browser in a loop between addresses. The usual cause is a stale or corrupt cookie.

How to fix it: Clear cookies and cached data for that specific site: click the icon to the left of the address bar, choose Cookies and site data > Manage on-device site data, and delete the entries for that site. Reload the page. If you run the website, check redirect rules, HTTPS settings and the interaction between your CDN and server, because a mismatch there commonly creates loops.

8. "Aw, Snap!" and page crashes

What it means: A tab crashed, often because of low memory, a faulty extension, a corrupted profile or a problem with the page itself.

How to fix it:

  • Close other tabs and applications to free memory. Use Chrome's built-in task manager (Shift + Esc) to see which tab or extension uses the most.

  • Disable extensions at chrome://extensions, then re-enable them one at a time to find the faulty one.

  • Check for malware with Windows Security or your antivirus.

  • Switch off hardware acceleration at Settings > System if the problem appears with video or graphics-heavy pages, then relaunch Chrome.

  • Update your graphics driver.

  • Create a new Chrome profile to test whether the current profile is corrupted.

9. ERR_BLOCKED_BY_CLIENT

What it means: Something on your side, usually an ad blocker or privacy extension, blocked a request on the page. It is often visible in the developer console when a page or a form does not work as expected.

How to fix it: Pause the ad blocker for that site, or add the site to its allow list. If a form or checkout fails, test in Incognito mode without extensions.

10. ERR_CACHE_MISS and "Confirm Form Resubmission"

What it means: You reloaded a page that had submitted data, and Chrome wants to confirm before sending the form again.

How to fix it: Do not resubmit a payment or order form, which could create a duplicate transaction. Instead, navigate back to the page or check your order confirmation email first. If the error occurs repeatedly, clear cached data and update Chrome. Developers should note that it can also appear when caching headers are misconfigured.

11. Chrome is slow, freezing or using too much memory

  • Open Shift + Esc to find memory hogs.

  • Turn on Memory Saver in Settings > Performance, which puts inactive tabs to sleep.

  • Remove extensions you do not need.

  • Restart the browser regularly if you keep many tabs open for days.

  • Free up disk space and make sure your computer meets the demands of what you are doing.

12. Chrome will not open or keeps crashing on launch

  1. End any stuck Chrome processes in Task Manager, then try again.

  2. Restart the computer and update Chrome.

  3. Reset Chrome's settings at Settings > Reset settings > Restore settings to their original defaults. This disables extensions and resets startup pages and search engine but keeps bookmarks and saved passwords.

  4. If it still fails, back up your bookmarks, uninstall Chrome and reinstall the latest version from google.com/chrome.

Quick error cheat sheet

  • ERR_INTERNET_DISCONNECTED: check Wi-Fi and router.

  • DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED: check the address, flush DNS, change DNS servers.

  • ERR_CONNECTION_TIMED_OUT: check network, VPN, firewall and whether the site is down.

  • NET::ERR_CERT_DATE_INVALID: fix your computer's date and time.

  • ERR_SSL_PROTOCOL_ERROR: update, clear SSL state, check the clock.

  • ERR_TOO_MANY_REDIRECTS: clear the site's cookies.

  • ERR_BLOCKED_BY_CLIENT: pause the ad blocker for the site.

  • Aw, Snap!: close tabs, disable extensions, update drivers.

A note about website error codes

Numbers such as 403 (forbidden), 404 (not found), 500 (server error), 502 (bad gateway), 503 (service unavailable) and 504 (gateway timeout) come from the website's server, not from Chrome. For 404, check the address. For 5xx errors, the problem is on the site's end, so wait a few minutes and try again, or contact the site owner.

Final thoughts

When Chrome shows an error, start with the simple steps: reload, test another site, restart, update and try Incognito mode. Then read the error code, which often names the cause directly. Keep Chrome updated, avoid installing unnecessary extensions and make sure your computer's clock is right. For certificate warnings, take them seriously and never enter sensitive information on a page that Chrome flags as unsafe.

  • browser
  • chrome errors
  • google chrome
  • troubleshooting

Comments

Leave a comment

← All posts