By arnaud9
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
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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:
- Check if nginx is running:
systemctl status nginx
If nginx is running you should see something like this:
● nginx.service - The nginx HTTP Server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2019-11-19 09:37:46 UTC; 2 days ago
Docs: https://httpd.nginx.org/docs/2.4/
If nginx is not running then the output would look like this:
● nginx.service - The nginx HTTP Server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Fri 2019-11-22 08:41:01 UTC; 39s ago
Docs: https://httpd.nginx.org/docs/2.4/
- If nginx is not running you could start it with:
systemctl start nginx
Then check the status agian and make sure that nginx remains running.
- If nginx did not start after a reboot, you could enable it so that it starts after the next reboot:
systemctl enable nginx
- Check your nginx config syntax:
nginx -t
If you get an error, you would need to fix that problem and then you could restart nginx:
systemctl restart nginx
- If you get
Syntax OKwhen runningnginx -tthen your confiruation is correct, so I would recommend checking your error logs:
tail -f /var/log/nginx/error.log
- Check the permissions of the files and folders in your document root:
Find the user that your nginx service is running as:
ps auxf | grep nginx
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:
chown -R www-data:www-data /var/www/yourdomain.com
- Check if nginx is binding to the default ports:
netstat -plant | grep '80\|443'
- Check if
ufwallows TCP connections on port 80 and 443:
ufw status
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:
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?
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
