Files > 1GB can be copied via davfs2 from filsystem to Nextcloud but where deleted ca. 10 seconds later

[Mornsgrans]

@CheckSP2NC

BadRequestExpected filesize of 1292938359 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.

Maybe that is the solution:

Error "Bad Request: Expected File Size..."

Hey, currently I setup my own Nextcloud (self-hosted). But when uploading large files > 500 MB, I receive this error: BadRequest Expected filesize of 2708731595 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side. I’m aware there are many other people dealing with the same issue, but yet I couldn’t find a solution in those topics. Occourance: I start …

Annother possible solution:

BadRequest Expected filesize of x bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) y bytes

@pitsinis I ran into the same problem. My setup also uses Traefik with Docker containers, and I discovered that the issue started with Traefik version 2.11.2. Its default respondingTimeouts now set the readTimeout to 60 seconds. I fixed it by adding these lines to my compose: services: traefik: command: - --entrypoints.web.transport.respondingTimeouts.readTimeout=0 - --entrypoints.websecure.transport.respondingTimeouts.readTimeout=0 For reference, see the Traefik migration …

(Google search for “BadRequestExpected filesize of bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 0 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side.”