How to Fix ERR_CONNECTION_RESET in Chrome

Network Intermediate 7 min read Published July 16, 2026

ERR_CONNECTION_RESET is the message Chrome shows when a TCP connection is forcibly torn down before the HTTP transaction can finish. Technically, the remote peer — or any router, proxy, or security appliance sitting between you and the server — sends a TCP RST packet, which tells your browser: “this connection no longer exists, stop trying.” Chrome has no choice but to abort and surface the error to you.

A reset is different from the two errors it is most often confused with. ERR_CONNECTION_REFUSED means a machine answered immediately but nothing was listening on the port. ERR_CONNECTION_TIMED_OUT means no answer came back at all within the waiting window. ERR_CONNECTION_RESET sits in between: a connection existed (or was being established) and was then abruptly killed. That abruptness is the clue — something actively intervened.

The intervention usually comes from one of six places: an unstable network, a VPN or proxy dropping its tunnel, corrupted browser or DNS cache, a broken TCP/IP stack, an overzealous firewall or antivirus performing HTTPS inspection, or an outdated network adapter driver. The fixes below walk through each in the order that solves the most cases the fastest.

Common Causes at a Glance

Likely Trigger	Root Cause	First Action
Unstable Wi-Fi or ISP dropouts	Packet loss forces a peer reset	Restart router; test a wired connection
VPN or proxy enabled	Tunnel drops; proxy sends RST	Disable VPN/proxy and retry
Recently cleared or old profile	Corrupted cache/cookies	Clear browsing data; flush DNS
After malware or “optimizer” use	TCP/IP stack corruption	Run `netsh int ip reset`
Antivirus or firewall update	HTTPS inspection resets TLS	Disable inspection; add Chrome exception
Old or rolled-back NIC driver	Driver-level connection resets	Update network adapter driver

Step 1: Check Your Network Connection

Before changing any settings, confirm the link itself is healthy. A flaky wireless signal or an ISP that intermittently drops packets will cause the remote server (or a middlebox) to give up and send a reset. The fastest test is to load the same site from a completely different network — a mobile hotspot works well. If it loads there but not on your main connection, the problem is local to your network.

Restart your router and modem: power them off, wait 30 seconds, and power them back on. If you are on Wi-Fi, move closer to the access point or switch to an Ethernet cable to rule out interference. Run a quick ping test to measure loss:

# Windows: send 50 packets to a stable host
ping -n 50 1.1.1.1

# macOS / Linux
ping -c 50 1.1.1.1

If you see more than a few percent packet loss or wildly varying round-trip times, your network is the culprit and no amount of browser tweaking will help until the link is stable.

Step 2: Disable VPN and Proxy

VPNs and proxies are among the most common causes of ERR_CONNECTION_RESET. When a VPN tunnel drops mid-session — common on overloaded or free VPN servers — the encrypted stream breaks and Chrome sees a reset. A misconfigured or abandoned proxy produces the same effect by forwarding your request to an endpoint that no longer exists.

Turn off your VPN client completely (do not just disconnect; quit the application). Then clear any leftover proxy configuration. On Windows, go to Settings > Network & Internet > Proxy and disable “Use a proxy server.” Check for proxy environment variables on macOS and Linux:

# Print any active proxy variables
echo "http_proxy=$http_proxy"
echo "https_proxy=$https_proxy"

# Clear them for the current session
unset http_proxy https_proxy all_proxy

In Chrome, disable extensions that force traffic through a proxy (many ad-blockers and “privacy” extensions do this). Reload the page. If the error disappears, re-enable items one at a time to identify the offender.

Step 3: Clear Browser Cache and Cookies

Corrupted cached data — especially a half-written response or a stale HSTS entry — can make Chrome attempt a connection that the server immediately resets. Clearing cache and cookies removes this corrupted state.

In Chrome press Ctrl+Shift+Delete (or Cmd+Shift+Delete on macOS), set the time range to “All time,” and select Cookies and other site data plus Cached images and files, then click Clear data. Also flush the operating system DNS cache so stale IP mappings do not send you to the wrong host:

# Windows
ipconfig /flushdns

# macOS
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

# Linux (systemd-resolved)
sudo resolvectl flush-caches

Restart Chrome fully (quit from the taskbar, not just close the tab) and try the site again. Testing in an Incognito window is a good shortcut: if Incognito works, the problem is almost certainly cached data or an extension.

Step 4: Reset the TCP/IP Stack

If the Windows networking stack itself has become corrupted — often after malware, an aggressive “PC optimizer,” or a bad VPN uninstall — connections can be reset at the operating system level before they ever reach the server. Resetting the stack restores the TCP/IP and Winsock catalogs to their factory defaults.

Open Command Prompt as Administrator and run both commands, then reboot:

# Reset the TCP/IP stack to its installation defaults
netsh int ip reset

# Reset the Winsock catalog
netsh winsock reset

# Flush DNS one more time after the reset
ipconfig /flushdns

Rebooting is mandatory — the changes are not fully applied until Windows restarts. After the reboot, note that any custom static IP, DNS, or VPN adapter settings may need to be reconfigured, because the reset clears them. This is a safe operation and does not delete personal files.

Step 5: Check Firewall and Antivirus

