Today started out fun. I've been using the old SourceTree client for over a year, with key authentication via pageant. Today my co-worker changed permissions settings on the bucket, and I found that I could no longer access a couple of repositories via SourceTree - it kept prompting me for a username and password. Through the git CLI, I was still able to perform all the usual tasks on the sasme repository using username/password authentication.
In an effort to fix this, I updated all software to the latest versions installed. No dice, it still wouldn't work. So I created a new key, and add it to pageant and bitbucket, deleting the old key from both. I only have one key.
Under "Edit hosting account" for my only BitBucket account, I have "preferred protocol: SSH", as per the instructions. I have the green tick and "Authentication OK".
Under repository settings, I have my origin path. In there, the URL is ssh://bitbucket.org/~~/~~, host type is bitbucket, username is my username - the one that works through the CLI.
Everything is looking good, right? Until I try to do anything, upon which I receive the error message above. If I try to use the git CLI, I'm told that it can't communicate with my authentication agent.
How do I resolve this?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs