Failed to load resource: net::ERR_INCOMPLETE_CHUNKED_ENCODING

The following error may appear in Chrome’s developer console:

Failed to load resource: net::ERR_INCOMPLETE_CHUNKED_ENCODING

This message is saying that the data was cut off before it was fully sent.

The issue can cause blank pages, partially loaded pages, failed AJAX requests, a continuous spinning icon in the browser tab, truncated JavaScript files, and CSS problems.

ERR_INCOMPLETE_CHUNKED_ENCODING may be caused by your antivirus software.

Your antivirus software’s real-time defense, browser guard, and web-scanning features may be the cause of this error.

Antivirus software such as Avast, Kaspersky, and Malwarebytes will intercept and scan HTTP requests to detect malicious content.

A number of users fixed Chrome’s “ERR_INCOMPLETE_CHUNKED_ENCODING” error by disabling these features. These users reported that the issue mostly impacted HTTP requests that were being sent to a local development server (localhost).

To rule your antivirus out, you may want to temporarily disable it.

If you’re running a Linux server, make sure that your root partition isn’t full.

If you’re running a Linux server, then you may want to check how much space is left in your root partition. A number of developers experienced this error when their root petition unexpectedly became full due to large log files and other unforeseen issues.

Nginx permission issues have also caused this problem.

If you are using Nginx, make sure that Nginx is the owner of the /var/lib/nginx and /var/lib/nginx/tmp directories.

You should also ensure that the /var/lib/nginx/tmp directory is writable.

Note that the paths of your directories may be different, depending on the operating system and configuration.

This issue may also impact other web servers and proxies that are being prevented from writing files to disk.

The incorrect Nginx permissions and the full Linux root partition both cause the same problem: The web server (or proxy) can no longer save cache files. Therefore, the true cause may be the server’s inability to read or write files.

Disable your Chrome extensions.

If the solutions above didn’t work for you, then you should try disabling your Chrome extensions to see if any of them are interfering with the traffic between the server and your browser.