Security software that performs HTTPS inspection (sometimes called SSL/TLS scanning or web shield) intercepts your encrypted traffic to scan it. When the scanner cannot keep up, or when it rejects a certificate, it tears the connection down with a reset — and Chrome reports ERR_CONNECTION_RESET. This often affects many sites at once and starts right after an antivirus update.

Temporarily disable HTTPS/TLS scanning in your antivirus (look under “Web Shield,” “HTTPS scanning,” or “SSL inspection”), then reload the page. If the site loads, re-enable scanning and add Chrome — or the affected domain — to the antivirus exclusion list. Do the same for the Windows Defender Firewall and any third-party firewall: turn it off briefly to test, and if that resolves the error, create an inbound/outbound allow rule for Chrome.

# Windows: check firewall state
netsh advfirewall show allprofiles state

# Temporarily disable (test only; re-enable after)
netsh advfirewall set allprofiles state off

# Re-enable
netsh advfirewall set allprofiles state on

Never leave your firewall permanently disabled. Use this only to confirm the diagnosis, then switch back on and configure proper exceptions.

Step 6: Update Network Drivers

An outdated, generic, or buggy network adapter driver can reset connections at the hardware interface level. This is especially common after a Windows feature update rolls back a manufacturer driver to a Microsoft default. Updating the driver often resolves persistent, otherwise-unexplained resets.

Open Device Manager > Network adapters, right-click your adapter, and choose Update driver > Search automatically. For the most reliable result, download the latest driver directly from your laptop or motherboard manufacturer (or the chipset maker — Intel, Realtek, Broadcom) and install it manually. After updating, reboot and test:

# Windows: list your network adapters and driver versions
ipconfig /all

# PowerShell: get adapter driver details
Get-NetAdapter | Select-Object Name, InterfaceDescription, DriverVersion

If a brand-new driver makes things worse, you can roll back: in Device Manager, open the adapter's properties, go to the Driver tab, and click Roll Back Driver.

Network Diagnostic Commands

When the simple fixes do not work, these commands help pinpoint where the reset originates. Run them in order and compare the results against a known-good network if possible.

# 1. Basic connectivity and packet loss
ping -n 20 example.com

# 2. Trace the route to find where packets stop
tracert example.com        # Windows
traceroute example.com     # macOS / Linux

# 3. Check DNS resolution
nslookup example.com

# 4. Full network configuration
ipconfig /all              # Windows
ifconfig                   # macOS / Linux

# 5. Reset the stack (repeat of Step 4, run as Admin)
netsh int ip reset
netsh winsock reset

Interpreting the output: if ping shows steady replies but tracert stops at your ISP's gateway, the reset is happening upstream — contact your ISP or use a VPN to route around it. If nslookup returns the wrong IP, your DNS is poisoned or stale and you should switch to a public resolver like Cloudflare (1.1.1.1) or Google (8.8.8.8).

Quick Reference: Causes and Fixes

Symptom	Root Cause	Fix
Reset on every site, all devices on the network	ISP or router problem	Restart router; test another network; contact ISP
Reset only while VPN is connected	VPN tunnel dropping	Disable VPN; switch VPN server or protocol
Reset in normal mode, works in Incognito	Corrupted cache or extension	Clear cache/cookies; disable extensions
Reset started after malware cleanup	Corrupted TCP/IP stack	`netsh int ip reset` + `netsh winsock reset`
Reset began after antivirus update	HTTPS inspection resetting TLS	Disable SSL scanning; add Chrome exception
Reset after a Windows update	Rolled-back network driver	Update or roll back the NIC driver

Frequently Asked Questions

Is ERR_CONNECTION_RESET a sign of a virus?

Not directly, but malware can cause it. Some malicious software rewrites proxy settings or corrupts the network stack, which then produces resets. If the error appeared suddenly alongside pop-ups or slow performance, run a full system scan with Windows Defender or a reputable antivirus, then follow Step 4 to reset the TCP/IP stack.

Why does ERR_CONNECTION_RESET happen on only one website?

When a single site is affected, the cause is usually server-side or a TLS mismatch: the server closes the connection during the HTTPS handshake, often because of an outdated cipher, a misconfigured load balancer, or the site blocking your region or IP. Try the site over a VPN or mobile network; if it loads, the issue is between your network and that specific server, not your computer.

Does ERR_CONNECTION_RESET mean I have been blocked?

It can, but it is not the most common reason. Some firewalls and services respond to blocked IPs with a reset rather than a clean refusal. However, network instability, VPN drops, and antivirus inspection are far more frequent causes. Confirm by testing from a different network before assuming you are blocked.

Will resetting the TCP/IP stack harm my computer?

No. netsh int ip reset is a safe, Microsoft-supported command that restores the network stack to its default state. It does not delete your files or applications. The only side effect is that custom network settings — static IP addresses, manual DNS servers, and some VPN adapters — may need to be reconfigured afterward.

Conclusion

ERR_CONNECTION_RESET means something forcibly closed your TCP connection, and in the vast majority of cases that “something” lives on your side of the wire: an unstable network, a VPN tunnel dropping, corrupted cache, a broken TCP/IP stack, aggressive antivirus inspection, or an outdated network driver. Work through the six steps in order — most readers resolve the error at Step 1 or Step 2. If every step fails and the problem affects all devices on your network, the reset is happening upstream at your ISP, and the fix is a call to your provider or a VPN to route around the broken path.