The server accepted the connection and the request, then closed it without sending a single byte. The program that should have answered died before writing anything, or something on the server deliberately hung up — a security rule, or nginx’s “close without response” code.
This page isn’t working example.com didn’t send any data. ERR_EMPTY_RESPONSE
How 6 other clients word the same error
Chrome, when it happens during HTTPS set-up
This site can’t be reached example.com unexpectedly closed the connection. ERR_CONNECTION_CLOSED
curl
curl: (52) Empty reply from server
WordPress and PHP
cURL error 52: Empty reply from server
Node.js
Error: socket hang up
Python
('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
Java
java.net.SocketException: Unexpected end of file from server
| Error | ERR_EMPTY_RESPONSE |
| Usually fixed by | The site owner or host |
| On the network | The server closed the connection without sending a byte |
| Chrome’s code | ERR_EMPTY_RESPONSE (-324); ERR_CONNECTION_CLOSED (-100) during the HTTPS handshake |
| curl | Exit code 52 |
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
Unlike a reset, this is an orderly close — just with nothing said first. Chrome is the only browser with a page for it; Firefox shows “The connection was reset”. When the close happens while HTTPS is being set up, Chrome calls it ERR_CONNECTION_CLOSED.
Why it happens
- The application or the web server’s worker crashed after reading the request and before answering.
- A security rule that closes the connection without an answer — nginx’s return 444 does exactly that.
- A server listening on the port but not speaking HTTP there — plain HTTP sent to an HTTPS-only port, or the other way round.
- A proxy or load balancer whose backend closed the connection.
How to fix it
- Read the web server’s and the application’s error logs at the time of the request: a crash or a killed worker shows there.
- Look for rules that drop requests (return 444, a firewall, a security plugin) and check whether they catch real visitors.
- Make sure https:// goes to the HTTPS port and http:// to the plain one.
If you are visiting the site
- Reload once. If it keeps happening only for you, try another network; otherwise the site owner has to fix it.
See it for yourself
curl -v https://example.com/
curl -v http://example.com/
“Empty reply from server” after the request is sent confirms it; compare the two to see whether only one protocol is affected.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Error page strings.grdp — raw.githubusercontent.com
- Net error list.h — raw.githubusercontent.com
- libcurl — Error Codes — curl.se
- Module ngx_http_rewrite_module — nginx.org
- HTTP — Node.js v26.10.0 Documentation — nodejs.org