Chrome Error Code Fix: Step-by-Step Guide

Chrome error codes can stop you from loading websites, syncing data, or even opening the browser. This guide walks you through the most common Chrome error codes—like ERR_CONNECTION_TIMED_OUT, ERR_NAME_NOT_RESOLVED, and STATUS_BREAK—and shows you how to fix them step by step. You’ll need a few minutes and, in some cases, access to your router or network settings.

What You’ll Need

A computer running Chrome (Windows, macOS, or Linux)
Administrator or owner access to your device (for some fixes)
Access to your router’s admin page (if you need to reset network settings)
A stable internet connection (for downloading updates or resetting)

Step-by-Step

Identify the exact error code. The error message usually appears on a full-page “Aw, Snap!” or “This site can’t be reached” screen. Write down the code (e.g., ERR_CONNECTION_REFUSED, ERR_CERT_COMMON_NAME_INVALID). This determines which fix applies.
Restart Chrome completely. Close all Chrome windows and tabs. On Windows, check the system tray for Chrome icons and close them too. Then reopen Chrome. This clears temporary glitches that cause some error codes.
Check your internet connection. Open another website (like google.com) in a different browser or on another device. If no site loads, the issue is your network, not Chrome. Restart your modem and router by unplugging them for 30 seconds, then plugging them back in. Wait for lights to stabilize.
Clear Chrome’s cache and cookies. Go to Chrome’s menu (three dots) → More tools → Clear browsing data. Choose “All time” as the time range, check “Cached images and files” and “Cookies and other site data,” then click “Clear data.” This resolves errors like ERR_CACHE_MISS or ERR_CACHE_READ_FAILURE.
Disable problematic extensions. Type chrome://extensions in the address bar and press Enter. Toggle off all extensions, then try loading the page again. If it works, enable extensions one by one to find the culprit. Remove any that cause errors.
Flush DNS and reset network settings. This fixes ERR_NAME_NOT_RESOLVED and ERR_CONNECTION_TIMED_OUT. On Windows, open Command Prompt as administrator and run: ipconfig /flushdns, then ipconfig /release, then ipconfig /renew. On macOS, open Terminal and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
Change your DNS server. If DNS errors persist, switch to a public DNS like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1). In Windows, go to Network Settings → Change adapter options → right-click your connection → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → Use the following DNS server addresses. Enter the addresses and click OK.
Check proxy settings. Go to Chrome’s settings → System → “Open your computer’s proxy settings.” Ensure “Use a proxy server” is off (unless you actually use one). On Windows, also check “Automatically detect settings” is on.
Update Chrome. Go to chrome://settings/help. Chrome will check for updates and install them automatically. Restart Chrome after updating.
Reset Chrome settings (if needed). If nothing works, go to chrome://settings/reset and click “Restore settings to their original defaults.” This disables extensions, clears temporary data, and resets shortcuts—but keeps your bookmarks and passwords.
Run a malware scan. Some error codes (like ERR_BLOCKED_BY_CLIENT) are caused by malicious software. Use Windows Defender or a trusted antivirus to scan your system. On macOS, check for adware in System Settings → Privacy & Security.
Check the site itself. If you get ERR_CONNECTION_REFUSED or ERR_SSL_PROTOCOL_ERROR on a specific site, the website may be down or blocking your IP. Try loading it on another device or use a site like downforeveryoneorjustme.com (but note: that site is a third-party service).

Common Mistakes

Not clearing all time ranges. Clearing only the last hour won’t fix corrupted cache from weeks ago. Always choose “All time.”
Skipping the router restart. Many connection errors are fixed by a simple router reboot, but people often skip it and try complex fixes.
Disabling all extensions permanently. If you find an extension is the issue, remove it rather than leaving it disabled—it may update and cause problems again.
Changing DNS settings incorrectly. Typing a wrong DNS address (like 8.8.8.8 instead of 8.8.8.8) will break all internet access. Double-check each number.
Ignoring the exact error code. Some fixes only work for specific codes. For example, clearing cache won’t fix ERR_SSL_PROTOCOL_ERROR if the server is misconfigured.

Tips

Use Chrome’s “Incognito mode” to test if an error is caused by extensions or cookies. If the page loads in incognito, the problem is likely related to your browsing data.
Keep Chrome updated automatically—outdated versions have known bugs that cause error codes.
If you use a VPN, try disconnecting it. Many VPNs interfere with Chrome’s connections, causing ERR_CONNECTION_RESET or ERR_PROXY_CONNECTION_FAILED.
For ERR_CERT errors, check your computer’s date and time. An incorrect clock can make SSL certificates appear invalid.
Use the “Network” tab in Chrome’s Developer Tools (F12) to see the exact request that fails. This helps diagnose complex errors.

Troubleshooting

If the steps above don’t fix your error:

Try a different browser. If the site loads in Firefox or Edge, the problem is Chrome-specific. Reinstall Chrome (back up your profile first).
Check for system-level firewall blocks. Temporarily disable your firewall (Windows Defender Firewall or third-party) and test. If the site loads, add Chrome to the allowed apps list.
Use Chrome’s built-in diagnostic tool. Go to chrome://net-internals/#dns and click “Clear host cache.” Then go to chrome://net-internals/#sockets and click “Flush socket pools.”
Check if the error is on a specific network. If you’re on a work or school network, the network may block certain sites. Try using a mobile hotspot to test.
If all else fails, reset your network stack. On Windows, run netsh winsock reset and netsh int ip reset in Command Prompt as administrator, then restart your computer. On macOS, go to System Settings → Network → select your connection → Details → TCP/IP → “Renew DHCP Lease.”

Frequently Asked Questions

Q: What does ERR_CONNECTION_TIMED_OUT mean?
A: Chrome could not reach the website’s server within the time limit. Usually caused by network congestion, firewall blocks, or server issues.

Q: How do I fix ERR_SSL_PROTOCOL_ERROR?
A: Clear your SSL state (Windows: Internet Options → Content → Clear SSL state), check your date/time, disable extensions, and try a different DNS server.

Q: Why do I get ERR_NAME_NOT_RESOLVED?
A: This means Chrome couldn’t translate the domain name into an IP address. Flush DNS, change DNS servers, or check your internet connection.

Q: Can an antivirus cause Chrome errors?
A: Yes, some antivirus software intercepts HTTPS traffic and can cause ERR_SSL_PROTOCOL_ERROR or ERR_CONNECTION_RESET. Try disabling the antivirus temporarily or adding Chrome to its exceptions.

Q: What is ERR_BLOCKED_BY_CLIENT?
A: This error appears when an extension or Chrome’s built-in ad blocker prevents a resource from loading. Disable extensions or allow the site in your ad blocker.

Q: Will resetting Chrome delete my bookmarks?
A: No, resetting Chrome only disables extensions, clears temporary data, and resets settings. Your bookmarks, history, and passwords are kept.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →