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

**Code:** `ERR_EMPTY_RESPONSE` · **Category:** Browser · **Seen on:** Chrome, Edge, Nginx, Apache

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

## 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?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/browser/err-empty-response)