I can still connect to it from the BitWarden extension in Chrome.
If I connect to it from BitWarden extension in Firefox, it loads the vault, shows that I have 1107 password records (which is the correct number), but all of them are blank. The whole list of 1107 items. I can click on them, and they open, showing me all the fields…All Blank.
If I connect to vwarden via the BitWarden phone app, I get one of 2 or 3 different errors. “We were unable to process your request. Please try again or contact us” is the most prevalent. I can look in the vwarrden log and it will show no errors, just 2 API calls that both returned 200 OK.
If I use the official bw cli, version 2024.7.2 (I’m now scared to update!!) It works perfectly.
Anyone else seen these problems?
I really really don’t want to move away from bitwarden/vaultwarden.
Thank you for the quick response, which I missed because I was still researching.
I was running vaultwarden:latest. Among other things, I rekeyed from the webUI. I looked at PR 5259, and tried to verify that I was running 1.32.6, but the log file says “Starting … Version 1.32.0” I think that is a build bug. I tried a few more things I found in issue 5237.
I read about the 4 versus null, 0, 1. You did not mention in there how to fix the 4 for a mere user :-P…
I backed up everything, then started from scratch. rm ~/vw-data; docker rm vaultwarden
Then I just started up the same image, set the URL in the admin page, and then created a new acct and imported the export of my data.
Now everything works.
But I can spin up a clone of it from today, before I rebuilt VW, if you want to investigate further.
Agreed, however I did all the steps, recreating a new container, and the new version still did not fix mine. Hopefully I am the only person with the “broken in yet another way” database…
But I will keep the snapshot around in case you want someone to run a HAR file if someone else runs into the problem again and the new version does not fix it for them either.
Merry Christmas
I had exactly the same problem. When I tried to access the vault in Android 14 I got an error (an error occurred …).
Vaultwarden runs as a docker on a private address and everything is fine. I can see through the web interface that the server is running and I have access to every item in the vault (or pay card).
When I checked the logs for the problem, I also saw 2 lines and 200 OK.
It didn’t work for a few days and then I started to deal with it. First I reinstalled the bitwarden app, but that didn’t help. I reinstalled it again, set it up and it’s been working ever since.
Today I had the same thing happen to me as wwalker in the first post. I opened biwarden on android and the vault is empty. In google chrome everything is OK
My ver. vaultwarden is 1.30.3.
I’ll try reinstalling it.
BTW I have the bitwarden app installed on two smartphones. It works great on Android 13 and has problems on Android 14.
Today I reinstalled to 1.32.7. If I logged in to the bitwarden plugin on android 14, the vault was still empty. I restarted the phone and reinstalled the bitwarden app and now it’s fine.
Hi, same problem here.
Since the Bitwarden update got installed on android phones i am unable to view some vaultwarden accounts. Message “… please try again later …” (translated, different source language)
Server is on latest / 1.32.7
Traefik logs show ok (status 200 log)
On Android:
Some accounts do work, some don’t (all on same server, Docker stack with traefik frontend, non standard web port), so i don’t think it is a setup problem.
[EDIT]: In the not working accounts, it is possible to view the folders in the vault settings but not view the entries in the main view. So i think the transfer of the database from server to client is working but displaying the entries fails [/EDIT]
Could be some problem with the internal database of bitwarden?
WebVault, Desktop Vault: everything OK
Tried switching to Argon2id, no difference
Tried reinstall App, clear cache & data, reboot phones, no difference.
Did not try to recreate the accounts, i try to prevent this steps if possible.
[EDIT2] Workaround / Fix:
Web Vault Export to encrypted JSON, delete all entries from affected vault and import again does fix the problem in the Android APP. Tested in 2 affected accounts on different Android devices.
For a single user this is a valid workaround but for a group/organisation/association this would cause problems.
I suspect the problem on the client side, not the server.
[/EDIT2]
