Nextcloud version: 28.0.2
Operating system and version: Debian 12
Apache or nginx version: Nginx reverse proxy, Apache on the backend
PHP version: php-fpm 8.2
The file is being chunked, and upon receiving the last chunks an unexpected error shows up, leaving undeleted profile subfolder like %username%/uploads/web-file-upload-add6d25a9969d801/.
The NC desktop app syncs the same file without any issue. Nothing wrong is left in the Nginx backend or reverse proxy logs, so it looks like pure webclient bug. The only error is being thrown into nextcloud log upon the transaction failure:
"Exception": "Sabre\\DAV\\Exception\\NotFound",
"Message": "File with name //web-file-upload-add6d25a9969d801 could not be located",
That error suggests the path is getting lost somewhere. That’s really weird.
I can’t reproduce this (tested uploading a 6 GiB file in chunked mode w/o any problem with v28.0.2 FPM/Nginx).
Can you reproduce it with the official Nginx config example in the Admin Manual[1]?
The Nginx configs in (and linked from) that tutorial have an oddly flattened formatting. That’s weird and I have no idea why. Unrelated, but it does make analyzing much more challenging.
Upd: things are even worse, the issue exist even with apache2 backend. Chunks uploading just drops. I’m not sure this could be TMP proxy size issue, since this is a 10mb chunks transfers…
Yes, Nginx reverse proxy for HTTPS, but I see nothing wrong with its config https://pastebin.com/y6jUphB8. No glues in the proxy config, it just passthrough the chunks without any errors. I don’t understand why the desktop client transfers just fine on the same configuration.
I’ve stepped back to an old Apache backend config until the issue is understood, it certainly worked some time ago with the same proxy.