RT, the configuration parameters are
upstream h39_server
{
server x.x.x.39;
}
...
location ~ ^/h39
{
proxy_redirect off;
proxy_pass http://h39:8080;
}
Small files are normal, large files can get the returned header, 200 is normal, and content-length is also available, but the data cannot be read and is blocked. Are there any parameters that need to be specified?
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It should be because of the buffer, just add the following configuration
First check the error log of nginx under x.x.x.39. If you have not customized the path, the error.log is located under the
/path/to/nginx_install_root/logsdirectory. Then try to solve it according to the error. If the error log is not opened, open it first.If you are not completely sure whether it is the following problem, you can give it a try. If the following error is found in the error log:
Cause of the problem
Nginx's fastcgi_temp directory has incorrect permissions, and the nginx sub-process (worker process; the master process runs under the root account, but all worker processes run under the user account according to the nginx configuration file) cannot write. I suddenly remembered that I had changed the directory permissions not long ago.
Problem Solved
The solution is simple once you know the cause. My nginx user configuration is www:www. Just change the permissions of the fastcgi_temp directory:
Has the poster solved this problem? How to deal with it