Hello,
I met a trouble with the size of my request. I have tried to send 14 pictures in my request so the body_size was superior to 1.5 Mb, I got “413 Entity too large”. So I followed instructions I found here and increased the client_max_body_size to 10 Mb in nginx.conf https://datanextsolutions.com/blog/how-to-fix-nginx-413-request-entity-too-large-error/
Now the problem is not fixed, I dont meet 413 anymore but now I meet “502 Bad Gateway” and a part of my request is readed (10 / 14 pictures are correctly uploaded and I made a lot of test, the problem doesn’t come from the image)
When I run “sudo tail -F /var/log/nginx/error.log” I can see “upstream prematurely closed connection while reading response header from upstream”
It is really strange because when I run the application in virtual environment on server The request is correctly launched and the 14 images are uplaoded.
Notice that I already investigate the timeout response and added this in nginx/sites-enabled
include proxy_params;
proxy_pass http://unix:/run/gunicorn.sock;
proxy_read_timeout 300s;
proxy_connect_timeout 75s;
Thanks for reading
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hello,
In addition to what has already been mentioned, I would recommend following these steps in case that you are having any problems with your nginx server and you are unsure on what the problem is:
If nginx is running you should see something like this:
If nginx is not running then the output would look like this:
Then check the status agian and make sure that nginx remains running.
If you get an error, you would need to fix that problem and then you could restart nginx:
Syntax OK
when runningnginx -t
then your confiruation is correct, so I would recommend checking your error logs:Find the user that your nginx service is running as:
If you are using Ubuntu, the user should be
www-data
, so you would need to make sure that your files and folders are owned by that user, so nginx could read and write to those files:ufw
allows TCP connections on port 80 and 443:If this is the case, you can follow the steps from this article here on how to configure your
ufw
:https://www.digitalocean.com/community/tutorials/how-to-set-up-a-firewall-with-ufw-on-ubuntu-18-04
That is pretty much it, with all of the above information you should be able to narrow down the problem.
For more information I would suggest checking out this article here:
https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-site-issues-on-a-linux-server
And here is also a quick video demo on how to do that as well:
Hope that this helps! Regards, Bobby Source: How to Troubleshoot Common Nginx Issues on Linux Server?