ERR_CONNECTION_RESET: Why It Happens and How to Fix It

Picture a phone call where the other person suddenly hangs up in the middle of a sentence. No goodbye, no explanation, just a dead line. That’s very close to what happens when Chrome shows you “This site can’t be reached – The connection was reset. ERR_CONNECTION_RESET.”

Unlike a site that never answers, this connection actually started. Your browser and the server were talking, and then something cut the line. It could be the website’s server, a firewall, your antivirus, your VPN or your own router.

That’s what makes ERR_CONNECTION_RESET tricky: the cause can be almost anywhere along the path. The good news is that it follows patterns, and you can narrow it down fast. This guide explains what the error means, what causes it, and how to fix it, whether you’re a visitor or you run the website.

Quick answer: how to fix ERR_CONNECTION_RESET

If you’re a visitor, try these in order:

  1. Reload the page and test a few other websites
  2. Try another network or device
  3. Turn off your VPN and proxy
  4. Check your antivirus and firewall (including HTTPS scanning)
  5. Disable extensions, clear the cache and try another browser
  6. Flush DNS and reset your network settings
  7. Update network drivers and check your MTU
  8. Check your hosts file, router and ISP

If you run the website or server, check these:

  1. Look at server logs for crashes and memory problems
  2. Review firewall, WAF and rate-limit rules
  3. Check SSL/TLS settings and proxy or load balancer timeouts
  4. Test your CDN and upload limits, and reproduce the error with curl

What does ERR_CONNECTION_RESET mean?

When your browser loads a website, it opens a connection to the server using TCP. If everything goes well, both sides exchange data and close the connection politely.

A connection reset happens when one side, or something sitting in between, abruptly ends that connection by sending a special packet called a TCP RST. It’s the networking version of slamming the phone down. Your browser gets that signal and reports ERR_CONNECTION_RESET.

A few things are worth knowing:

  • The connection did start, which separates this from a timeout (where nothing came back) and from a refusal (where the server said no right away).
  • The reset can come from the server, a firewall, a proxy, a security tool or your own network equipment. The browser can’t always tell you which one.
  • It’s a connection-level error, not an HTTP status code. Codes like 404 or 502 come from a web server that had a chance to reply. For those, see our HTTP errors guide.

How the error shows up in each browser

BrowserWhat you see
Chrome“This site can’t be reached. The connection was reset. ERR_CONNECTION_RESET”
Edge“Hmm… can’t reach this page. The connection was reset.”
Firefox“The connection was reset. The connection to the server was reset while the page was loading.”
Safari“Safari Can’t Open the Page. The server unexpectedly dropped the connection.”

Reset vs refused vs timed out

These three get mixed up constantly. They feel similar, but the fixes differ:

ErrorWhat happenedWhere to look first
ERR_CONNECTION_RESETThe connection started, then was cut offSecurity software, VPN, network equipment, server crashes
ERR_CONNECTION_REFUSEDThe server or firewall rejected the connection straight awayStopped web server, closed port. See our ERR_CONNECTION_REFUSED guide
ERR_CONNECTION_TIMED_OUTNobody answered before the time limitOverloaded server, dropped packets. See our ERR_CONNECTION_TIMED_OUT guide
ERR_SSL_PROTOCOL_ERRORThe secure handshake failedCertificate or protocol issue. See our SSL errors guide

The quick memory trick: refused means a door slammed shut, timed out means nobody was home, and reset means someone hung up mid-conversation.

What causes ERR_CONNECTION_RESET?

Causes on your side

  • A flaky or unstable internet connection, or weak Wi-Fi
  • A VPN or proxy that drops traffic
  • Antivirus or firewall software that scans or blocks connections, especially encrypted ones
  • Browser extensions that interfere with requests
  • Corrupted network settings or outdated network drivers
  • An MTU setting that’s too large for your connection
  • A router, ISP filter, school or workplace network blocking the site
  • Public Wi-Fi with a login page or content filter

Causes on the website’s side

  • The server crashed, restarted or ran out of memory in the middle of your request
  • A PHP or application process died while handling the page
  • A firewall, WAF or security tool cut connections it considered suspicious
  • Rate limiting or DDoS protection resetting real visitors
  • SSL/TLS settings that some browsers or devices can’t negotiate
  • A reverse proxy or load balancer with a shorter idle timeout than the server behind it
  • A CDN or proxy having trouble reaching the origin server

