TUS / Chunking seems to not work (at least if behind cloudflare) - can't upload files >100mb

[bahmrockk]

Hello,

If I can provide any more helpful information let me know, I'll happily do any test.

Actual Behavior
With a default server installation, the android client tries to upload files in a single upload, obeying a "filesBigChunking" variable instead of tus_support information.

Expected Behavior
Chunk my files :-)

Environment

OpenCloud Server Version: 4.1.0,
self-hosted, defaults from the reference compose w/o extra features. Behind nginx proxy manager and cloudflare. The latter is the "proof of the issue".

Android App Version: 1.0.0

Details

When uploading files that are larger than.
The android log is unbelievable large even when running only the seconds for the failed upload. The interesting things from what I can telll are>

filesBigFileChunking=FALSE

but the server sends>

"tus_support": {
  "version": "1.0.0",
  "resumable": "1.0.0",
  "extension": "creation,creation-with-upload",
  "max_chunk_size": 10000000,
  "http_method_override": ""
}

The android app still says>
D: 2025-12-20 08:18:48:568(UploadFileFromFileSystemWorker.kt:233)
Chunking is allowed: false, and file size is greater than the minimum chunk size: true

So it seems to use a bool that I don't know how to change instead of the tus_support variables. This leads to a single upload event which then returns 413 from cloudflare as it exceeds its 100MB limit.

[divinitas-art]

I just tried and 100MB+ file trully doesnt get uploaded when I am behind cloudflare tunnel and uploading from android app -

Is this somethign I can somehow enable? I see the android app should have TUS support, so why would it fail to upload bigger files if it should do it chunk by chunk? Am I missing something here? Is TUS protocol working somehow differently from what i thought?

Edit: I debugged a little more and it kinda looks like android app is not using TUS? It simply uses PUT without any attempt to chunk anything...

Is this known behaviour? Should I attempt debugging the app itself and why its deciding on not using TUS, or does anybody know about this?

[Narrat]

I may be missing some finer point and additionally I am by no means involved/familiar with the source code. Just following the development itself a bit. But it looks to me there are some things mixed?
Looking at the commit history, TUS support was only added after the 1.0.0 release. So it should probably more accurately be specified which versions and builds were tested. Did you create a debug build from 1.0.0 or from main, @divinitas-art? If the latter, then it would be no surprise why TUS is available and working but not with 1.0.0.

With 1.0.0 there should only be the (basic) chunking available. Which may not work with cloudflare tunnels. But this issue seems to be fixed with TUS and demonstrated with a testbuild from main (if the debug build was made from main). So it should be resolved with the next release.

[divinitas-art]

I may be missing some finer point and additionally I am by no means involved/familiar with the source code. Just following the development itself a bit. But it looks to me there are some things mixed? Looking at the commit history, TUS support was only added after the 1.0.0 release. So it should probably more accurately be specified which versions and builds were tested. Did you create a debug build from 1.0.0 or from main, @divinitas-art? If the latter, then it would be no surprise why TUS is available and working but not with 1.0.0.

With 1.0.0 there should only be the (basic) chunking available. Which may not work with cloudflare tunnels. But this issue seems to be fixed with TUS and demonstrated with a testbuild from main (if the debug build was made from main). So it should be resolved with the next release.

damn, I totally missed that the changes were not released yet... okay great, thank you!