• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue After PPPM-15094 - client_max_body_size set to 1MB

mvais

Basic Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
18.0.72 Update 2
Hi All

After the installation of Plesk Obsidian 18.0.72 Update 2 (PPPM-15094) (https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18072-mu2):
  • Nginx uses the default value of 1MB for client_max_body_size
  • Changing the Nginx setting Maximum allowed HTTP request body size has no impact anymore
/var/log/nginx/error.log lists following entries

2025/09/15 15:49:45 [error] 682685#0: *37903 client intended to send too large body: 3529036 bytes, client: 100.100.100.100, server: , request: "POST /admin/asset/add-asset?parentId=1&dir=&allowOverwrite=0 HTTP/2.0", host: "xyz.com", referrer: ".xyz Domain Names | Join Generation XYZ"

So we had to manually add client_max_body_size to /etc/nginx.conf or /etc/nginx/plesk.conf.d/server.conf (IP Section).

We think, the following change in PPPM-15094 in server.conf is responsible for this: proxy_set_header Host $ip_default_host;

Are we missing something?

Best,
Markus
 
Hello, yes, PPPM-15094 introduced those changes (proxy_set_header Host $ip_default_host;) in the nginx configs. But it's unclear for me what problem do you have?
 
The Problem is:
  • Nginx uses new the default value of 1MB for client_max_body_size / so setting the client_max_body_size in nginx additional directives has no impact anymore
  • Changing the Nginx setting Maximum allowed HTTP request body size in panel to for example 512MB has no impact anymore
 
Hello, Markus. I attempted to reproduce the issue by updating a test Ubuntu 22.04 server from 18.0.69 to the latest Plesk build, but was unable to replicate the behavior (during file uploads). Thus, I wouldn't say the issue results from the PPPM-15094 fix. However, it might still be plausible under specific conditions on the server in question.
I would suggest opening a ticket with Plesk support for further investigation on your server. To sign-in and open a ticket please go to:
If you got your license from a reseller, your reseller is in charge of providing you with support. You can raise the inquiry with them and they can forward it to our team for further processing.
If the reseller does not provide support, here is an alternative to get support directly from Plesk:
 
Back
Top