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,643,455
Community Members
 
Community Events
196
Community Groups

SSH not working on SourceTree?

I have set up SourceTree to use SSH but it does not appear to be working.
Whenever I try to do a fetch from our remote repository, I get prompted for a username and password.
When I enter the correct username and password, this is what I get (in the space marked XXXX, SourceTree puts my ACTUAL PASSWORD):

git -c diff.mnemonicprefix=false -c core.quotepath=false fetch --prune origin
Access denied
Access denied
Access denied
Access denied
FATAL ERROR: Server sent disconnect message
type 2 (protocol error):
"Too many authentication failures for XXXXXXXX"
fatal: The remote end hung up unexpectedly
Completed with errors, see above.

So not only does the SSH auth not work, I can't even use username/password auth. Does anybody have any ideas?

5 answers

1 accepted

18 votes
Answer accepted

I was able to fix the problem by changing from "Putty/Plink" SSH to "OpenSSH" for the SSH provider. No idea why this helped, but it works now.

I had this problem for days and spent many hours on it.... And this solved it!!!! Do this!

 

Thanks

Like Gaurav Singh likes this

Thanks, i also had the same problem for days and today with your guidance i was able to fix it!

Wiser words have never been spoken. Thanks. This works

Wooooow, this answer is priceless.

It still does the job in 2019. Awesome and thank you!

God, this issue cost me around 3 days to find out.

 

This one worked for me as well. Thank you!

SSH-Bug.png

Can you please tell me the path?

I am still facing the same issue

Works now, thanks!

I see the same problem when trying to use putty without keys (only username and password).

stevestreeting
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 25, 2013

Please try with today's release (1.2.3), a couple of refinements have been added for URLs which don't include the user name and manual login is used.

0 votes
KieranA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 17, 2013

Hi Tom,

This is very unusual behaviour. The error you're seeing which is showing your password is output from Git itself. Could you tell me more about your SSH setup? You've set up your id_rsa and id_rsa.pub keys in ~/.ssh/ and the URL for that repository has an SSH URL format? It looks like to me it's prompting for auth because it can't find any which could mean a number of things.

With further information we'll gladly be able to help.

Cheers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events