Skip to main content
June 12, 2025
Question

Ongoing Issues with 1Password & GitKraken Integration – Frequent Unlock Prompts

  • June 12, 2025
  • 1 reply
  • 180 views

I wanted to follow up on an issue I raised recently in another community post (link here). I’ve also reached out to 1Password support, but the problem is still unresolved.

I’m experiencing a persistent issue where I’m prompted to unlock 1Password almost 30 times a day, and I’m fairly certain GitKraken is the cause. When GitKraken is closed, these prompts stop entirely. The first prompt is always an SSH prompt, but the subsequent prompts don’t seem to be related to SSH at all. It’s becoming extremely frustrating, to the point where I’m seriously considering whether I can keep using both tools together.

Is anyone else in the community running into this? If so, could someone from the 1Password team help catalog these reports so the issue can be properly addressed? This would really help those of us relying on both 1Password and GitKraken for our workflow.

Thanks!

1 reply

1P_Dave
1Password Employee
June 20, 2025

@davmav 

Thank you for following up. I see that my colleague sent you a reply via email back on May 30th with some steps that he'd like you to try in order to shed more light on the issue that you're running into. I recommend following up in that support ticket so that the team can investigate this further. 

If you don't see the email then check your Spam/Junk folder, it might have landed there. 

-Dave

davmavAuthor
June 21, 2025

Hi@1P_Dave 

Thanks for your recommendation. I’m not sure if you stay appraised with your colleagues, but I did reply to him on the 30th, and we exchanged a few emails actually before we concluded that it was GitKraken and he’d suggested trying to reset the App which we did without much avail. I don’t think it’s an issue that can be fixed by adjusting a setting, I think it’s something your team may need to investigate, you should still have all the log files I’ve sent over.

1P_Dave
1Password Employee
June 25, 2025

@davmav 

Thanks for the reply. I recommend that you continue the conversation over email since I don't have access to your logs here in the public forum. One of my colleagues will send you another email soon. 

Since we have a communications channel open via email, I'll close this thread to avoid duplicating efforts. 

-Dave