Skip to main content
XIII
XIII
May 23, 2022
Question

op 2.3 via Connect broken

  • May 23, 2022
  • 16 replies
  • 218 views

Looks like op 2.3 and/or Connect is broken (reading fields from sections?), breaking almost all of my automations...

On my Raspberry Pi or router (both talking to 1Password Connect on my Pi).


➜ op read op://Automation/fastmail/webdav/password
[ERROR] 2022/05/23 09:24:49 could not read secret op://Automation/fastmail/webdav/password: could not find field or file password in section webdav on item fastmail in vault Automation
➜ op read op://Automation/fastmail/username
me@fastmail.com

On my MacBook Pro (directly talking to 1password.com):


➜ op read op://Automation/fastmail/webdav/password
my password
➜ op read op://Automation/fastmail/username
me@fastmail.com

Please fix (reading fields from sections?) ASAP.

1Password Version: CLI 2.3 / Connect
Extension Version: n/a
OS Version: n/a

16 replies

Show previous replies
A
Anonymous
May 23, 2022

I've looked a bit into the code responsible for this, and have confirmed that this error can be returned in two cases:

  • the section cannot be properly identified
  • the field cannot be properly identified

In order to continue diagnosing this, can you please take another look at your item's json and let us know if there is anything that appears unusual about the section/the field that this error happens for?

In particular, I am interested whether the field ID and the section ID (as they can be seen in the item's json format) are properly formatted: i.e. strings made out of 26 characters (lowercase letters and digits). My hunch is that there may be something off with the validation that the CLI performs when passing queries to Connect, when looking up sections/fields.

Looking forward to hearing from you.

Best,
Horia

XIII
XIIIAuthor
May 23, 2022

I think the issue occurs because the field names in two sections of one item are identical...

This is what happens with different field names:

  • webdav/password & imap/password: only reading imap/password works
  • webdav/passwork & imap/password: reading both fields work
  • webdav/password & imap/passwork: reading both fields work

Does this help in finding/fixing the bug?

A
Anonymous
May 23, 2022

Indeed, we think we've identified it!
Thank you for all your help here.
We're currently working on a fix, and will notify you as soon as this rolls out!

Best,
Horia

XIII
XIIIAuthor
May 23, 2022

That's good news!

Hope the fix will be available soon; several automations are broken here because of this...

(apparently I got quit dependent on this new 1Password product;)

A
Anonymous
May 24, 2022

Hey @XIII

This should fix it: https://app-updates.agilebits.com/product_history/CLI2#v2030101
Thank you once again for raising this with us, and helping us diagnose and fix this.
Looking forward to hearing your feedback!

Best,
Horia

XIII
XIIIAuthor
May 24, 2022

Did not see it appear in my RSS feed yet (oh wait, that also does not work because of this bug), so thank you for informing me here.

CLI version 2.3.1 indeed solves the problem; I can now read that password using both 1password.com and Connect! Thank you!

Terms & ConditionsAccessibility statement

©2026 1Password. All rights reserved.
4711 Yonge St, 10th Floor, Toronto Ontario, M2N 6K8, Canada