Add option to change nginx config per service. #114

wimb0 · 2025-10-25T09:09:26Z

wimb0
Oct 25, 2025

Would it be possible to add extra Nginx options per service?
I am having issues hosting Nextcloud behind Wiredoor and uploading large files.
(Error 413, request body too large.)

In Nginx proxy manager I can add extra custom nginx config to the site:

# allow large file uploads
client_max_body_size 50000;
proxy_max_temp_file_size 0;
proxy_buffering off;

Would be nice to have this option as well in Wiredoor.

My issue:
Upload failed for webdav: Backup operation failed: Request to https://fqdn/remote.php/webdav/Automatic_backup_2025.10.4_2025-10-25_05.24_28002191.tar failed with code 413 and message: b'<html>\r\n<head><title>413 Request Entity Too Large</title></head>\r\n<body>\r\n<center><h1>413 Request Entity Too Large</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n'

A bit related to #19

dmesad · 2025-10-27T13:06:57Z

dmesad
Oct 27, 2025
Maintainer

Hi @wimb0,

I've added an environment variable NGINX_CLIENT_MAX_BODY_SIZE to make this configurable globally across services. That way you’ll be able to increase the upload limit.

Per-service overrides are not yet supported, but we’re planning to add this feature in the future.

To apply client_max_body_size 50000; globally, simply modify your .env file:

NGINX_CLIENT_MAX_BODY_SIZE=50000

Then recreate the wiredoor container using the latest image.

0 replies

wimb0 · 2025-10-27T13:51:28Z

wimb0
Oct 27, 2025
Author

Hi @dmesad ,

~~I just tested it, and it is working. Thanks!~~
~~Now I can upload large files to my Nextcloud instance behind Wiredoor.~~

Edit:
Still having problems. The one backup that worked was a small one 😆

This is from the wiredoor access logs:

2025/10/27 14:20:59 [error] 108#108: *399 client intended to send too large body: 8252559360 bytes, client: 123.456.789.1, server: backup.domainname.tld, request: "PUT /remote.php/webdav/Custom_backup_2025.10.4_2025-10-27_14.17_18995511.tar HTTP/1.1", host: "backup.domainname.tld"
2025/10/27 14:30:22 [error] 108#108: *802 client intended to send too large body: 457308160 bytes, client: 123.456.789.1, server: backup.domainname.tld, request: "PUT /remote.php/dav/files/myrealusername/HomeAssistantBackups/test1_2025-10-27_14.30_09790856.tar HTTP/1.1", host: "backup.domainname.tld"
2025/10/27 14:41:12 [error] 108#108: *1362 client intended to send too large body: 52433656 bytes, client: 123.456.789.1, server: backup.domainname.tld, request: "PUT /remote.php/dav/files/myrealusername/SynologyBackups/DiskStation_1.hbk/Pool/0/0/0.bucket.2 HTTP/1.1", upstream: "http://123.456.789.2:80/remote.php/dav/files/myrealusername/SynologyBackups/DiskStation_1.hbk/Pool/0/0/0.bucket.2", host: "backup.domainname.tld"
2025/10/27 14:50:26 [error] 108#108: *325 client intended to send too large body: 52433656 bytes, client: 123.456.789.1, server: backup.domainname.tld, request: "PUT /remote.php/dav/files/myrealusername/SynologyBackups/DiskStation_1.hbk/Pool/0/0/0.bucket.2 HTTP/1.1", upstream: "http://123.456.789.2:80/remote.php/dav/files/myrealusername/SynologyBackups/DiskStation_1.hbk/Pool/0/0/0.bucket.2", host: "backup.domainname.tld"

0 replies

wimb0 · 2025-10-27T14:20:36Z

wimb0
Oct 27, 2025
Author

I've looked in to the config files, and it seems the parameter is in the wrong place?
Should it not be higher up, under the server block?

location / {
    include              partials/proxy.conf;
    client_max_body_size 100G;
    set $node1service2   nextcloud;
    proxy_pass           http://$node1service2:80;

Also checked in the Nextcloud container and that is set correctly, and large uploads there work fine without Wiredoor.

Edit:

As a test I've add the client_max_body_size 100G; to /etc/nginx/nginx.conf and then it works fine.
Will also test in other locations.

1 reply

dmesad Oct 27, 2025
Maintainer

You’re right that client_max_body_size can (and often should) be defined at the server scope for a global effect.

In Wiredoor we currently render it inside each location intentionally. That lets us support finer-grained policies later (for example, different limits for an app and its API within the same server).

I agree that, for the global env-var use case, defining it once at the server level is cleaner. I’ll adjust the renderer accordingly. Thanks for your feedback!

wimb0 · 2025-10-28T08:54:44Z

wimb0
Oct 28, 2025
Author

Thanks!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Wiredoor

Add option to change nginx config per service. #114

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 4 comments 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Wiredoor

Add option to change nginx config per service. #114

Uh oh!

Uh oh!

wimb0 Oct 25, 2025

Replies: 4 comments · 1 reply

Uh oh!

dmesad Oct 27, 2025 Maintainer

Uh oh!

Uh oh!

wimb0 Oct 27, 2025 Author

Uh oh!

Uh oh!

wimb0 Oct 27, 2025 Author

Uh oh!

dmesad Oct 27, 2025 Maintainer

Uh oh!

wimb0 Oct 28, 2025 Author

wimb0
Oct 25, 2025

Replies: 4 comments 1 reply

dmesad
Oct 27, 2025
Maintainer

wimb0
Oct 27, 2025
Author

wimb0
Oct 27, 2025
Author

dmesad Oct 27, 2025
Maintainer

wimb0
Oct 28, 2025
Author