First, work out where the problem is

Before you change settings, run two quick checks:

  1. Try other websites. If every site gets reset, the issue is in your connection or device. If only one site fails, the cause is more likely that site or something that treats it specially.
  2. Try the same site on your phone over mobile data. If it works there, the fault is between your computer and the internet. If it fails everywhere, it’s probably the server.

Site owners who see this from every network can skip to Fix 9.

Fixes for visitors

Fix 1: Reload the page and test a few other websites

A reset is sometimes a one-off, such as a server restarting or a short network drop. Wait half a minute, reload with Ctrl+Shift+R (Cmd+Shift+R on Mac), and try again. If a handful of unrelated sites load fine, your connection is healthy and the site itself is the issue.

Fix 2: Try another network or device

Connect your computer to your phone’s hotspot, or open the site on another device.

  • Loads fine elsewhere: the problem is on your home network, your ISP, or your computer. Keep going with Fix 3 to Fix 8.
  • Fails everywhere: the website’s server or network is likely resetting connections, so you can only wait or tell the owner.

Fix 3: Turn off your VPN and proxy

A VPN or proxy is an extra link in the chain, and any weak link can drop your connection.

  • Disconnect the VPN and reload the page. If it works, try a different VPN server, or a different protocol in your VPN app.
  • On Windows, open Settings > Network & internet > Proxy and turn off any proxy you didn’t set up.
  • On Mac, go to System Settings > Network, select your connection, click Details, open Proxies and untick anything that’s enabled.

If you’re on a work or school network where a proxy is required, ask your IT team before changing it.

Fix 4: Check your antivirus and firewall

This is one of the most common causes on home computers. Many antivirus suites inspect encrypted web traffic. If their scanner has a problem with a website, or with a certain browser, it can reset the connection.

  1. Temporarily switch off your antivirus web protection or HTTPS scanning feature, then reload the page.
  2. Do the same for any third-party firewall.
  3. On Windows, also open Windows Security > Firewall & network protection and make sure your browser isn’t blocked.
  4. If the page loads, don’t leave protection off. Add an exception for the browser or website, or turn off just the HTTPS scanning option, and switch everything else back on.

Fix 5: Disable extensions, clear the cache and try another browser

Browser extensions can change or block requests. Ad blockers, privacy tools and security add-ons are the usual culprits.

  • Open the site in a private or incognito window, which turns off most extensions. If it loads, re-enable your extensions one at a time to find the one causing trouble.
  • Clear the cache: in Chrome go to Settings > Privacy and security > Delete browsing data, and tick Cached images and files.
  • Open the site in a different browser. If that works, the problem is limited to your main browser, and you can reset its settings.

If you want to experiment, Chrome has an experimental QUIC protocol setting at chrome://flags. Setting it to Disabled can help on networks that handle QUIC badly. Treat this as a test, not a permanent fix.

Fix 6: Flush DNS and reset your network settings

Corrupted network settings can cause resets that look random.

Flush DNS. On Windows, open Command Prompt as administrator:

ipconfig /flushdns

On macOS, open Terminal:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Also clear Chrome’s DNS cache by visiting chrome://net-internals/#dns and clicking Clear host cache.

Reset the Windows network stack. In an administrator Command Prompt, run these, then restart your PC:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew

Switch to a public DNS server such as Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1) if your ISP’s DNS is unreliable. If DNS problems are your main suspect, our DNS errors guide goes deeper.

Fix 7: Update network drivers and check your MTU

Update your network adapter driver. On Windows, open Device Manager, expand Network adapters, right-click your Wi-Fi or Ethernet adapter and choose Update driver. Outdated or buggy drivers can drop connections under load.

Check your MTU. MTU is the largest packet size your connection sends. If it’s set too high for your network (this can happen with some VPNs and DSL lines), large packets get dropped or reset while small ones work. That’s why some pages load and others fail.

Test on Windows with:

ping -f -l 1472 example.com

If the reply says the packet needs to be fragmented, your path can’t carry packets that large. Lower the number until the ping works, and add 28 to the working size to get your MTU. Then see your adapter names:

netsh interface ipv4 show subinterfaces

