Error: Must provide Key

Help
1

Hi

I’ve been running vaultwarden for years without problems.

Unfortunately now, I cannot access my vault, neither per web, app, extension or cli.
In developer tools it shows me this:

image
image1162×352 53.6 KB

In CLI I find the same error:

Error: Must provide key
at SymmetricCryptoKey (/usr/local/Cellar/bitwarden-cli/2024.6.1/libexec/lib/node_modules/@bitwarden/cli/build/bw.js:1489:19)
at Cipher. (/usr/local/Cellar/bitwarden-cli/2024.6.1/libexec/lib/node_modules/@bitwarden/cli/build/bw.js:3566:26)
at Generator.next ()
at fulfilled (/usr/local/Cellar/bitwarden-cli/2024.6.1/libexec/lib/node_modules/@bitwarden/cli/build/bw.js:3470:58)

I can still access the organizations entries, I am also the only user with this problem.

The only thing I actually did different was using the native Bitwarden beta app on iOS.

I hope, somebody can give me a hint where to start troubleshooting.

I’m using vaultwarden in docker behind Traefik. I tried both latest and testing. I also tried an older db snapshot, unfortunately no change.

2

What exactly do you mean by that? Did you add or update an entry? We have another user reporting the same issue after adding an entry with the beta app on iOS.

3

I was able to restore using a snapshot.

Aside from having the original issue, which is with my organizational policy on where users individual vault is removed, I am going to try and break this again and see if I can reproduce.

It happened when trying to add an item or edit an item and/or when/after I took off that organization policy. From the iOS app I am not able to save or edit anything.

4

When this issue happened did you happen to add an item to your vault using the iOS native app and save? I am able to reproduce this on demand.

5

Yes, it happened when I tried to change an organization entry with the iOS beta app, exactly as you mentioned in your issue.

In the meantime I was able to restore from an older snapshot. Seems like the first snapshot I had tried was already corrupted.

1 Like
6

Thank the IT gods for backups, and hopefully regularly tested backups too.
Or at least in this case a forced test to confirm restore capabilities. :wink:

1 Like
7

Good news is it’s reproducible, now just have to dig and find out what’s causing it; client side or server side.

This does put me at ease with reverting from a snapshot and seeing there was no complications and how simple it was. Kind of glad I spun up a test container a long time ago just to mess around.