“Took too long to respond” means the browser received no response to its connection attempt in time. “Connection was reset” means the connection was cut off by a TCP reset signal. Open the page on another device on your network, then on your own device via mobile data. This way you separate a computer failure from a network or website problem. For other error codes, use the general diagnostic procedure for “This site can’t be reached”.
Why a timeout and a reset require different checks
With ERR_CONNECTION_TIMED_OUT, the connection attempt received no response in time. In short, the browser waited and gave up. Possible causes: an unreachable server, packet loss, or a filter that silently drops traffic.
With ERR_CONNECTION_RESET, a TCP RST (reset) signal arrived. TCP (Transmission Control Protocol) maintains the connection, and a valid RST ends it. According to the TCP standard, a reset is sent when a segment (a portion of data) appears unrelated to the current connection.
The reset may come from the server, a device along the path, or a local firewall (network filter). The message in Chrome does not show the sender. A reset does not prove blocking by your provider.
Why a timeout and a reset require different checks
The reset may come from the server, a device along the path, or a local firewall (network filter).
The message in Chrome does not show the sender.
In the Chromium source code, on which Chrome and Edge are based, these errors differ as follows:
| Browser code and internal number | What happened | What to check |
|---|---|---|
| ERR_CONNECTION_TIMED_OUT, −118 | The connection attempt did not complete in time | Availability via another network, local filters |
| ERR_CONNECTION_RESET, −101 | The connection was reset by a TCP RST signal | Whether the reset recurs on another device and connection |
| ERR_CONNECTION_REFUSED, −102 | The connection attempt was refused | Correctness of the address; if the refusal occurs across different networks, report it to the site owner |
| ERR_CONNECTION_ABORTED, −103 | The connection was aborted after a timeout: no ACK (acknowledgement that the sent data was received) arrived | Recurrence of the error and network condition |
| ERR_EMPTY_RESPONSE, −324 | The server closed the connection without sending data | Reloading the page and access via another network |
Does the error follow the device or the network?
Compare the same page at roughly the same time. On the phone, switch off Wi-Fi before testing mobile data. A different browser is not a substitute for a different network.
| Comparison result | Where to look for the cause | Next step |
|---|---|---|
| The second device on the same Wi-Fi opens the page | The first computer, its browser, or security software | Check incognito mode, extensions and filters |
| Neither device opens the site on Wi-Fi, but it is reachable via mobile data | The router, the provider, or the route from this network | Check your own network, keep the results for the provider |
| On one computer, a different browser opens the page | Settings, extensions, or data of the first browser | Check its profile |
| The site is unreachable even via an independent network | A site outage is possible; two attempts are not enough for a final conclusion | Check whether the site is down for others too |
If only your home network is failing, restart your modem and router. Microsoft recommends switching off the power for at least 30 seconds, then switching it back on and waiting for it to boot.
Example scenario: a phone on home Wi-Fi opens the page, while a laptop gets a reset both at home and via mobile data. Check the laptop first.
Chrome resets the connection because of an extension or a filter
If only one computer is failing, follow Chrome’s recommendations. After each change, retry loading the page.
- Incognito: open Chrome → Menu → New incognito window. If the page loads, check your extensions and saved data.
- Extensions: open Chrome → Menu → Extensions → Manage extensions. Turn extensions off and re-enable them one at a time, checking when the error returns.
- Browser data: clear browsing data in Chrome’s settings (Delete browsing data) to remove the cache and cookies. After deleting cookies (saved site data), you may need to sign in again.
- Network filter: check the firewall or antivirus log. If a block on Chrome is visible, fix the rule. Do not leave protection disabled.
- Proxy: check the system proxy settings in Windows. A proxy is an intermediary server. ERR_PROXY_CONNECTION_FAILED, code −130, means a failure to connect to it. Remove only an unnecessary setting you are familiar with.
Note: on a work or managed device, security and proxy settings are changed by the administrator. Give them the page address, the error code and the results of the network comparison.
How to check network responses with ping and tracert in Windows
Open Start → type “Command Prompt” → Open. Replace SITE_NAME with the domain without the protocol or page path. These commands check network responses, but not whether the whole site loads.
Ping receives no response
ping SITE_NAMEPing uses ICMP (Internet Control Message Protocol) to check whether a host is reachable. In Windows, four requests are sent by default, with a wait of up to 4000 ms for each reply. If no response arrives, “Request timed out” appears. This is the ping waiting time, not Chrome’s. The parameters are documented in Microsoft’s reference.
- Replies arrive: the host responds to service requests. This does not yet confirm that the web server is working.
- No replies arrive: connection loss or ICMP filtering is possible. The absence of replies does not prove the site is unreachable.
- The host name is not found: a DNS (Domain Name System) check is needed first, which translates the site name into a network address. Its steps are given on the main page.
Tracert shows asterisks along the path
tracert /d SITE_NAMETracert shows the responding hosts along the path to the destination. The /d option speeds up the output by disabling the resolution of router names. Each line corresponds to a hop, and an asterisk means no timely response.
Asterisks do not indicate where the break is: some routers forward traffic but do not respond to probes. In Microsoft’s example, hops 14–16 show “Request timed out”, while the destination is reached at hop 17.
Look at where replies stop before the end of the trace. This is a lead for support, although filtering of service messages is possible. Save the output and the time of the error. A trace does not establish the sender of the RST.
How to check network responses with ping and tracert in Windows
The site works via mobile data, but the connection drops at home
If the site works via mobile data but the connection drops at home, you can test a different path from your own device using CitadelVPN. A VPN (virtual private network) routes the connection through the service’s server. For difficult networks, CitadelVPN lists the VLESS protocol with tcp/gRPC/xhttp variants and the Hysteria2 protocol.
Add the service’s subscription to a compatible client, refresh the list, select an available connection with one of these protocols and retry loading the page. Availability and speed need to be checked yourself: there is no guarantee that the site will open or that the connection will stay stable. Success shows a dependence on the connection path, but does not prove blocking.
If the site is down for everyone, a VPN will not help. On someone else’s, work or school network, contact the administrator. Do not use this check to circumvent its filters or restrictions imposed by a court or regulator.
Frequently asked questions about similar symptoms
An error appeared after switching from Wi-Fi to mobile data. What should I do?
The cause may be ERR_NETWORK_CHANGED, internal code −21: the network changed during loading. Wait for the connection and reload the page. If the message returns without any action on your part, check whether the device is switching between networks.
Ping fails, but the site opens. Does anything need fixing?
This happens with ICMP filtering: service requests go unanswered, while the web connection works. If the page opens consistently, there is no need to change settings just for the sake of ping replies.
Does “504 Gateway Timeout” mean the same timeout?
Code 504 is a response from HTTP (the HyperText Transfer Protocol): the site’s gateway did not receive a response from the server behind it in time. The browser did receive a response, so the situation differs from ERR_CONNECTION_TIMED_OUT. Usually site administrators fix the problem; if everything works for others, check your own connection. For more details, see the reference on code 504.
What to fix based on the results of the checks
Timeout −118 means the connection attempt did not complete in time; reset −101 corresponds to a TCP RST. If only one computer is failing, check Chrome, the proxy and security software. If only one network is failing, give the provider the site address, the time of the error, the comparison with mobile data and the trace output. If a site-wide outage is confirmed, wait for it to be fixed by the site’s owner.
For name errors, DNS flushing and the remaining branches, return to the general diagnostic procedure for the “This site can’t be reached” error.