---
title: "This Site Can't Be Reached: What It Means and Why It Happens"
description: "This Site Can't Be Reached means Chrome could not connect to the site. We explain each error code and how to tell whether the problem is yours or the site's."
url: https://proxynet.io/blog/this-site-cant-be-reached
date: 2026-09-24
author: "Enver Kaya"
category: "Tutorial"
lang: en
---

# This Site Can't Be Reached: What It Means and Why It Happens

In the evening you want to check your basket on a shopping site. Chrome opens a grey screen instead: "This site can't be reached" in large letters, "The connection was reset." underneath, and `ERR_CONNECTION_RESET` at the bottom. Reloading brings the same screen, yet the site opens on your phone over mobile data. Which one is broken: the computer, the router or the site?

This guide reads that screen line by line: what each code means, what Chrome means by "Checking the proxy and the firewall", four checks that show whose problem it is, and the causes on phones.

> **Note: Short answer**
>
> "This site can't be reached" means Chrome could not set up a connection, so your request never got to the site. The code at the bottom says what broke. `DNS_PROBE` or `NAME_NOT_RESOLVED`: the name could not be turned into an address. `TIMED_OUT`: nothing answered. `REFUSED`: the machine is there but refused the connection. `RESET`: a connection opened and was then cut. First check whether no site opens or only this one. Then try the site on your phone with Wi-Fi off. If it opens there, the problem is in your network or device; if it opens nowhere, it is most likely the site's, and the fix is to wait.

## What does "This site can't be reached" mean?

Chrome shows this screen when it cannot connect to a site at all. That is the difference from a 404, 403 or 503 page, where the site's server answered with an error. The same goes for a [429 Too Many Requests](/blog/http-429-too-many-requests) response and for Cloudflare's [Verifying you are human](/blog/cloudflare-verify-you-are-human) and [Sorry, you have been blocked](/blog/sorry-you-have-been-blocked) screens: the site is up and talking to you.

The large heading is shared by many errors; the grey line under it and the code in capitals name the exact failure. Browsers built on Chrome's engine (Chromium), such as Edge, Brave and Opera, show the same codes, even where the heading is worded differently.

With the cable or Wi-Fi fully disconnected, Chrome shows a different heading, "No internet" (`ERR_INTERNET_DISCONNECTED`). If the line says "There is something wrong with the proxy server, or the address is incorrect", the cause is a proxy setting, covered in [Proxy Server Not Responding](/blog/proxy-server-not-responding).

## How does a browser open a site, and where does the error appear?

Opening a page takes four steps, and the code tells you which one failed:

1. **Name lookup.** The browser turns the name (`example.com`) into an IP address, the server's numeric address. It asks DNS, the system that works like the internet's phone book. If no address comes back, you see `ERR_NAME_NOT_RESOLVED` or a `DNS_PROBE_FINISHED_*` code.
2. **Opening the connection.** The browser knocks on a numbered door of the server, called a port; secure sites use port 443. No answer at all gives `ERR_CONNECTION_TIMED_OUT`. "This door is closed" gives `ERR_CONNECTION_REFUSED`.
3. **Exchanging data.** The connection is open; on secure sites the browser and server first set up encryption (TLS), then the request goes out. If either end, or a device in between, cuts the connection now, the code is `ERR_CONNECTION_RESET`. If the connection is closed before the page arrives, Chrome says the site "unexpectedly closed the connection" (`ERR_CONNECTION_CLOSED`).
4. **The response.** From here on you see the site's page or an HTTP error it sent, never this screen.

In the first three steps no page arrives, so clearing the cache rarely helps.

## What does the code at the bottom of the screen tell you?

