What does this error tell you?
Google Chrome describes ERR_EMPTY_RESPONSE as a page that did not send data and may be unavailable. Unlike a 404 or 500, there may be no normal HTTP status at all.
First find out whether it only happens to you
- Check the same page with an external HTTP checker.
- If the check receives a normal status, compare another device or network.
- If the external request also fails, the server, proxy, CDN or application is more likely involved.
Common server-side causes
An application process may crash before sending response headers, a reverse proxy may close its connection to the origin, or the protocol may be misconfigured—for instance, using HTTPS against a port expecting plain HTTP.
If you are a visitor
Refresh once and check other sites. If only one domain fails, do not clear all browser settings. Compare without VPN or proxy and on another network.
If you manage the website
Inspect application, reverse proxy and CDN logs around the same time. Look for crashes, memory limits, timeouts, connection resets or TLS/protocol mismatches.
ERR_EMPTY_RESPONSE versus 502
A 502 is a valid HTTP response from an intermediary. ERR_EMPTY_RESPONSE means the browser did not receive a normal response.
Frequently asked questions
Does ERR_EMPTY_RESPONSE mean my internet connection is lost?
Not necessarily. Often only one website or one server route fails.
Why does an external checker help?
It distinguishes a failure also seen from another network from a problem limited to your own device.