• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue 413 Request Entity Too Large after changing client_max_body_size

Anbosuki

New Pleskian
Server operating system version
Ubuntu 22.04.1 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.44 Update #1
Hello, I am running a docker-compose project with python as codebase on a Ubuntu (22) Plesk (18.0.44) server. Now I have a problem that I cannot upload a file with ~1.1GB of size. I changed the value of `Maximum allowed HTTP request body size` under `Domain > my.domain > Hosting & DNS > Apache & nginx Setting` to `2048M` (which then got converted to 2GB). Which worked fine at first, because without that change I instantly got the response that my request is too large (directly from nginx). But after waiting for the file to upload in the end I got basically the same error like the following:
```
Request Entity Too Large

exceeds max_body of 1073741824

(generated by waitress)
```
I don't know where that value comes from. When I check the log of my container I just see the following:
```
[warn] 10#10: *72 a client request body is buffered to a temporary file /var/cache/nginx/client_temp/0000000001, client: *.*.*.*, server: , request: "POST /api/uploads HTTP/1.0", host: "my.domain", referrer: "https://my.domain/upload"
[error] 10#10: *72 readv() failed (104: Connection reset by peer) while reading upstream, client: *.*.*.*, server: , request: "POST /api/uploads HTTP/1.0", upstream: "http://*.*.*.*:6666/uploads", host: "my.domain", referrer: "https://my.domain/upload"
```

Can anyone help me solve this problem?

Thanks for any help in advance :)
 
What is listening upstream? You have to configure that too.
If it's PHP, then in the PHP settings.
E.g.:
1671642731145.png
 
Hello, thank you for the reply.
Since it's python I actually completely deactivated php for my website. So that's not the problem.
I am not sure, but I think the problem has something to do with my docker nginx config. I now get the error:
Request Entity Too Large
exceeds max_body of 1073741824
(generated by waitress)
 
Back
Top