ERR_EMPTY_RESPONSE
The server didn't send any data
Seen in Chrome, Edge ("didn't send any data")
The connection was accepted but closed without any HTTP response.
Common causes
- The application or worker process crashed or was killed while handling the request.
- A plain HTTP request was sent to a port that expects HTTPS (or the reverse), so the server dropped it.
- A proxy, load balancer or firewall closed the connection after a timeout.
How to fix it
- Check the application and web server error logs for crashes, out-of-memory kills or timeouts.
- Make sure the URL scheme matches the port (https:// for TLS ports).
- Reproduce with "curl -v" to see where the connection ends.
Got a different message? Paste it into the error explainer.
Related errors
- ERR_TOO_MANY_REDIRECTS · The page redirects in a loop
- ERR_CONNECTION_CLOSED · The server closed the connection unexpectedly
- 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