net::ERR_INCOMPLETE_CHUNKED_ENCODING Browser Origin: On your device Last updated 15 Oct 2026

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

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

Exact message you may see net::ERR_INCOMPLETE_CHUNKED_ENCODING 200incomplete chunked encoding
Explore the map of this error Full error map →
Seen on: Chrome Edge Nginx PHP

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?

🔧 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):

502 — 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 portalDNS_PROBE_FINISHED_NO_INTERNET — Chrome: No internet — DNS_PROBE_FINISHED_NO_INTERNET (DNS probe finished, no internet) (Browser)DNS_PROBE_FINISHED_NO…DNS_PROBE_FINISHED_NXDOMAIN — Chrome: This site can’t be reached — server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN (Browser)DNS_PROBE_FINISHED_NX…ERR_CONTENT_DECODING_FAILED — Chrome: This page isn’t working — sent an invalid response. ERR_CONTENT_DECODING_FAILED (Browser)ERR_CONTENT_DECODING_…ERR_EMPTY_RESPONSE — Chrome: This page isn’t working — example.com didn’t send any data. ERR_EMPTY_RESPONSE (Browser)ERR_EMPTY_RESPONSEERR_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…Maximum execution time — PHP Fatal error: Maximum execution time of 30 seconds exceeded (PHP)Maximum execution timenet::ERR_…

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.