Hello,
I use vaultwarden with docker compose, latest version. I am also using the latest fdroid bitwarden (2024.7.1).
When I try creating a send, I get “An error has occured, Send not found”. Any ideas? I’ve seen some issues on GH, but they seem to be closed with fixes merged a long time ago.
The Android app i in f-droid is outdated.
See GitHub - bitwarden/f-droid: Bitwarden F-Droid support. for the updated links
I swapped the fdroid repo link, updated (2024.9.0) and now get “We were unable to process your request. Please try again or contact us.”
The file is smaller than 100 megs.
Which version of Vaultwarden are you running? v1.32.1 should solve all issues.
From diagnostics:
Versions
Server Installed Ok
1.32.1
Server Latest
1.32.1
Web Installed
2024.6.2c
Database
SQLite: 3.46.0
When I try to create a new send from the app, here are the only logs I get in my docker compose console:
vaultwarden-1 | [2024-10-04 14:14:38.683][request][INFO] POST /api/sends/file/v2
vaultwarden-1 | [2024-10-04 14:14:38.685][response][INFO] (post_send_file_v2) POST /api/sends/file/v2 => 200 OK
vaultwarden-1 | [2024-10-04 14:14:43.716][request][INFO] DELETE /api/sends/HASH
vaultwarden-1 | [2024-10-04 14:14:43.718][response][INFO] (delete_send) DELETE /api/sends/<id> => 200 OK
It looks like it deletes the send immediately after creation. I did not change the send settings. I have also not configured any per user limits, but that should be enforced by the server anyways.
It works fine for me using Version: 2024.9.0 (19209) of the android app.
Try to enable debug log level, and also check your reverse proxy.
Reverse proxy was indeed at fault, I found it out by creating a large send from the web extension:
I added
client_max_body_size 200M;
to my nginx vaultwarden config, and now everything works.
P.S. sends on mobile are limited to 100MB but other applications can attach up to 500MB currently.
So you may wish to set the limit slightly higher than that if you wish to account for supported edge cases.