Recently android app will no longer work with my server

I’ve been running my own server for a few years.

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!

Which version of Vaultwarden are you running?

BlackDex,

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.

Or just install 1.32.6 by pulling in the recent image.
Something like

docker pull vaultwarden/server:latest 

Should work, but you still need to remove and recreate the container afterwards.

The reason i didn’t explained how people could fix it is because i fixed it in code and running the latest version should solve your issues.

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… :slight_smile:

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.

Thank you!