The table matches Chrome's wording with its code and step. The numbers in brackets come from Chromium's [network error list](https://chromium.googlesource.com/chromium/src/+/HEAD/net/base/net_error_list.h).

| Line on the screen | Code | Where it broke | Common causes | Check first |
|---|---|---|---|---|
| "The connection was reset." | `ERR_CONNECTION_RESET` (-101) | Opened, then cut | Security software, a VPN or proxy app, a network filter | Does it open on another network? |
| "example.com took too long to respond." | `ERR_CONNECTION_TIMED_OUT` (-118) | No answer | Server down or overloaded, a firewall dropping traffic | Is it down for everyone? |
| "example.com refused to connect." | `ERR_CONNECTION_REFUSED` (-102) | Machine reached, port closed | Wrong port, site maintenance | The address and port |
| "Check if there is a typo in example.com." | `DNS_PROBE_FINISHED_NXDOMAIN` | The name does not exist | A typo, an expired domain | The spelling |
| "example.com's server IP address could not be found." | `ERR_NAME_NOT_RESOLVED` (-105) | Lookup failed | A DNS server that does not answer | DNS settings, if no site opens |

"example.com unexpectedly closed the connection." (`ERR_CONNECTION_CLOSED`, -100) can appear under the same heading and is checked like a reset. `ERR_EMPTY_RESPONSE` ("example.com didn't send any data.") comes under a different heading, "This page isn't working".

## Why does "The connection was reset" appear?

A reset means the connection had opened, and then one end or a device between them sent a signal saying "this connection is over". The TCP standard ([RFC 9293](https://www.rfc-editor.org/rfc/rfc9293.html)) calls it RST. The browser only knows the line was cut, not who cut it.

The usual sources:

- **Security software** whose "web protection" or "HTTPS scanning" sits in the middle of your connections.
- **A VPN, proxy app or browser extension** that drops the connection it carries.
- **A work, school or dormitory network filter** cutting sites its rules do not allow.
- **A short fault on the router or line**, usually hitting several sites for a few minutes.
- **Protective equipment in front of the site** that cuts connections it does not like.

When the reset appears on one site, only on one network, and the site opens elsewhere, a device on the route may be cutting the connection. That can be a network rule, a block by the internet provider or a legal decision. The problem is then not in your device, and no setting fixes it. On a work or school network, ask the administrator.

## What is the difference between "took too long to respond" and "refused to connect"?

"Took too long to respond" (`ERR_CONNECTION_TIMED_OUT`) means no reply came. The server may be off or too busy, a firewall may drop the traffic silently, or the name may point to an old address.

"Refused to connect" (`ERR_CONNECTION_REFUSED`) is a clearer answer: the machine replied, but no program listens behind that port. Home users see it most on the router's page (such as `192.168.1.1`) or with a wrong port in the address; public sites show it briefly during maintenance. The number after the colon is explained in [What Is Port 8080?](/blog/port-8080).

## What do the DNS errors mean?

`NXDOMAIN` is a DNS answer saying the name does not exist ([RFC 9499](https://www.rfc-editor.org/rfc/rfc9499.html) lists it as the name error). Chrome shows `DNS_PROBE_FINISHED_NXDOMAIN` and suggests checking for a typo. Usually a letter is missing or the domain has expired.

The other DNS codes point to your side. `DNS_PROBE_FINISHED_NO_INTERNET` comes with the "No internet" heading. `DNS_PROBE_FINISHED_BAD_CONFIG` means your DNS server did not work. If you set a provider by hand in Chrome's secure DNS or Android's Private DNS and it stops answering, every site fails and Chrome's help box says "Check your Secure DNS settings". Google's [Chrome security help page](https://support.google.com/chrome/answer/10468685?hl=en) notes that with a custom provider Chrome does not fall back to normal lookups. The desktop path is **Settings > Privacy and security > Security**, then **Use secure DNS** under **Advanced**.

Changing DNS has one place here: when no site opens and the code is a DNS one, your provider's DNS may be faulty, and trying another is a test. It is not a way to open a blocked site. How lookups travel is in [WebRTC and DNS Leaks](/blog/webrtc-dns-leak).

## What does "Checking the proxy and the firewall" mean?

This line is not an error. It is an item in Chrome's **Try:** list, next to "Checking the connection" and "Running Windows Network Diagnostics". For some DNS errors it reads "Checking the proxy, firewall, and DNS configuration" (or "Secure DNS" in place of "DNS"). It appears on computers; Chrome on Android does not show it.

Clicking it opens a help box. In summary: allow Chrome through your firewall or antivirus (if it is already allowed, remove and re-add it), and if you should not be using a proxy, open your computer's proxy settings from Chrome's **Settings > System**. In practice that is two questions.

**Is a proxy setting on without your knowledge?** On Windows, open **Settings > Network & internet > Proxy**. If **Use a proxy server** is on under **Manual proxy setup** and you never set it, that is your lead. Turning it off, and what to do when it comes back, is in [Proxy Server Not Responding](/blog/proxy-server-not-responding). Chrome takes the setting from Windows, as [How to Set Up Proxy Settings in Windows and Chrome](/blog/windows-chrome-proxy-settings) shows. For other devices see [Mac and Safari](/blog/mac-safari-proxy-settings), [Android](/blog/android-proxy-settings) and [iPhone](/blog/iphone-proxy).

**Is security software blocking Chrome?** Open **Windows Security > Firewall & network protection > Allow an app through firewall** and check that Chrome is listed. Do not switch the whole firewall off. Microsoft's page on the [risks of allowing apps through Windows Firewall](https://support.microsoft.com/en-us/windows/risks-of-allowing-apps-through-windows-firewall-654559af-3f54-3dcf-349f-71ccd90bcc5c) says to allow only apps you recognise, and that allowing an app is safer than opening a port. With third-party antivirus, pause only "web protection" or "HTTPS scanning" for a quick test, then turn it back on. How a firewall differs from a proxy is in [Proxy vs Firewall](/blog/proxy-vs-firewall); if you use a proxy on purpose, test it with [How to Test a Proxy](/blog/how-to-test-a-proxy).

## Is the site down, or is it just me?

Four checks, from the quickest to the slowest:

1. **Does another site open?** If none does, the problem is your connection. Turn the router off, wait 30 seconds and turn it on.
2. **Open the site on your phone with Wi-Fi off.** If it opens over mobile data, the problem is your home network or computer. If not, the site may be down.
3. **Try another device on the same Wi-Fi.** If it opens there, the first device has a proxy setting, security software or an extension in the way.
4. **Look outside.** An independent "is it down" checking site, the site's status page or its official social media account shows whether others see the same.

Sites also fail for everyone when exam results, ticket sales or a big sale bring a crowd at once. Visitors then get a timeout or a 503 page, and reloading every second only adds load. If the site is yours, [What Is Uptime Kuma? Setup and Monitoring Through a Proxy](/blog/uptime-kuma) shows how to set up a monitoring tool so that you hear about an outage from it rather than from your visitors.

## Why does this error appear on a phone?

Chrome on Android shows the same heading and codes, but the causes are often phone-specific:

1. **Switching between Wi-Fi and mobile data.** A connection can break as the phone changes networks; reload after a few seconds.
2. **A hand-typed Private DNS.** On stock Android it is under **Settings > Network & internet > Private DNS**; on other brands, search Settings for "Private DNS". If that server does not answer, every site fails.
3. **A VPN profile in the background.** Some ad blockers and "data saver" apps filter traffic through one, and connections break when the app fails.
4. **Café, hotel or airport Wi-Fi.** These networks want you to sign in on a login page first, and the phone usually shows a notification asking you to sign in.

On iPhone, Safari shows its own message, but the same checks apply.

## Advanced: how to read nslookup and Test-NetConnection output

You can skip this section. Two commands built into Windows test steps 1 and 2 outside the browser, in PowerShell:

```powershell
nslookup example.com
Test-NetConnection example.com -Port 443
```

If `nslookup` prints `Name:` and addresses, step 1 works. "Non-existent domain" matches `NXDOMAIN`; a timeout means your DNS server did not answer.

`TcpTestSucceeded : True` means the door on port 443 opened, so the problem is in step 3 or the browser. `False` means it did not open; the command does not separate a timeout from a refusal, so read it with Chrome's code. On 24 September 2026, `example.com` gave `True` on port 443 and `False` on port 81, where nothing listens.

## Common mistakes

- **Switching the firewall or antivirus off and forgetting it.** The computer stays exposed.
- **Clearing cache and cookies for every code.** The page never arrived, so nothing changes.
- **Changing DNS for every error.** It only matters for DNS codes.
- **Installing a free VPN or proxy extension "to fix it".** One more program can cut connections, and [free proxies carry their own risks](/blog/are-free-proxies-safe).
- **Pressing the router's reset pinhole instead of restarting it.** It restores factory settings and can erase your provider's login details.

## Decision guide

| Situation | What to do |
|---|---|
| No site opens, code is `DNS_PROBE` or `NAME_NOT_RESOLVED` | Restart the router, check secure DNS and Private DNS; if it continues, call your provider |
| No site opens, heading says "No internet" or mentions a proxy | A different screen; check the device's proxy setting |
| One site fails but opens on mobile data | Try another device on the same Wi-Fi, then check the VPN, extensions and web protection |
| One site, one network, `ERR_CONNECTION_RESET` | A device on the route may be cutting it; ask the network administrator |
| Fails on every network and device | The site's problem; check a status tool and wait |
| Router page refuses or times out | Use the router's Wi-Fi or cable, not mobile data; check the address on its label |
| Chrome suggests "Checking the proxy and the firewall" | Look for a proxy you did not set and check Chrome is allowed through the firewall |

## Frequently asked questions

### Why can't I reach one site when the internet works?

Either the site is down or the path to it is blocked, and the mobile data test separates the two. A reset on only one network may also be a block on that network, which your device cannot fix.

### Why do I get this error on my router's page?

The router's page only opens from its own network. On mobile data, on a VPN or with the wrong address you get "refused to connect" or "took too long to respond". Use the router's Wi-Fi or cable and the address on its label.

### Why does the error appear when I turn on a VPN?

Your traffic now goes through the VPN's server, and if that server does not answer or the site refuses it, Chrome shows this screen. Turn the VPN off and retry; the two tools are compared in [Proxy vs. VPN](/blog/proxy-vs-vpn).

### Why does "The connection was reset" appear on my phone?

Check the Wi-Fi to mobile data switch, a hand-typed Private DNS, a background VPN profile and public Wi-Fi sign-in, in that order. The first one usually clears itself if you reload after a few seconds.

### Why does a site stop opening when everyone visits at once?

A server accepts only so many connections at a time, so a crowd gets timeouts or 503 pages. Retry every few minutes rather than reloading constantly.

### Is "This site can't be reached" the same as a 403 error page?

No. On a 403 or security page the site answered and chose not to show the content; here the connection never reached the site. Cloudflare's versions are covered in [Cloudflare Verifying You Are Human](/blog/cloudflare-verify-you-are-human) and [Sorry, You Have Been Blocked](/blog/sorry-you-have-been-blocked). The block page titled "Access Denied" with a "Reference #18" line at the bottom is explained in [Access Denied Error on Websites: What Reference #18 Means](/blog/access-denied-error).

## Summary

"This site can't be reached" means Chrome could not connect, and the code shows where it broke: DNS codes at the lookup, timeout and refusal while connecting, reset after the connection opened. Ask whether only this site fails and whether it opens over mobile data. Chrome's proxy and firewall hint means checking two settings, not switching protection off. If a proxy setting is the cause, [Proxy Server Not Responding](/blog/proxy-server-not-responding) walks through it, and [our proxy page](/proxy) explains which proxy types exist and what they are for.