Skip to main content
B
blemasle
February 14, 2025
Solved

Issue with SSH agent since last release(s) ?

  • February 14, 2025
  • 3 replies
  • 898 views

Hi,

For a few days now, I'm facing some weird SSH agent issue with the last release of 1password for windows : `Load key "[keypath]": invalid format`.

This is occuring when signing, pulling or pushing git commit, but also on simple ssh connections. It does not occur every time, but almost exactly 1/2 of the time. To me, this exclude problems with key format or permissions issue and the culprit must be the ssh agent somehow.

OpenSSH Authentication Agent service is disabled, and everything was working fine for months now. I started to see this behavior since the last release on february 12th I guess, but I'm not entirely sure.

I cannot find the 1password ssh agent process to be sure it does not run twice for instance which could explain the random failure.

Is anyone facing a similar issue or is it a know problem ? Nothing in the logs obviously :) 

Regards

    Best answer by blemasle

    Well after more research and a bit of luck, I found out the culprit which is... bitwarden 
    I need to use both as my company use it. They recently release an ssh agent of their own but it claims the socket even if the agent is not started, resulting in communication error with the 1password agent.

    Quitting bitwarden + restarting 1password made the trick.

    3 replies

    B
    blemasleAuthor
    February 14, 2025

    And using ssh-add -l, one every two times I see either my keys being listed or "error fetching identities: agent refused operation"

    B
    blemasleAuthor
    February 20, 2025

    Ok, it's getting critical cause it fails every single time now...
    In the logs, I can see various issues with the agent like

    • get_agent_identities: ssh_fetch_identitylist: agent refused operation

    • error fetching identities: agent refused operation

    Can someone in the 1password team assist me in this ?

    B
    blemasleAuthorAnswer
    February 20, 2025

    Well after more research and a bit of luck, I found out the culprit which is... bitwarden 
    I need to use both as my company use it. They recently release an ssh agent of their own but it claims the socket even if the agent is not started, resulting in communication error with the 1password agent.

    Quitting bitwarden + restarting 1password made the trick.

      Terms & ConditionsAccessibility statement

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