ERR_CONNECTION_RESET: What It Means and How to Fix It

What a Connection Reset Means Technically

A TCP RST (reset) packet is the network equivalent of hanging up mid-sentence. Unlike a normal connection close (FIN/ACK handshake), a RST immediately terminates the connection with no further exchange. ERR_CONNECTION_RESET means your browser received a TCP RST after the connection was already established and communication had begun — or the RST arrived during the TLS handshake, before any HTTP data was exchanged.

This is distinct from ERR_CONNECTION_REFUSED, where a RST arrives in response to the initial SYN packet (meaning the port was never open). A reset mid-session means something actively terminated an existing connection.

Who Sends the RST

The reset can originate from three different places, each with different implications:

• The server: The web server or application crashed, ran out of resources, applied a rate limit, or enforced a session timeout.
• A middlebox firewall or ISP DPI: Deep packet inspection at the ISP or a corporate firewall identifies the traffic type and injects a RST to terminate it — common with P2P traffic, certain streaming protocols, or content the ISP deems undesirable.
• Your local antivirus or firewall: SSL inspection tools intercept the TLS connection and can inject RST packets if they mishandle the re-encryption or encounter a certificate they distrust.
• A VPN endpoint: A VPN that drops the tunnel mid-session may generate a RST from the VPN server as the tunnel collapses.

Most Likely Causes (Ranked)

1. Router NAT table full — too many simultaneous connections exceed the router's state table
2. Antivirus HTTPS/SSL inspection issuing RST due to a certificate mismatch or inspection bug
3. ISP deep packet inspection throttling or resetting specific traffic types (P2P, streaming)
4. Target server overload, crash, or rate-limiting your IP
5. Unstable Wi-Fi causing brief disconnection mid-session
6. VPN tunnel collapsing mid-request
7. MTU mismatch — packets too large for the path, causing fragmentation issues that trigger resets

Diagnosis: Using Wireshark

To definitively identify who is sending the RST, capture traffic with Wireshark. Apply the display filter tcp.flags.reset == 1 to show only RST packets. Examine the source IP of each RST: if it originates from your local machine's loopback or antivirus process, local software is the cause; if it comes from the server IP, the server is resetting; if it comes from an unexpected intermediate IP, a middlebox is injecting it. The TTL value of the RST packet can also help — an injected RST from an ISP middlebox often has a different TTL than normal packets from the same server.

Fix Steps

Step 1: Restart your router

A router NAT table that has accumulated tens of thousands of connection state entries can become unstable. A reboot clears the state table instantly. If the problem recurs quickly after a reboot, the router's connection limit is too low for your usage pattern — check the router's connection tracking or session table settings.

Step 2: Disable antivirus HTTPS scanning

Bitdefender, Kaspersky, ESET, Avast, and Norton all offer SSL/HTTPS inspection features that intercept TLS connections. A bug or misconfiguration in these scanners is one of the most common causes of ERR_CONNECTION_RESET, particularly after antivirus or browser updates. Temporarily disable HTTPS scanning in your antivirus settings and retest. If the problem disappears, add the affected site to the antivirus exclusion list or update the antivirus to the latest version.

Step 3: Switch to wired Ethernet

If the error comes and goes intermittently, weak Wi-Fi is a strong suspect. Brief signal drops during a TCP session cause the remote server to time out and send a RST. A wired Ethernet connection eliminates wireless reliability as a variable.

Step 4: Test with a VPN

If the error occurs only on specific sites or protocols and you suspect ISP DPI interference, connect a VPN and retest. If the resets disappear on VPN, your ISP is injecting RST packets for that traffic. If resets continue on VPN, the cause is either local (antivirus, router) or server-side.

Step 5: Check for MTU mismatch

A common but overlooked cause is MTU mismatch, especially when using a VPN. The default Ethernet MTU is 1500 bytes; a VPN tunnel adds overhead, reducing the effective MTU to around 1400–1450 bytes. If large packets are being dropped and the connection falls back incorrectly, sessions can reset. Test by lowering MTU on Windows: netsh interface ipv4 set subinterface "Wi-Fi" mtu=1400 store=persistent. On macOS: sudo ifconfig en0 mtu 1400. If resets stop, investigate the proper MTU for your VPN configuration.

Step 6: Test in incognito mode

Browser extensions that modify or intercept requests — privacy tools, cookie managers, request blockers — can alter headers in ways that cause servers to reject or reset connections. Incognito mode disables all extensions by default. If incognito works, disable extensions one at a time in normal mode to isolate the offender.

Difference from ERR_CONNECTION_REFUSED

ERR_CONNECTION_REFUSED means a RST arrived in response to the initial SYN — the server (or a firewall) rejected the connection attempt before it was ever established. No data was exchanged. ERR_CONNECTION_RESET means the connection was established and then terminated with a RST mid-session. The distinction matters: refused connections point to blocked ports or down services; reset connections point to active interference or server-side problems during an existing session.

Frequently Asked Questions

Can a slow internet connection cause ERR_CONNECTION_RESET?

Slow speed alone does not cause resets — instability does. A steady 5 Mbps connection will not reset TCP sessions. A 100 Mbps connection with intermittent 100% packet loss bursts will cause resets constantly, because the remote server stops receiving acknowledgements and eventually sends a RST or the local stack times out.

Does a VPN fix ERR_CONNECTION_RESET?

It can, by routing around ISP DPI or a bad network path. But if resets occur on the VPN too, the cause is local — router, antivirus, or Wi-Fi instability. A VPN also introduces its own reset risk if the tunnel is unstable, so compare behavior carefully: on VPN to one server, on VPN to a different server, and off VPN entirely.