How to Fix ERR_CONNECTION_FAILED in Chrome

Chrome shows ERR_CONNECTION_FAILED (and in some versions the message “This site can’t be reached”) when it tried to connect to a website’s server and the connection could not be made at all. It differs from ERR_CONNECTION_RESET, where a connection started and was then cut, and from a timeout, where the server never answered. The cause is usually your internet connection, a firewall or VPN, a DNS problem, or the website itself.

Quick diagnosis: where is it failing?

• Every site fails on every device: the router, modem or internet provider. Start with steps 1 and 2.
• Every site fails only on your PC: a VPN, proxy, firewall or network setting on that computer. Go to steps 3 to 5.
• Only one site fails, on every device: the website is down or blocking you. Wait, or see step 9 if it is your own site.
• It fails in Chrome but works in Edge or Firefox: the problem is inside Chrome. Go to steps 6 to 8.

What causes ERR_CONNECTION_FAILED

• Your internet connection is down or unstable.
• A firewall or antivirus is blocking Chrome or the site.
• A VPN or proxy that is misconfigured or offline.
• A DNS problem, so the site address cannot be reached.
• A faulty Chrome extension or damaged browser data.
• The website or its server is down, or blocks your connection.

1. Check your connection and test other sites

Open two or three other websites. If none load, your connection is the problem, so continue with step 2. If only one site fails, try it on your phone using mobile data. If it fails there too, the site is down and you can only wait.

2. Restart the router and modem

Unplug the router and modem for about 30 seconds, plug them back in and wait a few minutes. If you use a cable, check that it is firmly plugged in, and try Wi-Fi instead, or the reverse. See our guide to can’t connect to this network on Windows 11 if Windows cannot join Wi-Fi at all.

3. Turn off VPN and proxy

Disconnect any VPN. In Windows open Settings > Network & internet > Proxy and turn off Use a proxy server unless you set one up on purpose. Try the page again.

4. Check your firewall and antivirus

Open your security software and check that Chrome is allowed to connect. You can pause web protection briefly to test, then turn it back on. In Windows Security, open Firewall & network protection > Allow an app through firewall and make sure Google Chrome is ticked for private and public networks.

5. Flush DNS and reset the network stack

Open Command Prompt or Terminal as administrator and run:

ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Restart the PC and try again. If the problem looks like a DNS lookup failure, our guide to ERR_NAME_NOT_RESOLVED covers changing DNS servers.

5a. Change your DNS servers and reset the Windows proxy

If flushing DNS did not help, switch to a public DNS service. In Windows 11, open Settings > Network & internet, choose Wi-Fi or Ethernet, open Hardware properties, and next to DNS server assignment choose Edit. Set it to Manual, turn on IPv4, and enter 1.1.1.1 and 1.0.0.1 (or 8.8.8.8 and 8.8.4.4). Save and reload the page.

Chrome on Windows can also be blocked by a leftover system proxy that the Settings page does not show. In an administrator Command Prompt run:

netsh winhttp show proxy
netsh winhttp reset proxy

The first command shows whether a proxy is set, and the second removes it. Restart Chrome afterwards.

6. Test without extensions

Open the page in an Incognito window, which disables most extensions. If it loads, an extension is the cause. Open chrome://extensions and turn extensions off one at a time, especially ad blockers, VPN and security extensions.

7. Clear browsing data

Press Ctrl + Shift + Delete, choose Cached images and files and cookies for a suitable time range, and clear them. You will be signed out of some sites.

8. Reset Chrome settings

Open Settings > Reset settings > Restore settings to their original defaults. This resets startup, search and extension settings but keeps bookmarks and saved passwords.

9. If it is your own website

If visitors see ERR_CONNECTION_FAILED on your site, check that the server is running, that port 443 for secure traffic is open, that your firewall or security plugin is not blocking visitors, and that your hosting plan has not been suspended. Test the site from another network and check your host’s status page.

ERR_CONNECTION_FAILED on Android or iPhone

On a phone the same causes apply, with fewer settings to check. Turn Airplane Mode on for 10 seconds, then switch between Wi-Fi and mobile data to see which one fails. Turn off any VPN app, restart the phone, and clear Chrome’s cached data from Chrome’s own settings. On Android, also check Private DNS in your network settings and set it to Automatic or Off while testing. Menu names vary by phone and version.

Frequently asked questions

What is the difference between ERR_CONNECTION_FAILED and ERR_CONNECTION_RESET?

Failed means the connection could not be made. Reset means it was made and then cut. Our guide to ERR_CONNECTION_RESET covers the second.

Why does it work on my phone but not my computer?

Your computer probably has a firewall, VPN, proxy or damaged setting in the way. Steps 3 to 6 target those.

Does ERR_CONNECTION_FAILED mean my IP address is blocked?

Sometimes. Some sites and firewalls block addresses they distrust, including many VPN servers. If the site fails on your home network but loads on mobile data, try again without the VPN, then contact the site owner if it still fails.

Can antivirus software cause ERR_CONNECTION_FAILED?

Yes. Web protection and firewalls can block Chrome, especially after an update. Pause the web protection briefly to test, and if that fixes it, add an exception for Chrome instead of leaving protection off.

Is the website down?

If it fails on every device and network, probably yes. If it works elsewhere, the problem is on your side.

When to contact support

If every site fails on every device, contact your internet provider. If only one site fails for everyone, contact its owner. If only your PC fails, contact your PC maker or IT team. A related error is ERR_NO_BUFFER_SPACE.