How to setup up 'client_max_body_size' in this proxy? (upload large files)

[cod3r0k]

Error description:

gitlab error 413 (big file can't be uploaded). How can we setup nginx to upload large file?

[evertramos]

might be... enable the nginx conf and set your max file upload. make sure you have the same settings in your local application set up.

[gustawdaniel]

This is third issue in this topic:

#207
#81

I have this problem too some times. We should add chapter in documentation that explains possible
solutions and best practices of solving this problem.

[evertramos]

Thanks @gustawdaniel for your suggestion! Let's see if we make this clear and help others.

This proxy allows you to set 'client_max_body_size' in couple ways.

1. Use $ ./fresh-start.sh with `--use-nginx-conf-files' argument

This way you will have 100m allowed as of uploadsize.conf

2. If you already have the proxy running add this file to ./data/conf.d folder.

3. You can set this option per site as of nginx-proxy doc

• Per-host
• Per-host location

Adding this setting per site you must use the site (url) name as mentioned in this sample as well.

You can set client_max_body_size at multiple context as of nginx docs, you can use it per location if you with to or at vhost (http) level.

So, if your url is _my-very-own-domain.com, and you intend to use at host level you create a file named my-very-own-domain.com at your './data/vhost.d' path, you may find the right path at NGINX_FILES_PATH variable at .env file.

Your file will look like:

client_max_body_size 1024m;

Then you must stop your site container (example the nextcloud) and start again, so the nginx-proxy will update the options or if you can not stop it, you can reload nginx options using the following:

$ docker exec -it [YOUR_NGINX_PROXY_CONTAINER_NAME] nginx -s reload

Please let me know if this was useful.

Thanks!

[Pyroseza]

Thanks for showing me this discussion Evert, apologies for raising the issue earlier

[evertramos]

I just replied, right after your issue @Pyroseza, so thank you for raising up this subject again so I could stop and answer it the right way!

[ivanhercaz]

Hi @evertramos! First of all, thank you very much for your awesome work with nginx-proxy-automation. I am having a similar issue but I don't if you prefer that I open a new thread or to expose my problem here so, what do you prefer?

And yes, I tried to reproduce the same steps, but it works with one domain and not with another one.