# Chrome DevTools: net::ERR_INCOMPLETE_CHUNKED_ENCODING 200 (OK) — response cut off midway

**Code:** `net::ERR_INCOMPLETE_CHUNKED_ENCODING` · **Category:** Browser · **Seen on:** Chrome, Edge, Nginx, PHP

The server started sending a chunked response with status 200 and then stopped before the final chunk, so Chrome reports the transfer as broken.

## Meaning

This points to the server side: a PHP/Node process crashing or timing out mid-response, a proxy buffering limit, a full disk for temp files, or output compression issues. The status shows 200 because the headers were already sent.

## Common causes

- Application crashed or hit a time/memory limit while streaming
- Proxy buffer or temp-file problem (disk full, permissions)
- gzip/brotli or output buffering conflicts
- Load balancer idle timeout shorter than the response
- Antivirus or middlebox interrupting the stream

## Quick fix

1. Check server error logs at the time of the request
2. Free disk space and fix proxy temp-dir permissions
3. Raise timeouts or stop streaming huge responses through a proxy

## Detailed fix by platform

### Nginx

1. Look for "upstream prematurely closed" / "no space left on device"; check `proxy_temp_path` permissions and `df -h`; raise `proxy_read_timeout`

### Linux

1. `curl -v --raw https://example.com/page -o /dev/null` shows whether the chunked stream ends properly

### PHP

1. Check `error_log` for fatal errors and `max_execution_time`, `memory_limit`

## How to diagnose

1. **Logs** — Crash or timeout in the server log?
2. **Disk** — Free space and temp directory writable?
3. **Proxy** — Direct to origin works?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/browser/err-incomplete-chunked-encoding)