Hey Vaultwarden users… I was turned on to Vaultwarden by this community and have a new installation up and running. I’ve recently imported a pretty substantial keeypass DB and have been manually validating the import and tidying up my folder organization as I go, including selectively moving some credentials to an organization with the future intention of adding family members to that org to access shared accounts.
By and large it’s all going swimmingly with one concerning exception. Every now and again, a bunch of credentials forget their folder and get moved into “no folder”.
- I don’t have a reliable reproduction yet, but it seems vaguely correlated with bulk moves. In the web-ui, I’ll check a bunch of entries to move from my vault to the org, and OTHER entries I didn’t touch get moved to “no folder” in my vault as a side-effect.
- Once I had a folder disappear like this as well
- I think I understand the basics around how collections, folders, and nesting of those containers work. I’m fairly confident that I’m not getting tripped up by just failing to understand the implications of the operation I’m doing.
- I’m using sqlite for my db backend. I’m perfectly comfortable running a Postgres instance, I just thought the no-maintenance and no-dependencies approach of sqlite felt like a good match for this tiny but critical dataset. Could it be that the sqlite backend is under baked and I"m hitting some persistence bug?
- Fwiw I’ve also seen issues where I get an encryption key error saving an entry or I see tons of missing entries.In each case logging out and logging in works around the issue. I had assumed this was browser/web buglets, but now I wonder if it’s more signs of storage layer problems.
Have others seen similar issues? What db backend are you using?
One thing to keep in mind is that the websocket sync is not straightforward to set up with vaultwarden and the proxy. If you don’t have it working, then your client does not necessarily sync on every change.
Maybe this is related to this, with sync not being performed by the client you were using for modification?
Thanks for the suggestion, but sync seems to be working ok… at least on the read side. I was able to verify the pre-existing good state and the bad state afterward from multiple clients. If sync played into it, it must have been on a write somehow.