Just installed Sourcetree 3.3.8
I followed these directions for linking to my bitbucket account.
I opened a repo on disk that I had already previously cloned using exist SSH keys I setup a long time ago in bitbucket.
Any time I try to push or pull I get this dialog.
Why is sourcetree popping this up? I already have valid SSH keys.. There should be zero problems performing operations repos I've already cloned.
Wow this app is hot-garbage.
So you have to:
Not enough steps Atlassian. Add at least 10 more. l33t fails..
Why this app cannot connect using existing standard SSH keys, which are already added to bitbucket and being used by the git CLI, is ridiculous.
Thanks that works
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That sounds like your keys were messed up somehow since that process basically describes a basic SSH key pair setup: Generate keys, provide public key to end host, configure applications to use private key.
I'd check your public key and known_hosts for changes in IP or hostname since this can cause a common SSH authentication issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For me, the problem what that Sourcetree kept complaining about not having a key loaded, then saying I did have a key loaded, in a loop. Turns out (for Windows), you have to double click Pageant hiding in the system tray (looks like Putty) and load the keys. Sourcetree never brings the app up for you to see "oh, there's no keys loaded today". They should stay loaded for the duration that Pageant stays loaded.
Bear in mind that you probably have more than one Pageant on your machine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.