How to Fix Chrome ERR_CONNECTION_TIMED_OUT

ERR_CONNECTION_TIMED_OUT means Chrome tried to connect to the site’s server and gave up waiting. Chrome’s error page says “This site can’t be reached” and “site took too long to respond.” Google’s Chrome error messages page says the page took too long to connect: your internet connection might be too slow, or the page might be too busy.

Whose problem is it? Usually the site or the network, not Chrome. One quick test tells you which:

  • Only one site times out: that site is probably down or overloaded. Wait and try again later, or check it on another device or on mobile data.
  • Every site times out: the problem is your connection, or something on your computer that sits between Chrome and the internet, such as a proxy or firewall. Work through the steps below.

Step 1: Check your connection and restart the router

  1. Make sure your device is connected on Wi-Fi or Ethernet. Google’s connection and loading errors help says you may need to reboot your modem and router, or contact your internet provider.
  2. To restart them, unplug the router and the modem, wait at least 30 seconds, plug the modem back in and wait for its lights to settle, then plug in the router (Microsoft’s steps).
  3. On public Wi-Fi, such as in a cafe, you may need to sign in through the network’s portal page before anything loads.

Step 2: Check for a proxy

Chrome’s error page suggests “Checking the proxy and the firewall”. Start with the proxy.

  1. Open chrome://settings/system and select Open your computer’s proxy settings. If the page says Chrome is using proxy settings from an extension or from your administrator, the setting is controlled there.
  2. Windows: this opens Settings > Network & internet > Proxy. Under Manual proxy setup, make sure Use a proxy server is off unless you need one (Microsoft’s proxy help).
  3. Mac: choose Apple menu > System Settings, click Network, click your network service, click Details, then click Proxies and turn off any proxy you did not set up on purpose (Apple’s steps).

Our proxy errors guide covers Linux and the proxy error codes.

Step 3: Check the firewall and antivirus

Google’s help says to make sure firewall or antivirus software is not blocking your connection.

  • Windows: open the Windows Security app and go to Firewall and network protection. Allow an app through firewall is where you let an app through if the firewall is blocking it (Microsoft’s guide).
  • Mac: choose Apple menu > System Settings, click Network, then Firewall. Click Options to see which apps are allowed (Apple’s steps).
  • Other security software: check its settings to see whether it is blocking Chrome or the site.

Step 4: Reset the network settings on Windows

Microsoft’s Wi-Fi troubleshooting guide gives these commands:

  1. Select Search on the taskbar, type command prompt, and choose Run as administrator.
  2. Run, in order: netsh winsock reset, netsh int ip reset, ipconfig /release, ipconfig /renew, ipconfig /flushdns.
  3. Check whether the site loads.

Microsoft’s last resort is Network reset (Windows 11: Settings > Network & internet > Advanced network settings > Network reset), which reinstalls your network adapters. You may need to set up VPN software again afterwards.

On a Mac, you can renew your address from System Settings > Network, your network service, Details > TCP/IP > Renew DHCP Lease (Apple’s steps).

Step 5: Rule out Chrome

If other browsers load the site and Chrome does not, follow Google’s browser steps:

  1. Open the site in an Incognito window. If it works there, turn off extensions at chrome://extensions or delete browsing data.
  2. Update Chrome and restart it.

Related errors

Frequently asked questions

Is ERR_CONNECTION_TIMED_OUT my fault or the website’s?

If only one site does it, it is most likely the site. If every site does it, look at your connection, proxy or firewall.

What is the difference between ERR_CONNECTION_TIMED_OUT and ERR_TIMED_OUT?

Google lists them together with the same meaning for you: the page took too long to connect. The fixes are the same.