Opens in a new tab

ERR_CONNECTION_RESET: “The connection was reset”

The connection was made, then cut: something sent a reset in the middle of it. The server’s software may have crashed or restarted, or something in between — a firewall, antivirus inspecting HTTPS, a VPN or proxy — decided to end it. Whether it happens everywhere or only for you tells you which.

This site can’t be reached
The connection was reset.
ERR_CONNECTION_RESET
How 7 other clients word the same error

Firefox

The connection was reset
The connection to the server was reset while the page was loading.

Firefox, interrupted

The connection to example.com was interrupted while the page was loading.

curl on Linux

curl: (56) Recv failure: Connection reset by peer

curl on Windows, and PHP

cURL error 56: Recv failure: Connection was reset

Node.js

Error: read ECONNRESET

Python on Windows

ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host')

Java

java.net.SocketException: Connection reset
ErrorERR_CONNECTION_RESET
Usually fixed byEither side
On the networkA reset (RST) in the middle of an open connection
Chrome’s codeERR_CONNECTION_RESET (-101)
curlExit code 56

Check the site from outside

Enter the address: we load it from our network and show the status code, how long it took, and the error if it failed.

What it means

A reset ends a connection immediately, without the usual goodbye. The server sends one when the program holding the connection dies or closes it abruptly; a firewall, antivirus, proxy or VPN in between can send one to cut a connection it does not like. The browser cannot tell which, so it reports the reset.

Firefox up to version 157 shows a reset on an https:// site under the title “Secure Connection Failed”, with this text underneath.

Why it happens

  • The server’s software crashed or restarted mid-request — a PHP process killed, a web server reloading.
  • A firewall or intrusion-prevention system on either side cutting the connection.
  • Antivirus or security software that inspects HTTPS on the visitor’s computer.
  • A VPN or proxy dropping the connection, or a network with an MTU problem.

How to fix it

  1. Check the site from outside with the check above: reset there too points at the server.
  2. On the server, read the web server’s and PHP’s error logs at the time: a crash or a killed process shows there.
  3. Check the server’s firewall or intrusion prevention for blocks on the visitor’s address.

If you are visiting the site

  • Try another browser, then another network. If both work, something on your device is cutting the connection: turn off HTTPS scanning in your antivirus, or the VPN or proxy, to test.
  • Reset Chrome’s proxy settings if they were changed: Settings → System → Open your computer’s proxy settings.

See it for yourself

curl -v https://example.com/

Shows how far the connection got before it was reset — during the TLS handshake points at HTTPS inspection or the server’s TLS set-up; after the request was sent, at the server’s software.

Sources

Error text and meaning checked on 25 September 2026 against these official sources:

Know when your site goes down — before your visitors do

Add your site and we check it every few minutes, confirm a failure from another location — Europe, North America or Asia — before calling it down, and email you when it stops answering and when it is back. Free for two sites.

Create a free account