CODEWITHSUNDEEP
gitmsysgittortoisegit
ProfK
ProfK

Reputation: 51124

Authentication error when pushing to remote Git repo with TortoiseGit

When I try an push to my remote repo (Unfuddle) using TortoiseGit, my favourite tool, I get the following error. I then open GitGUI and am able to push with no problem. I have gathered through some googling that pageant needs to be running for some PuTTY variants, and it is running. Where do I look next?

No supported authentication methods available (server sent: publickey)

Upvotes: 9

Views: 9323

Answers (5)

Vesper
Vesper

Reputation: 433

Try this Example. This is the solution to your problem https://confluence.atlassian.com/display/BITBUCKET/Set+up+SSH+for+Mercurial

Upvotes: 0

j2emanue
j2emanue

Reputation: 62559

I tried all this but it did not work for me. It turns out i had my remote URL wrong:

try this way: https://github.com/Username/repository-name

instead of this: [email protected]:Username/repository-name.git

Upvotes: 1

Michael Fayad
Michael Fayad

Reputation: 1336

I had the same problem.

I think the problem was that my Putty key was not set in my TortoiseGit Settings. I had to convert my bitbucket repository private key to a putty private key (.ppk file).

This is how I fixed it:

  • I downloaded puttygen.exe

  • I opened puttygen

  • I clicked Conversions -> Import key -> (imported my "~/.ssh/id_rsa" key)
  • I confirmed my key passphrase
  • I clicked "Save private key" and saved the key in my "~/.ssh/" folder
  • I went in my TortoiseGit settings : (right click on my master folder) -> TortoiseGit -> Settings -> Git -> Remote -> origin -> Putty key -> ... -> (I added my newly generated putty private key)

And voilà, I was able to push to my origin repository.

Upvotes: 21

user1067737
user1067737

Reputation:

Resetting the default PuTTY configuration solved the issue here. To do so, delete the HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions\Default%20Settings key with regedit.

Upvotes: 2

Adam Dymitruk
Adam Dymitruk

Reputation: 129782

Push from the command line and see if you get the same problem. If you do, it's most likely a public key issue. 

SSH -vvvv yourproject.unfuddle.com

To see what key is bring presented. You can manipulate what public keys are used by tailoring your .ssh/conf file.

Hope this helps.

Upvotes: -1

Related Questions