and set a lower MTU, for example:

netsh interface ipv4 set subinterface Wi-Fi mtu=1400 store=persistent

Replace Wi-Fi with your adapter’s name. If this makes no difference, you can set it back to 1500, the common default.

Fix 8: Check your hosts file, router and ISP

Hosts file. A leftover entry can point a domain to the wrong place. On Windows the file is in C:\Windows\System32\drivers\etc\hosts, and on Mac and Linux it’s /etc/hosts. Remove any line for the problem domain that you didn’t add on purpose.

Router. Restart it by unplugging for 30 seconds. Make sure its firmware is current, and check whether any parental controls, security filters or firewall features are active, since these sometimes reset connections to certain sites.

Your network. Public Wi-Fi, schools and offices often filter websites, and filters sometimes reset connections instead of showing a block page. If the site works on mobile data, that may be your answer. If it fails on every network you try, contact your ISP.

Fixes for website owners and server admins

If visitors from many networks report resets, look at your server. These steps go from the most common causes to the least.

Fix 9: Look for crashes and memory problems in your logs

If your server crashes or restarts in the middle of a request, the connection is dropped and the visitor sees a reset.

Check whether your web server and PHP processes are healthy:

sudo systemctl status nginx
sudo systemctl status php8.2-fpm
sudo journalctl -u nginx --since '1 hour ago'

Replace the PHP service name with the version you use. Then look for out-of-memory kills, which can stop processes without warning:

dmesg | grep -i 'out of memory'
free -m

Also read your web server and PHP error logs (usually in /var/log/nginx/ or /var/log/apache2/) around the time of the problem. Signs of trouble include worker processes exiting, segmentation faults, and requests that hit PHP limits.

If memory is the problem, the long-term fix is a lighter setup or a bigger server. Our Server Size Calculator can help you estimate what you need. On shared hosting you can’t read these logs directly, so open a ticket and ask your host to check for resource kills. Our web hosting errors guide covers related problems.

Fix 10: Review firewall, WAF and rate-limit rules

Security tools sometimes reset connections they think are suspicious, and they don’t always get it right.

  • Web application firewalls (ModSecurity, Cloudflare WAF, Sucuri and similar): check the event logs for blocked requests that match the time of the error. A rule may be firing on a legitimate form or API call.
  • Fail2ban, CSF and Imunify360: see whether visitors’ IP addresses have been banned, especially after repeated login attempts.
  • Rate limiting: make sure limits aren’t so tight that normal browsing, such as loading a page with many assets, triggers them.
  • DDoS protection: during attacks or traffic surges, mitigation can reset genuine users. Review what thresholds are set.

If you find a rule that’s blocking real traffic, adjust or whitelist it, then retest from an outside network.

Fix 11: Check SSL/TLS settings and proxy or load balancer timeouts

Two configuration problems cause quiet resets.

TLS compatibility. If your server only allows certain protocol versions or ciphers, some browsers and devices can’t finish the handshake, and the connection gets reset. Test it with:

openssl s_client -connect yourdomain.com:443 -servername yourdomain.com

If the command errors out or the handshake fails, review your certificate chain and TLS configuration. Free online SSL test tools can show which protocol versions and ciphers you support. See our SSL errors guide for more.

Idle timeouts. If a reverse proxy or load balancer closes idle connections sooner than the server behind it, the next request on a reused connection can arrive at a closed door and get a reset. Make sure keep-alive and idle timeouts are consistent across every layer, with the proxy’s timeout set slightly shorter or matched in a way that avoids reusing connections that have already been closed. Slow back-end responses can also show up as 504 Gateway Timeout or 502 Bad Gateway errors.

Fix 12: Test your CDN and upload limits, and reproduce the error with curl

CDN or proxy issues. If you use Cloudflare or another CDN, try bypassing it temporarily for a test, or check its logs. Resets between the CDN and your origin often come from firewall rules that block the CDN’s IP ranges. Our Cloudflare errors guide and CDN errors guide walk through that.

Upload and request size limits. On some setups, a request that’s larger than the allowed size gets its connection reset instead of a polite error. If the problem only happens when uploading files or posting large forms, check limits such as client_max_body_size in Nginx, upload_max_filesize and post_max_size in PHP, and any limits in your WAF.

