nginx-proxy-manager: 413 Request Entity Too Large
Checklist
-
Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image? Yes -
Are you sure you’re not using someone else’s docker image? Yes
-
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? Yes, but not related
Describe the bug
File uploads trigger 413 Request Entity Too Large
Setting the advanced config client_max_body_size 100m; takes no effect and the problem persists
To Reproduce Steps to reproduce the behavior:
- Upload a larger file on a website going thru the proxy, 413
- Set an appropriate
client_max_body_size - try to upload again
- See a 413
Expected behavior
client_max_body_size would take effect and allow the upload as it does with regular nginx
Screenshots If applicable, add screenshots to help explain your problem.
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 8
- Comments: 36
At the Edit Proxy Host window, click Custom locations and click the gear button, set the following attributes to an appropriate value
it works, when set the
advancedtabHey, I also have that issue. In my case I’m trying to proxy Immich (https://github.com/immich-app/immich) through NPM. If I adjust the custom config as following: “client_max_body_size 0;” I get an error code 500 after uploading ~1.5G I also tried “client_max_body_size 100000m;” and added “proxy_max_temp_file_size 100000m;” too. The same error occurs.
The error is shown in Immich as following:
With no custom config I’m getting this error:

It works!
I pushed a giant (13GiB) docker container image to harbor via nginxproxymanager as a reverse proxy service. I did it.
Worked for me. I realised I had another proxy server in front of NPM. So I updated the
client_max_body_sizefor that server too