Seafile 13 docker syncing big file using Android app fails

Seafile Server
,
1

When trying to sync big files > 2GB using the Android seafile app (3.0.19) to a seafile instance 13.0.12 the upload fails. The Android app shows:
Upload failed
Internal Server Error

Interestingly syncing images with the same device works fine, just big files fail.

seafhttp.access.log:
“POST /seafhttp/upload-api/9d4575c1-f19a-4586-9c13-3c9bdeeeebef HTTP/1.1” 400 0 “-” “Seafile Android/3.0” 60.000

seafhttp.error.log:
nothing

seahub.access.log:
“GET /api/v2.1/repos/ HTTP/1.1” 200 444 “-” “okhttp/4.12.0” 0.028
“GET /api2/repos/3023272e-e3a5-4c78-a036-66262059ee1b/dir/?t=f&recursive=1&p=%2FSignalbackup%2F HTTP/1.1” 200 350 “-” “okhttp/4.12.0” 0.025
“GET /api/v2.1/repos/ HTTP/1.1” 200 444 “-” “okhttp/4.12.0” 0.103

seahub.error.log:
nothing

Could you please guide me how to proceed to figure out what goes wrong?

Gruesse
Michael

Large file upload fails (>10GB) with HTTP 500 - no error in logs
2

I forgot to mention - syncing using the linux client works nicely - also with huge files…

3

So no single hint - how to figure out where things go wrong?

Gruesse

Michael

4

Can you try to upload a >2GB size file via web interface in a desktop browser? If it cannot work, it is likely to related to your reverse proxy configuration.

5

1.) Successfully uploaded a 2.7GB file via the WebUI

2.) Retried the same via a extremely slow connection, there the message of a missing access token popped up, but I could run a “Retry” and also could successfully upload the file.

3.) Tried the same with the Android app:
Upload failed…

Gruesse
Michael

6

Could mitigate the issue by specifically increasing the timeouts for the https entrypoint. The successful uploads using the web interface mislead that this could be the issue.

It seems the android app is not applying the same magic the desktop interface does, to successfully upload big files. May be the android app should be modified to do it similarly the desktop app does…

Gruesse
Michael