Bitwarden CLI not syncing items

Ask the Community Password Manager
1

Hello everyone. I’m having an issue with the Bitwarden CLI syncing with my vault.

I’ve been testing the CLI to use with a script I’m designing and it kept failing and I couldn’t figure out why. I then began running the raw queries itself in my terminal to see if I could get the results I wanted. I noticed that changes I was putting in my Chrome Extension, although was syncing to the Bitwarden Vault (and visible on mobile) are not actually getting changed in the CLI.

I did a sync including with the force flag, and no update. I logged out and back in as per the Bitwarden Support rep I spoke with, and this resolved the issue - but only to the point of when I logged in again. Once any further changes were made, even after syncing, the CLI won’t retrieve these new changes. In particular I’m noticing this with secure notes, adding, removing or editing. I haven’t done enough testing with logins to see if this behavior is consistent.

Anyone else experiencing this and have any feedback or soltutions?

Thanks,
Brandin.

3

I think I may experience the same issue.

bw list items | jq | grep token doesn’t show the item that I can clearly see present in the desktop app and online vault.

I also added a new item just for testing purposes - “A token test” and the cli tool doesn’t see it as well.

I logged out, logged in and sync’ed.

Best,
Yevhenii

4

I also have this issue…

5

I regularly encounter this issue (it occurs in spurts, a month or two at a time, and doesn’t happen again for six months).

It’s mainly on new items (added from the Web vault), and I can usually fix it by removing the item from one of the collections, clicking save, and then re-adding it to the collection and then syncing again.

Note that syncing doesn’t fail. It appears to be some sort of backend issue at Bitwarden, I’ve had a long standing ticket open with Bitwarden (almost 14 months now) but as yet they’ve been unable to resolve it.

6

Hello everyone,

Thank you all for your input. For anyone that is still encountering this; are you encountering this in relation to vault items within your individual vault or within an organizational vault?

Thank you in advance,