Nextcloud hub 9 not uploading large documents

I think I have a common issue with Nextcloud, but every online resource found so far is not working with my issue.

I’am currently running Nextcloud AIO Hub 9 (30.0.4) installed with docker and using caddy and Tailscale as reverse proxy, as shown in this guide.
https://github.com/nextcloud/all-in-one/discussions/5439
where I used the same compose.yml as in the guide, just changing the necessary fields.

Nextcloud Server version:

  • Nextcloud Hub 9 (30.0.4)
    Operating system and version:
  • Ubuntu 24.04.1 LTS

Whenever I try to upload a large number of file or a big file, the upload process takes forever (while I have 100 Mb/s at least). But this is not the biggest problem, if I try to upload a large file/files then the upload fails and the logs shows:

[no app in context] Error: Expected filesize of 10485760 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 1245184 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.
	PUT /remote.php/dav/uploads/admin/web-file-upload-b730e2cb6ab0e1bd/25
	from 127.0.0.1 by admin at Jan 17, 2025, 1:13:31 PM

Any help? Thank you

Perhaps try to eliminate some variables? i.e. Tailscale

Any errors on your NIC at the host OS level and/or the port it is attached to?

Using docker compose logs the only error messages I obtain are given by caddy:

caddy-1                        | {"level":"error","ts":1737112608.5816166,"logger":"http.handlers.reverse_proxy","msg":"reading from backend","error":"unexpected EOF"}
caddy-1                        | {"level":"error","ts":1737112608.5817268,"logger":"http.handlers.reverse_proxy","msg":"aborting with incomplete response","upstream":"nextcloud-aio-apache:11000","duration":0.098504842,"request":{"remote_ip":"127.0.0.1","remote_port":"49400","client_ip":"127.0.0.1","proto":"HTTP/3.0","method":"PUT","host":"nextcloud-server.taildf8f8f.ts.net","uri":"/remote.php/dav/files/admin/Photos/Lorenzo%20Backup/e3311af8-26e2-4b81-a545-0260901364af.jpg","headers":{"Content-Length":["190508"],"Upload-Draft-Interop-Version":["5"],"Upload-Complete":["?1"],"X-Oc-Mtime":["1736712271.0631418"],"Accept-Language":["it-IT,it;q=0.9"],"Content-Type":["application/octet-stream"],"Priority":["u=3, i"],"X-Oc-Ctime":["1736691482.0"],"X-Forwarded-For":["127.0.0.1"],"X-Forwarded-Proto":["https"],"Authorization":["REDACTED"],"Accept-Encoding":["gzip, deflate, br"],"User-Agent":["Mozilla/5.0 (iOS) Nextcloud-iOS/6.2.2"],"Cookie":["REDACTED"],"Accept":["*/*"],"X-Forwarded-Host":["nextcloud-server.taildf8f8f.ts.net"]},"tls":{"resumed":false,"version":772,"cipher_suite":4865,"proto":"h3","server_name":"nextcloud-server.taildf8f8f.ts.net"}},"error":"reading: unexpected EOF"}

it seems that somewhere in transit the file gets truncated. you probably have to check the related settings (upload filesizes etc.) of all components involved.
If you haven’t actively modified any system’s network parameters i think it’s quite unlikely that the hardware (NIC) is at fault - you could do a first check with ifconfig
Also i’m wondering if http3 is really ready for production use? (I remember it took the squid devs quite a big effort to support H2 in a stable way).

GOOD LUCK!