Skip to main content
gboudrea
Mar 12, 2022 9:43 PM UTC
Question

Invalid iv in the message

After successfully signing in, trying to list my personal vault errors-out:


$ op list items --vault gboudrea
[ERROR] 2022/03/12 16:37:17 Invalid iv in the message: 16

Other vaults are OK.

Similarly, I can do op get account 'My Item Name', but trying to get the TOTP of the same item fails. Same for get item:


$ op get totp 'My Item Name'
[ERROR] 2022/03/12 16:39:25 failed to listMatchingItemsInVault: Invalid iv in the message: 16
$ op get item 'My Item Name'
[ERROR] 2022/03/12 16:41:55 failed to listMatchingItemsInVault: Invalid iv in the message: 16

Thanks.


1Password Version: CLI 1.12.4
Extension Version: N/A
OS Version: macOS 12.2.1

18 replies

gboudrea
gboudreaAuthor
Mar 17, 2022 4:40 PM UTC

I then went on 1password.com, and in my Guillaume vault, an item was left. That item was NOT showing in 1Password 8 for Mac.
So I moved that item to another vault (Personal), and now, I can successfully list both my Guillaume and Personal vaults!
I moved that item back into Guillaume, and voilà. I can now list all vaults using the CLI, and that item works too. I guess moving it from 1password.com fixed the problem with that item.

FYI:
That item was NOT My Item Name, it was something else.
That culprit item had:
- last modified: February 28, 2016 5:00 PM
- created: November 24, 2009 9:10 AM

So for anyone with a similar problem:
- Create a new vault
- Using a native 1Password client (Mac or Windows): nove all items from the problematic vault into that new vault
- Go on 1Password.com, and look into the problematic vault; you should see 1+ other items. Move them into the new vault from the web interface. You should now see all items, including those problematic items, in the new vault.
- Using a native client: nove all items from the new vault back into the problematic vault
- Delete the now empty new vault
The problematic vault should now be OK. Yay.

Mar 17, 2022 7:08 PM UTC

Thank you so much for following up here. We really appreciate your patience. We have one last piece we'd like to hit on privately to wrap this up. To facilitate that, could you please email us at 'mailto:support+forum@1password.com', and then post the support ID you get back from BitBot here?

gboudrea
gboudreaAuthor
Mar 17, 2022 7:17 PM UTC

#YSL-13514-125

Mar 17, 2022 7:24 PM UTC

Looks like your messages just came into our system, did you get a response from BitBot via e-mail?

gboudrea
gboudreaAuthor
Mar 17, 2022 7:25 PM UTC

(Yes. Edited my post above.)

Apr 5, 2022 2:58 PM UTC

Hey @gboudrea,
Just to confirm, has your problem been solved, or do we need to follow up here? :D

Thanks,
Horia

gboudrea
gboudreaAuthor
Apr 5, 2022 4:53 PM UTC

All good, this can be closed.

May 19, 2022 10:45 AM UTC

Glad this got sorted out! Let us know if we can help with anything else.