Intermittent "agent refused operation" - Restart 1Password to fix

gboudrea

Sometimes, the 1Password agent would just stop working. Same client, same server, unchanged keys.
When that happens, if I completely close 1Password from the menu bar, and restart it, then it works as expected.

When it doesn't work, I get the following error using SSH :

$ assh fileserver5
sign_and_send_pubkey: signing failed for ED25519 "id_ed25519" from agent: agent refused operation
gb@fileserver5's password: 

The only line logged in $HOME/Library/Group Containers/2BUA8C4S2C.com.1password/Library/Application Support/1Password/Data/logs/1Password_rCURRENT.log when this occurs :

INFO  2022-05-15T14:07:03.281 tokio-runtime-worker(ThreadId(4)) [1P:ssh/op-ssh-agent/src/lib.rs:381] Session was not authorized

When this happens, I see no popup from 1Password asking me to authorize the SSH key access.

Not sure how related it could be : I'm on a Mac M1 with Touch ID, which I always use to authorize 1Password requests to SSH keys.

Thanks.

---

1Password Version: 8.8.0 (80800021)
Extension Version: Not Provided
OS Version: macOS 12.3.1

thesun

I'm on Windows 11 and I every once in awhile get this as well so I don't think this is a Mac M1 specific issue. It seems to typically happen after a reboot but doesn't happen all the time. To fix, I need to unlock 1Password and then restart my Terminal application. That last bit is slightly odd - I use Windows Terminal and I have profiles that run ssh from the OpenSSH that is distributed with Windows. Re-running ssh isn't enough, I need to actually restart the terminal application.

I have a similar error in some of my logs, I can't correlate it right now to this specific issue but I'll have to note the next time it happens.

INFO  2022-05-05T10:26:16.589 tokio-runtime-worker(ThreadId(7)) [1P:ssh\op-agent-controller\src\desktop.rs:311] SSH Agent has started.
INFO  2022-05-05T10:26:33.350 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging\op-native-core-integration\src\lib.rs:305] Extension connecting.
INFO  2022-05-05T10:26:33.350 tokio-runtime-worker(ThreadId(8)) [1P:native-messaging\op-native-core-integration\src\lib.rs:307] Extension connection accepted.
INFO  2022-05-05T10:26:46.731 tokio-runtime-worker(ThreadId(11)) [status:op-app\src\app\backend\updater.rs:206] No Nightly updates found for 80800012
INFO  2022-05-05T10:33:39.659 tokio-runtime-worker(ThreadId(7)) [1P:native-messaging\op-native-core-integration\src\lib.rs:305] Extension connecting.
INFO  2022-05-05T10:33:39.659 tokio-runtime-worker(ThreadId(7)) [1P:native-messaging\op-native-core-integration\src\lib.rs:307] Extension connection accepted.
WARN  2022-05-05T10:35:18.870 tokio-runtime-worker(ThreadId(44)) [1P:foundation\op-enclave\src\windows\mod.rs:324] platform state changed, hardware-backed unlock has been invalidated and is now unavailable
INFO  2022-05-05T10:35:18.871 tokio-runtime-worker(ThreadId(8)) [1P:ssh\op-ssh-agent\src\lib.rs:381] Session was not authorized
INFO  2022-05-05T10:35:26.804 tokio-runtime-worker(ThreadId(14)) [1P:op-data-layer\src\load.rs:136] loaded 1478 items in 9 vaults for account: <REMOVED>

MartonS1P

Are you still encountering this issue? Note that updating to the latest nightly could help resolve it.

gboudrea

It happened to me a few times a day since I opened this thread. I had 80800126, on BETA channel this morning.
I changed the channel to NIGHTLY, and got 80800133.
I will try this build, and report back during the weekend or Monday, to indicate if this build solved my issue or not.
Thanks.

gboudrea

This indeed seems to be resolved in the 80800133 build. I have yet to hit this problem since installing yesterday. Thank you for your help.