ERR_CONTENT_DECODING_FAILED
ERR_CONTENT_DECODING_FAILED Error
What This Error Means
The ERR_CONTENT_DECODING_FAILED error occurs when the browser receives data from the server but cannot decode it properly. This typically happens when the server claims to be sending data compressed with Gzip or Brotli (via the `Content-Encoding` header), but the actual data body is either corrupted, incomplete, or not compressed at all.
Common Causes
- Double compression where a reverse proxy (like Nginx) compresses already-compressed content.
- The server sending a `Content-Encoding: gzip` header but delivering uncompressed plain text.
- Network packet corruption modifying the compressed data stream.
- Antivirus or firewall software interfering with the HTTP stream and corrupting the encoding.
- A PHP script crashing halfway through outputting a compressed response.
- Misconfigured CDN settings applying compression rules incorrectly.
How to Fix It (For Users)
- 1 Clear your browser cache and cookies to remove any corrupted cached versions.
- 2 Disable your antivirus or firewall temporarily to see if it is modifying traffic.
- 3 Try accessing the site in Incognito mode.
- 4 Check if the error persists across different browsers.
For Site Owners / Developers
- Check your web server configuration (Nginx/Apache) for double-compression issues.
- Ensure your application is not manually setting `Content-Encoding` headers if the server handles compression automatically.
- Verify that your backend scripts are not crashing or exiting prematurely.
- Disable Gzip/Brotli temporarily to isolate the issue.
- Inspect the raw response headers and body using `curl -v` or developer tools.
When It Is NOT Your Fault
If the website's server is misconfigured to send invalid compressed data.
Is the website actually down?
Sometimes the issue is just on your end. Check if the website is down for everyone or just you.
Check Website Status →