ERR_EMPTY_RESPONSE -324

What it means

Chrome shows 'didn't send any data'. The connection opened, the request was sent, and the server closed the connection without returning a single byte of HTTP response. On the server side it almost always means the request crashed or was killed before a response was written.

Applies to: Chrome, Edge, Brave, Opera, Vivaldi

How to fix ERR_EMPTY_RESPONSE

1. Reload the page, then try a private window to rule out extensions
2. Disable VPN, proxy and antivirus web scanning, which can swallow responses
3. Clear Chrome's cache and cookies for the site
4. Reset network caches: 'chrome://net-internals/#sockets' (Flush socket pools) and 'ipconfig /flushdns'
5. Check that you are using the right protocol: sending plain http:// to an HTTPS-only port (or the reverse) commonly produces an empty response
6. If you own the site: check PHP-FPM, Node or app server logs for segfaults, out-of-memory kills ('dmesg | grep -i kill') or worker timeouts at the time of the request
7. If you own the site: reproduce with 'curl -v http://localhost:PORT/path' on the server to see whether the backend or the proxy drops the connection

Why it happens

The server closed the socket before any status line. Typical sources are a crashing or timed-out worker process, an OOM-killed backend, protocol mismatch (HTTP sent to an HTTPS port or to a non-HTTP service), and filters that block the response.

FAQ

Related errors