ERR_CONNECTION_RESET — Connection Reset in Chrome

Igor Verentsov

ERR_CONNECTION_RESET: Causes & Fix

By Igor Verentsov · Updated Aug 11, 2026

Key idea:

ERR_CONNECTION_RESET means Chrome received TCP RST during TLS handshake or active session. Causes: firewall (local or ISP) drops a packet, antivirus with TLS inspection mangles the handshake, overloaded server where the kernel kills the connection, DPI systems blocking a specific SNI. Fix: disable AV TLS inspection, verify server reachability, try via VPN.

This error blocks HTTPS access. Below: causes, fixes, working config, FAQ.

Free online tool — ping & port checker: instant results, no signup.

Check your host & ports →

Common Causes

Local firewall / Kaspersky TLS inspection cuts packets
ISP-level DPI blocks SNI by domain (common in certain regions)
Server overloaded, kernel TCP accept queue overflowed
Wrong path MTU — TCP segments get dropped
Web process crash (nginx/Apache worker) mid-handshake

Step-by-Step Fix

Disable antivirus TLS inspection for 10 minutes — retest
Reboot the router (sometimes it cuts connections)
Try via VPN or mobile — if it works = ISP DPI
On the server: ss -ltn to confirm listener. dmesg | grep -i tcp — OOM?
Increase net.core.somaxconn and nginx backlog=1024

Check reachability and ports →

Related SSL Errors

TL;DR: Understanding ERR_CONNECTION_RESET

The ERR_CONNECTION_RESET error in Chrome indicates that the connection to the server was unexpectedly closed. This can occur due to various reasons, including server misconfiguration, firewall settings, or issues with the local network. To resolve this, check your network settings, disable any VPNs or proxies, and ensure that your firewall isn’t blocking the connection.

Common Causes of ERR_CONNECTION_RESET

The ERR_CONNECTION_RESET error can be attributed to several underlying issues. Understanding these causes can help you diagnose and resolve the problem effectively:

Network Configuration: Misconfigured network settings can lead to connection resets. This includes incorrect DNS settings or IP conflicts.
Firewall/Antivirus Software: Overzealous firewall or antivirus programs can block legitimate connections. Ensure that your security software is not blocking Chrome.
VPN/Proxy Issues: If you are using a VPN or proxy, they may be causing the connection to reset. Temporarily disabling them can help identify the issue.
Server-Side Issues: The server may be misconfigured, causing it to close connections unexpectedly. Check server logs for errors.
Browser Extensions: Some extensions can interfere with network requests. Disable all extensions and re-enable them one by one to identify the culprit.

Practical Solutions to Fix ERR_CONNECTION_RESET

To resolve the ERR_CONNECTION_RESET error, you can follow these practical steps:

Check Your Internet Connection: Ensure your internet connection is stable. You can run the following command in the Command Prompt to check connectivity:

ping google.com

Reset TCP/IP Stack: If your network settings are corrupted, resetting the TCP/IP stack can help. Open Command Prompt as an administrator and run:

netsh int ip reset

Flush DNS Cache: Flushing the DNS cache can resolve issues related to outdated or incorrect DNS information. Execute this command:

ipconfig /flushdns

Disable Firewall/Antivirus: Temporarily disable your firewall or antivirus software to check if they are causing the issue. If the error disappears, adjust the settings or switch to a different security solution.

Change DNS Settings: Consider switching to a public DNS service like Google DNS or Cloudflare DNS. You can change your DNS settings on Windows by going to:

Control Panel
Network and Internet
Network and Sharing Center
Change adapter settings
Right-click your network connection and select Properties
Select Internet Protocol Version 4 (TCP/IPv4) and click Properties

Then, select Use the following DNS server addresses and enter:

Google DNS: 8.8.8.8 and 8.8.4.4
Cloudflare DNS: 1.1.1.1 and 1.0.0.1

Check for Browser Issues: Clear your browser cache and cookies. Go to Chrome settings, select Privacy and security, and then Clear browsing data.

Review Server Configuration: If you have access to the server, check the configuration files (like httpd.conf for Apache or nginx.conf for Nginx) for any misconfigurations or limits on connection handling.

By systematically addressing each of these areas, you can effectively troubleshoot and resolve the ERR_CONNECTION_RESET error in Chrome.

ICMP PingHost availability and latency

Port ScannerOpen TCP port detection

LatencyResponse time in milliseconds

Packet LossPercentage of dropped packets

Why teams trust us

ICMP+TCP

check protocols

key ports scanned

2,014

checks in 30 days

regions

How it works

Enter IP or domain

ICMP packets sent

Latency & packet loss shown

How Do Ping and Port Scanning Work?

Ping sends ICMP packets to a host and measures response time. Port scanning checks which TCP ports are open and accepting connections — helping diagnose serviceavailability issues.

Configurable Ping

Choose packet count (3, 4, 6, 10). Stats: min/avg/max latency and packet loss.

Common Port Scanner

Check 14 key ports: HTTP, HTTPS, SSH, FTP, SMTP, MySQL, PostgreSQL, and more.

Cloud-Based Check

Testing from our server — see site availability from outside, not just your local network.

Uptime Monitoring

Need constant monitoring? Create a monitor — checks every minute with notifications.

Who uses this

DevOps

availability diagnosis

Network engineers

TCP port scanning

Developers

connection debugging

SRE

basic health check

Common Mistakes

ICMP blocked = server is downMany servers block ICMP. Ping fails but site works — check ports instead.

High ping = server problemLatency depends on geography. 150ms between continents is normal, not an error.

Closed ports — cause for alarmClosed ports of unused services are good. Unnecessary open ports are a risk.

One check = sufficientNetworks are unstable. A single timeout ≠ a problem. Check multiple times or set up monitoring.

Best Practices

Combine ping and port checksPing shows host availability, ports show specific service availability. Use both.

Check from different locationsThe problem may be local. A cloud test shows the real picture.

Close unused portsEvery open port is a potential attack vector. Keep only necessary ports open.

Set up monitoringManual checks do not scale. Set up automated monitoring with notifications.

Get more with a free account

Ping check history, host availability monitoring and downtime alerts.

Learn more

Research

Open ports in 2026: 1,042 checks run by users themselves

Errors

Ports

Frequently Asked Questions

How is it different from ERR_EMPTY_RESPONSE?

ERR_EMPTY_RESPONSE — server accepted connection but sent nothing. ERR_CONNECTION_RESET — the connection was torn down by an RST packet.

How do I know if it's ISP blocking?

Try via VPN. If VPN works — ISP. If it fails everywhere — server side.

Browsers show ERR_CONNECTION_RESET or ERR_CONNECTION_ABORTED — which?

ABORTED = client cancelled (redirect/close). RESET = RST packet from the other side (server/proxy/DPI).

How do I check reachability?

Enterno Ping + Port Checker — tests TCP 443 from multiple regions + monitoring.

Try the live tool that powered this guide

Free plan — 10 monitors, checks every 5 min, no card required. Upgrade for 1-minute interval and multi-region monitoring.

Start free See pricing