Authentication via SSH keys failed

[Joey Bradshaw]

Just installed Sourcetree 3.3.8

I followed these directions for linking to my bitbucket account.

https://confluence.atlassian.com/get-started-with-sourcetree/connect-your-bitbucket-or-github-account-847359096.html

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.

[Joey Bradshaw · Accepted solution]

Wow this app is hot-garbage.

So you have to:

1. Generate a new SSH key using PuTTY
2. Run through a bunch of unnecessary hoops (https://confluence.atlassian.com/sourcetreekb/generate-and-load-ssh-keys-into-sourcetree-with-putty-790629663.html) to save the public and private keys to disk.
3. Go to your bitbucket account and add the public key, but the one displayed in PuTTY - if you try to open the .pub from disk and paste that it will fail with "Invalid key".
4. Then you have to double click the Pageant app from your system tray and add the key you just created. 
5. 

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.

[Galih Aria Dananjaya]

Thanks that works

[Electric Erger]

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.

[Steve]

This works, but after a while I need to re-do it again.  Just for fun's sake I guess.  I had to re-set it the 4th time today.