Replies: 2 comments 3 replies
-
Hello, I think you might have misconfigured your webdav server. I ran in the exactly same issue with Signal, and the problem is due to files size limitation in Apache/nginx reverse. Mine was limited to 1024MB. Edit your Apache config and add credit: https://www.reddit.com/r/gnome/comments/17radiu/failure_to_share_files_larger_than_1gb_via_gnome/ |
Beta Was this translation helpful? Give feedback.
1 reply
-
There are known problems with nginx and Apache for chunked-transfer PUTs. Does it help to buffer the FastCGI requests as described here?
See also #745 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
So I have a WebDAV mount pointing at an Apache mod_dav server (with nginx reverse-proxy), and it seems to work fine as far as SeedVault and the file manager are concerned. But if I ask Signal to save a backup into the mount, it always fails with "Your recent backup could not be created and verified."
Firmware: CalyxOS v4.15.0
Apache: v2.4.57
nginx: v1.22.1
debug-info.txt, logcat: https://gist.github.com/gnoutchd/aa9714c879845b57caab423319d9680d
Looks like Signal fails at the verification step. At the WebDAV level it appears to create a zero-length file, PUT some data, then immediately GET it back -- only to see content-length: 0. But what's weird is the GET is sent before the PUT is finished, so it would make sense IMHO for my server to show the previous (empty) version of the file.
Is this a Signal problem, a davx5 problem, or is my server doing something weird after all?
Beta Was this translation helpful? Give feedback.
All reactions