Google Chrome ERR_CONNECTION_FAILED: How to Fix It
Easy 10-30 minutes Medium Severity
Verified June 2026
- Error Code
- ERR_CONNECTION_FAILED
- Brand
- Google Chrome
- Product Type
- browser
- Severity
- Medium
- DIY Difficulty
- Easy
- Estimated Fix Time
- 10-30 minutes
Ad
Tools You'll Need
- Google Chrome browser
- Access to Windows Command Prompt or Mac Terminal
- Administrator or user account password for your computer
- Access to your router (for restarting)
How to Fix Error Code ERR_CONNECTION_FAILED
-
Check Your Internet Connection
-
Disable VPN or Proxy Settings
-
Flush DNS Cache and Renew IP Address
-
Change Your DNS Server
-
Disable Chrome Extensions
-
Clear Chrome's Browsing Data and Cache
-
Check Windows Firewall and Antivirus Settings
Only temporarily disable your antivirus for testing purposes. Re-enable it immediately after testing. -
Reset Chrome Network Settings via Flags
-
Update or Reinstall Google Chrome
Before uninstalling, sign in to your Google account in Chrome so your bookmarks and passwords are synced and will not be lost. -
Reset TCP/IP Stack on Windows
This step modifies core network settings. It is safe but requires a system restart to take effect.
Ad
When to Call a Professional
Contact your Internet Service Provider (ISP) if the error persists across all browsers and all devices on your network after restarting your modem and router — this points to an ISP-side outage or account issue. Seek IT support if the error only happens on a work or school computer where you do not have administrator access to change firewall or DNS settings. If your computer has malware that is redirecting or blocking connections, run a full malware scan with a tool like Malwarebytes, or consult a professional PC repair technician.Frequently Asked Questions
What causes ERR_CONNECTION_FAILED in Chrome?
ERR_CONNECTION_FAILED is most commonly caused by a misconfigured proxy or VPN, a firewall or antivirus program blocking Chrome, corrupted DNS cache, stale Chrome socket connections, or a faulty browser extension. Less commonly, it can be caused by a corrupted Chrome installation or an issue with your ISP's network.
Does ERR_CONNECTION_FAILED mean the website is down?
Not necessarily. ERR_CONNECTION_FAILED means Chrome could not establish a connection at all, which almost always points to a local issue on your device or network rather than the website being down. If the website were down, you would typically see a different error like ERR_NAME_NOT_RESOLVED or a server error page. Test the same website on a different device or network to confirm whether the site itself is the problem.
Why does ERR_CONNECTION_FAILED only happen on one website?
If the error only affects one specific website, that site may be blocking your IP address, or your local DNS is failing to resolve that particular domain. Try clearing your DNS cache (ipconfig /flushdns on Windows), switching to a public DNS like Google's 8.8.8.8, or using a VPN to change your apparent location. It is also possible that particular website is down or blocking traffic from your region.
How do I fix ERR_CONNECTION_FAILED on Android or iPhone Chrome?
On mobile, start by toggling Airplane Mode on and off to reset the network connection. Make sure you are not connected to a VPN. Go to Chrome Settings > Privacy > Clear Browsing Data and clear the cache. If on Wi-Fi, try switching to mobile data to see if the problem is network-specific. Restart the Chrome app completely, and if the problem persists, uninstall and reinstall Chrome from the App Store or Google Play Store.
Will resetting Chrome fix ERR_CONNECTION_FAILED?
Resetting Chrome can fix the error if it is caused by corrupted settings, a bad extension, or misconfigured proxy settings within Chrome. To reset, go to chrome://settings/reset and click 'Restore settings to their original defaults'. Note that this will disable your extensions and clear your startup pages and search engine settings, but it will not delete your bookmarks or passwords. If the error is caused by a network or firewall issue outside of Chrome, a reset alone will not fix it.