nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Accepted answers

Joey Bradshaw

Wow this app is hot-garbage.

So you have to:

Generate a new SSH key using PuTTY
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.
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".
Then you have to double click the Pageant app from your system tray and add the key you just created.

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.

All comments

Joey Bradshaw

Wow this app is hot-garbage.

So you have to:

Generate a new SSH key using PuTTY
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.
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".
Then you have to double click the Pageant app from your system tray and add the key you just created.

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_3tjhf2

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.

CaptainPalapa

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

sourcetree

atl-gruland