How to Solve Chrome Error: “net::ERR_INCOMPLETE_CHUNKED_ENCODING”

Remember the process of troubleshooting. Premise to build a publishing system, colleagues suddenly appear in the use of the page whiteboard, the page can not render any content. Of course, the first reaction is that there may be something wrong with the diff module

Print the CMD of diff module and check the return without any problem. At the last step of the template, there is something wrong with the output. Strange heart 10000 question mark, again did not encounter this problem, change a browser. No problem! There is really no problem

Chrome Open debug mode, failed error code (failed) net:: err_ INCOMPLETE_ CHUNKED_ ENCODING。 Then Google got the results. Actually, it’s a very common problem. When the output proxy file size exceeds the configured proxy file size_ temp_ file_ write_ Size, nginx will write the file to the temporary directory. If you don’t have permission, chrome will fail without outputting anything

Specific error:

/var/lib/nginx/tmp/fastcgi/2/37/0000000372" failed (13: Permission denied) while reading upstream, client:, server:, request: "GET /walle/deploy?taskId=147 HTTP/1.1", upstream: "fastcgi://", host: ""


chown -R www:www /var/lib/nginx

WWW is replaced by the ngxin running user configured in the actual project

This problem review is when installing nginx, you can directly Yum install. When configuring the web, I forgot to change the directory permissions of/var/lib/nginx. The default is nginx:nginx Group permissions, usually do not use this account to start. So when it comes to a body with large output, this et:: err is triggered_ INCOMPLETE_ CHUNKED_ Encoding error

Similar Posts: