Errors / Network errors
net::ERR_EMPTY_RESPONSE
The server accepted the connection and then sent nothing back.
The request fails with nothing to show for it.
Why it happens
- The server process crashed or was killed while handling the request.
- A proxy or load balancer timed out waiting for the app behind it and closed the connection.
- A security module or firewall dropping the response.
How to fix it
- Look at the app's logs for a crash or an out-of-memory kill at that time.
- Compare the app's time to answer with the proxy's timeout.
curl -von the URL shows whether the connection closes with no status line at all, which confirms it is the server's side and not the browser's. If it happens only on some pages, look at what they do differently: a large upload, a slow report, a query that takes longer than the proxy is willing to wait.
Whose problem it is
Usually the server that answers the request.
Does your site have it?
Free, no account. We open your page and four more in a clean Chrome and list every error like this one, with the page and the click that caused it. How the free page check works.
Often seen with
- ERR_CONNECTION_RESETThe connection to the server was cut in the middle.
- 502 Bad GatewayThe server you reached works, but the application behind it did not answer properly.