Web & Browsers

Chrome "This Site Can't Be Reached" (ERR_CONNECTION_TIMED_OUT / REFUSED / RESET)? Fix Order

Published June 10, 2026 · by The FixHub Team

Chrome shows “This site can’t be reached” with one of: ERR_CONNECTION_TIMED_OUT, ERR_CONNECTION_REFUSED, ERR_CONNECTION_RESET, or ERR_NAME_NOT_RESOLVED.

What they mean (and why to work outward): all four mean Chrome couldn’t establish the connection — but the layer differs. NAME_NOT_RESOLVED = DNS can’t find the address; TIMED_OUT = no response in time; REFUSED/RESET = the server (or something between) actively dropped it. So fix from your side outward rather than randomly.

Fix 1: Confirm it’s not just one site

  • Open a different site. Only one site failing → it’s that site/your DNS (skip to Fix 3). Everything failing → it’s your connection (Fix 2).

Fix 2: Your connection

  • Reload (Ctrl+R). Toggle Wi-Fi off/on; try a different network.
  • Reboot your router/modem (off 30s, on).
  • Turn off any VPN/proxy temporarily — a dead VPN causes all four errors.
  • If the whole PC has no internet, see Wi-Fi connected but no internet.

Fix 3: DNS (especially ERR_NAME_NOT_RESOLVED)

  • Flush DNS — admin Command Prompt: ipconfig /flushdns.
  • Try a public DNS (e.g. 8.8.8.8 / 1.1.1.1) on your adapter.
  • For a deeper reset, see reset TCP/IP & Winsock.

Fix 4: Chrome-side culprits

  • Open the site in an Incognito window — if it works, an extension is the cause (disable extensions one by one).
  • Clear cache & cookies (Settings → Privacy → Clear browsing data).
  • Check proxy settings (Settings → System → Open your computer’s proxy settings) — a leftover proxy from removed software causes REFUSED/RESET.

Fix 5: Firewall / antivirus

Security software can block Chrome or reset connections. Temporarily disable third-party firewall/AV to test; if that’s it, add an exception for Chrome.

FAQ

Which one is DNS? ERR_NAME_NOT_RESOLVED (and DNS_PROBE_FINISHED_NXDOMAIN) — the address can’t be resolved. See DNS_PROBE_FINISHED_NXDOMAIN.

Only HTTPS sites fail with a security warning? That’s a certificate/clock issue, not connection — see “Your connection is not private”.

Sources: Google Chrome Help — Get help with common error messages in Chrome