ERR_EMPTY_RESPONSE
Chrome connected to the server and sent the request, but got zero bytes back before the connection closed.
Quick checks
- Reload, then try a private window.
- Try another network and turn off VPNs.
- Check whether other people can open the site.
Fixes on Mac
Clear Chrome's sockets and cache
- Flush
chrome://net-internals/#sockets, then delete cached files in Chrome's privacy settings.
- Flush
Remove proxies and filters
- Turn off unused proxies in System Settings › Network › Details › Proxies; pause content filters and VPNs.
Fixes on Windows
Reset the network
ipconfig /flushdns,netsh winsock reset, restart.
Other devices
Router
- Restart the router; check its content filtering.
Still not working?
Site owners: an empty response usually means the process handling the request died or closed the socket without writing (an uncaught exception before headers, a PHP segfault, a proxy pointing at a non-HTTP port). Check the app's crash logs and test with curl -v: Empty reply from server confirms it.
See what’s happening
For local servers, LightAtom's Ports view shows which app owns the port you're connecting to, in case it isn't the server you expect.
Frequently asked questions
What does ERR_EMPTY_RESPONSE mean?
The server closed the connection without sending any data, not even an error page.
What does curl's “Empty reply from server” mean?
The same thing seen from the command line: the connection closed with no HTTP response. The server crashed on the request or something closed the connection.
Can my browser cause ERR_EMPTY_RESPONSE?
Rarely: corrupted cache or an extension. More often a VPN, proxy or the server itself.