ERR_CONNECTION_CLOSED
The server closed the connection unexpectedly
Seen in Chrome, Edge ("unexpectedly closed the connection")
The connection opened but was closed before a response arrived, so the browser had nothing to show.
Common causes
- A firewall, content filter or ISP block closed the connection.
- VPN, proxy or antivirus software interfered with the request.
- The server or reverse proxy closed the connection, for example during a TLS handshake it could not complete.
How to fix it
- Test on another network and with VPN or proxy turned off.
- Check the server and reverse proxy error logs while reproducing the request.
- Check TLS is configured for this hostname on the server.
Got a different message? Paste it into the error explainer.
Related errors
- ERR_TOO_MANY_REDIRECTS · The page redirects in a loop
- ERR_EMPTY_RESPONSE · The server didn't send any data
- ERR_HTTP2_PROTOCOL_ERROR · The HTTP/2 response was malformed or cut short
- ERR_QUIC_PROTOCOL_ERROR · The HTTP/3 (QUIC) connection failed
- NET::ERR_CERT_DATE_INVALID · The certificate has expired or is not yet valid
- NET::ERR_CERT_AUTHORITY_INVALID · The certificate isn't issued by a trusted authority
- SEC_ERROR_UNKNOWN_ISSUER · Firefox doesn't recognise the certificate's issuer
- NET::ERR_CERT_COMMON_NAME_INVALID · The certificate doesn't cover this name
- ERR_SSL_PROTOCOL_ERROR · The secure connection failed during the handshake
- ERR_SSL_VERSION_OR_CIPHER_MISMATCH · No TLS version or cipher in common
- You cannot visit this site right now because the website uses HSTS · HSTS blocks the bypass of a certificate error
- NET::ERR_CERT_REVOKED · The certificate has been revoked by its issuer