Reproduce it with curl. This shows you what a client sees, without browser extras:

curl -v https://yourdomain.com

If you see a message like “connection reset by peer,” the reset is happening on the network or server. Repeat the test from another network or server to see whether the problem depends on location. For deeper debugging, a packet capture with tcpdump shows which side sends the reset, but that’s usually a job for your host or sysadmin.

What about WordPress sites?

WordPress itself rarely causes a reset, but the stack around it can. If your site resets connections only on certain actions, try these steps:

  • Deactivate security, caching and backup plugins to rule out plugin conflicts.
  • Increase the PHP memory limit and make sure the PHP version is supported.
  • Look for plugins that run heavy tasks (imports, backups, scans) that might crash PHP workers.
  • Check that your security plugin or host firewall isn’t blocking the admin or REST API.

How to prevent ERR_CONNECTION_RESET

  • Monitor uptime and resources so crashes and memory pressure show up before visitors notice.
  • Keep software updated: web server, PHP, OS and TLS libraries.
  • Test firewall and WAF changes from an outside network before relying on them.
  • Keep timeouts consistent across proxies, load balancers and servers.
  • Use a modern TLS configuration that supports current browsers and devices.
  • Plan for traffic spikes with caching, a CDN and enough server capacity.
  • Choose dependable hosting with clear logs and support that responds quickly.

Does ERR_CONNECTION_RESET affect SEO?

If it happens now and then, probably not. If search engine crawlers keep getting their connections cut, they may crawl less, and pages that fail repeatedly can drop out of the index. A frustrating experience for real visitors can also hurt engagement. After fixing the problem, check the Crawl stats and Pages reports in Google Search Console to make sure Google can reach your pages again.

Frequently asked questions

What does ERR_CONNECTION_RESET mean?

It means a connection between your browser and a website was started and then abruptly ended before the page finished loading. Something, either the server, a firewall, or a device in between, sent a signal to cut it off.

Is ERR_CONNECTION_RESET caused by my computer or the website?

Either. If the site loads on other devices and networks, the cause is on your side. If it fails everywhere, the website’s server or security setup is likely responsible.

What is the difference between ERR_CONNECTION_RESET and ERR_CONNECTION_REFUSED?

With a reset, the connection was made and then cut off. With a refused connection, the server or a firewall rejected the attempt right away. A refusal usually means a stopped service or closed port, while a reset points more to security software, network equipment or a crash mid-request.

Can a VPN cause ERR_CONNECTION_RESET?

Yes. A VPN adds extra links where connections can drop, and some websites block known VPN servers. Disconnect it or switch servers and test again.

Can antivirus software cause ERR_CONNECTION_RESET?

Yes, and it’s very common. Antivirus tools with HTTPS scanning can cut connections they can’t inspect. Turn off the web protection or HTTPS scanning feature to test, and add an exception if it solves the problem.

Why does ERR_CONNECTION_RESET only happen on one website?

Usually the site’s server, firewall or CDN is dropping the connection, or something on your network treats that site differently. Test from a different network and device to find out which.

Can a bad MTU setting cause connection resets?

It can. If your MTU is higher than your connection supports, large packets get lost, so some pages load and others don’t. Testing with a ping and lowering the MTU can fix it.

How do I fix ERR_CONNECTION_RESET on my own website?

Check your server logs for crashes and memory kills, review firewall and WAF rules, test your SSL/TLS setup, make sure proxy timeouts are consistent, and reproduce the error with curl from an outside network.

Will ERR_CONNECTION_RESET go away on its own?

Sometimes, if it was a brief server restart or network hiccup. If a firewall rule, security software setting or configuration issue is the cause, it will keep coming back until you fix it.

Does Chrome show ERR_CONNECTION_RESET more than other browsers?

The code name is specific to Chrome and other Chromium browsers like Edge. Firefox and Safari report the same problem in plainer words, but the causes and fixes are the same.

Final thoughts

ERR_CONNECTION_RESET can feel mysterious because so many things sit between your browser and a website, and any of them can pull the plug. But the troubleshooting is logical.

Work out whether the problem is local or global, then check security software, VPNs and networks if you’re a visitor, or logs, firewalls and proxy settings if you manage the site.

If you’re still stuck, a curl test, a server log and a clear note to your host will usually get you to the answer much faster.