ERR_EMPTY_RESPONSE Browser Origin: On your device Last updated 15 Oct 2026

Chrome: This page isn’t working — example.com didn’t send any data. ERR_EMPTY_RESPONSE

The server accepted the connection but closed it without sending any HTTP response — a crash, timeout or misconfigured proxy on the server side.

Exact message you may see didn’t send any dataThe server didn't send any data
Explore the map of this error Full error map →
Seen on: Chrome Edge Nginx Apache

Meaning

Unlike a timeout, the connection worked; the server just hung up. For site owners this points to a web-server or PHP-FPM process crashing, a reverse proxy rejecting the request, an upstream that closed early, or a firewall dropping the reply. For visitors it is usually a server problem, but VPNs and antivirus can cause it too.

Common causes

  • Web server or application process crashed or was killed (out of memory)
  • Reverse proxy or load balancer closing the connection
  • Firewall/WAF resetting the reply
  • Huge request or header closed by the server limit
  • HTTP and HTTPS mismatch on a port

⚡ Quick fix

  1. Visitors: try again later, another network, or without VPN/antivirus web shield
  2. Owners: check the web server, PHP-FPM and proxy error logs at that time
  3. Confirm the port speaks the protocol you used (http vs https)

Detailed fix by platform

Linux

  1. Look for crashes: sudo journalctl -u nginx -u php8.2-fpm --since "10 min ago" and dmesg | grep -i -E "killed process|oom"
  2. Test directly: curl -v https://example.com/

Nginx

  1. In error.log look for "upstream prematurely closed connection" and raise proxy_read_timeout or fix the crashing upstream

How to diagnose

  1. Scope — Everyone or only some networks?
  2. Logs — Server errors at that exact time?
  3. Proxy — Does the origin answer directly?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: On your device. Errors that are often confused with or caused by this one (click to open):

444 — Nginx 444 No Response (connection closed without response) (HTTP)444502 — HTTP 502 Bad Gateway (HTTP)502captive portal — Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites (Browser)captive portalERR_CONNECTION_CLOSED — Chrome: This site can’t be reached — example.com unexpectedly closed the connection. ERR_CONNECTION_CLOSED (Browser)ERR_CONNECTION_CLOSEDERR_CONNECTION_RESET — ERR_CONNECTION_RESET: This site can’t be reached — The connection was reset (Browser)ERR_CONNECTION_RESETERR_CONTENT_DECODING_FAILED — Chrome: This page isn’t working — sent an invalid response. ERR_CONTENT_DECODING_FAILED (Browser)ERR_CONTENT_DECODING_…ERR_HTTP2_PROTOCOL_ERROR — Chrome: This page isn’t working — example.com is unable to handle this request. ERR_HTTP2_PROTOCOL_ERROR (Browser)ERR_HTTP2_PROTOCOL_ER…ERR_TOO_MANY_REDIRECTS — Chrome: This page isn’t working — example.com redirected you too many times. ERR_TOO_MANY_REDIRECTS (Browser)ERR_TOO_MANY_REDIRECTSERR_EMPTY…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.