Comment 1 for bug 1801866

Looks like an issue from nginx. The related setting is:

As far i can see this value isn't set at all in our nginx configuration, so the default of 1m applies.

https://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size

Was that a .png file? In case of yes, it should be considered to converting into jpeg. Having 10 Images with size of 2MB will result in serving 20MB from the server, which results in a lot of bandwidth i think.

We have enough disk space:

Current Server free disk space: 70G from 100G
Current server disk used inodes: 33%

Not sure if we should allow 2M.