You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to upload a big file (or a small one with limited bandwidth), the upload always fails.
When looking at the reverse proxy logs on server side (traefik), there are some kind of timeout after ~60 seconds (most likely due to traefik's default read timeout of 60s).
Then, If I try to restart the upload, the upload starts again from the beginning.
When searching in existing issues, there is a 4 year old issue (#2978) referring to file upload but I don't know the current status of this feature.
Expected behavior
I was expecting :
large files to be uploaded in multiple chunks
failed uploads to restarts from where it ended
Steps to reproduce
Use ocis as backend (5.0.8), with traefik as reverse proxy
Try to upload a big file (which takes more than 60 seconds to upload)
The TUS protocol is still not implemented in the Android app. But, as you mentioned, that timeout comes from your proxy, so the best thing you can do here is setting it to a bigger number in traefik or removing it at all. We have TUS introduction in our future roadmap anyway, so we hope we can include it soon 👍
Actual behavior
When trying to upload a big file (or a small one with limited bandwidth), the upload always fails.
When looking at the reverse proxy logs on server side (traefik), there are some kind of timeout after ~60 seconds (most likely due to traefik's default read timeout of 60s).
Then, If I try to restart the upload, the upload starts again from the beginning.
When searching in existing issues, there is a 4 year old issue (#2978) referring to file upload but I don't know the current status of this feature.
Expected behavior
I was expecting :
Steps to reproduce
Environment data
ownCloud app version: 4.4.0
ownCloud server version: ocis 5.0.8 behind traefik
Logs
I can provide logs if needed, but I think the issue is easy enough to reproduce.
The text was updated successfully, but these errors were encountered: