Attempting to open a website in Google Chrome only to encounter the error screen stating “This site can’t be reached. The connection was reset. Try checking the connection, checking the proxy and firewall. ERR_CONNECTION_RESET” abruptly halts browsing. The error code ERR_CONNECTION_RESET indicates an abrupt termination of the TCP transmission session: while the initial three-way TCP handshake between Chrome and the destination server was established, the peer connection was suddenly terminated mid-stream by a TCP RST (reset) flag before data packets could be fully transferred. This typically occurs when a local network proxy abruptly closes sockets, third-party antivirus deep packet inspection detects an unhandled TLS certificate sequence, maximum transmission unit (MTU) packet fragmentation occurs, or local network drivers deadlock. This guide covers how to fix ERR_CONNECTION_RESET in Google Chrome.
What Causes ERR_CONNECTION_RESET in Chrome?
TCP socket resets originate from local network stacks, proxy filters, and security software:
- Third-Party Antivirus / Firewall Packet Inspection: Endpoint protection suites (such as Avast, Bitdefender, or AVG Web Shield) intercepting encrypted TLS sessions and dropping the connection when payload signatures clash.
- Corrupted Windows Winsock & IP Routing Tables: Stale TCP/IP network catalog states failing to track open socket states.
- Misconfigured Automated Proxy Settings: The Windows “Automatically detect settings” Web Proxy Auto-Discovery (WPAD) feature querying non-existent proxy pac scripts.
- VPN Network Adapter Clashes: Virtual network interface drivers (TAP/TUN) truncating TCP window sizes during high-bandwidth streaming.
- MTU Size Mismatch: Network routers sending packet frames larger than what upstream intermediate network switches can accommodate without fragmentation.
Method 1: Reset the Windows TCP/IP Stack and Winsock Catalog
Rebuilding network socket interfaces eliminates corrupted TCP state entries.
- Press Win + S, type
cmd, right-click Command Prompt, and select Run as administrator. - Execute the following network reset commands in order:
netsh winsock reset netsh int ip reset ipconfig /release ipconfig /renew ipconfig /flushdns - Close the Command Prompt and restart your computer to apply the newly built network registry bindings.
Method 2: Disable Automated Proxy Detection (WPAD)
Windows proxy detection can cause Chrome to route traffic through defunct local loopback addresses.
- Press Win + R, type
inetcpl.cpl, and press Enter to open Internet Properties. - Select the Connections tab.
- Click the LAN settings button near the bottom.
- Uncheck the box for Automatically detect settings.
- Ensure that Use a proxy server for your LAN is also unchecked.
- Click OK twice to save changes.
- Relaunch Google Chrome and attempt to navigate to the website.
Method 3: Temporarily Disable Antivirus HTTPS Scanning
Antivirus web shields inspect incoming encrypted web packets. If the scanner’s internal decryption buffer overruns, it resets the TCP stream.
- Open your third-party antivirus application (e.g. Avast, AVG, Kaspersky, ESET).
- Navigate to Settings > Protection > Web Shield (or Core Shields).
- Locate settings such as Enable HTTPS scanning or Scan encrypted connections.
- Temporarily disable this feature (or pause the shield for 10 minutes).
- Refresh your Chrome tab. If the page loads immediately, add an exception for the domain or update your security software.
Method 4: Adjust Maximum Transmission Unit (MTU) Size
If network routers enforce packet fragmentation limits, oversized TCP packets are dropped by network switches.
- Open an elevated Command Prompt (Run as administrator).
- View your current network interfaces:
netsh interface ipv4 show subinterfaces - Note the exact interface name (e.g. Wi-Fi or Ethernet) and its MTU (default is typically 1500).
- Set the MTU to 1472 or 1450 to accommodate network overhead:
netsh interface ipv4 set subinterface "Wi-Fi" mtu=1450 store=persistent - Test browsing in Google Chrome.
Method 5: Power Cycle the Wi-Fi Router
Routers maintain stateful packet inspection (SPI) firewalls and NAT connection tables that can run out of memory under high socket churn.
- Disconnect the power cord from the rear of the router and modem.
- Wait 30 seconds.
- Reconnect the power cable and allow 2 minutes for the network lights to turn solid green.
- Reload the webpage in Chrome.
Chrome Connection Error Comparison Matrix
| Error Code | Network Layer Event | Primary Root Cause |
|---|---|---|
ERR_CONNECTION_RESET |
TCP RST flag received during active session | Antivirus HTTPS scanning, proxy failure, or MTU fragmentation |
ERR_CONNECTION_REFUSED |
Immediate TCP RST on port opening | Target server port closed or host service offline |
ERR_CONNECTION_TIMED_OUT |
No reply packets received (silent drop) | Firewall dropping packets or routing blackhole |
ERR_NETWORK_CHANGED |
Default IP route altered during request | Wi-Fi roaming conflict or VPN tunnel flapping |
Frequently Asked Questions
Why does ERR_CONNECTION_RESET happen only on specific websites?
If common search engines and social platforms load normally, the issue usually stems from the target server’s Web Application Firewall (WAF) such as Cloudflare or AWS WAF. The remote firewall may flag your residential IP range, cookie structure, or browser request rate and reset the TCP stream.
Can clearing Chrome browsing data fix connection resets?
Yes. Corrupted SSL session tickets and malformed HTTP cookies stored in the browser can cause web servers to immediately reject and reset the TLS session upon arrival.