Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,460,023
Community Members
 
Community Events
176
Community Groups

Sourcetree with Gitlab - SSH not working

Hi,

I have been evaluating using Sourcetree for Windows with a Gitlab server. I have been able to clone, push, and pull correctly over HTTP. This was not possible until I correctly uploaded my public SSH key to the server and pointed Sourcetree and my HOME environment variable to the private key. However, I am still unable to connect via SSH.

Using the git bash, running "ssh -vvvT git@SERVER" prompts me for my SSH key password, then connects correctly (responds with a welcome message as well). This indicates that my SSH key is set up correctly.

When attempting to clone an existing test repository, using the path "git@SERVER/REPO_DIR.git" results in an invalid source path. Clicking details gives me the following:

"fatal: 'xxxxxx' does not appear to be a git repository
fatal: could not read from remote repository.

Please make sure you have correct access rights and the repository exists"

When attempting to clone the repository, using the path "ssh://git@SERVER/REPO_DIR.git" results in and invalid source path with the following details:

"Access denied
Access denied
Access denied
Access denied

FATAL ERROR: Server sent disconnect message type 2 (protocol error):
'Too many authentication failures for git'
fatal: could not read from remote repository

Please make sure you have correct access rights and the repository exists"

Again, this works over HTTP flawlessly. My user account has been created and my SSH key is correctly stored. Why am I still having trouble with SSH? Are there other SSH commands I should run in the git bash to debug this issue?

7 answers

7 votes

Apologies for the late response, I've been out of the office for a week.

It sounds like you're using OpenSSH keys (and not PuTTY), did you choose the OpenSSH option in the setup wizard? If not, you can set this in Tools > Options > General > SSH Client - it should pick up your key location automatically if it's the standard ~/.ssh/id_rsa but otherwise you can specify it. If your key is protected by a passphrase, you'll be prompted to supply it in a pop-up terminal window when you confirm the settings, and when you start SourceTree next time - this is necessary so that there is an instance of ssh-agent running that SourceTree can talk to with your key loaded.

If you need to load more than one key into your agent, you can do this from the Tools menu, Add SSH Key.

Once you have this configured SourceTree should behave just like the command line since OpenSSH picks up all the same configuration files.

this is far too difficult, why can't it "just work"

I'm experiencing a similar error, how I'm not using OpenSSH. My SourceTree client is running on a Windows machine with PuTTY/Plink selected. Any suggestions?

This resolved my issue. Thanks! 

Resolved my issues

Thanks, but now I have getting a new issue.

Permission denied (password,keyboard-interactive,publickey).
fatal: Could not read from remote repository.

@stevestreeting thanks a lot. Your provided solution solved my issue with keys. 

Hello! This worked for me, but only with the ssh key, and not with the username and password.

After I added the ssh key to sourcetree, I changed the settings in Tools -> Options -> SSH-Client to work with PuTTY / Plink.

I ran into a problem after I added the ssh key because I forgot to restart sourceTree. Hope this helps.

custom writing services

Thnx!! This worked!!! simply just use OpenSSH instead of Putty as option and it will work

I am using putty for the key. I had this issue and Adding key again at Pageant(PuTTY authentication agent) from windows quick icons on the bottom right end near time solved it. Good luck! 

I have the same issue. I imported my key but it doesn't work for me. Bitbucket SSH > clone locally > spotless

 

 

Try from gitlab and the horrors begin... 

use http url instead of git url like bellow :

http://server/user/project.git

In my case I wasn't prompted for the pass phrase and starting SourceTree from the Command Line, fixed it. The prompt closed inmediatelly after popping up

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events