Suddenly getting “No supported authentication methods available” when pushing to github

Question

I started a github project a few weeks ago. I was able to push changes without any problems (I'm using TortoiseGIT).

Suddenly today when I tried to push my changes, I got "PuTTY Fatal Error" "Disconnected: No supported authentication methods availble" error window.

Anything you can recommend to remedy the problem?

Answer 1

I figured it out - it happened because I reinstalled TortoiseGIT since starting to work on the project. Pulls went smoothly, but as soon as I tried to push back my changes TortoiseGIT needed my authentication key, which was not configured.

Edit

To resolve, I simply cleared all authentication data from my TortoiseGit, under: Context menu "Tortoise Git" -> Settings -> Saved Data -> Authentication data [Clear]

Answer 2

For me there was a problem to perform actions against the remote repository only when using TortoiseGit, through CMD / GitBash there have been no issue at all.

So what I did was Very simple: I opened TortoiseGit-->Settings --> Network and in SSH Client I changed "ssh.exe" instead of "TortoiseGitPlink.exe".

Answer 3

Make sure you installed TortoiseGit with OpenSSH and that you use the SSH authentication method. If you installed with Putty, there may be a "computer symbol" in the systray called "Putty Pageant".

Answer 4

I was able to fix this error by adding the private key into Pageant. I forgot to do this during the key creation, and once I added it I no longer received the error.

Answer 5

In my case, Tortoise Git lost PuttyKey. So I had to go to TortoiseGit settings > Git > Remote and in this section I clicked on Remote frame my origin and PuttyK Key was not set (It was before). I had to set it up again.

Answer 6

For TortoiseGit Users on Windows
(as I originally posted in this question)

I used to setup most of my Github/Bitbucket repositories using the SSH repository URLs as (originally) it used to be the only convenient way to prevent TortoiseGit from prompting for your password on every single action.

But setting TortoiseGit up this way was always hair-pullingly painful. Every time it took me hours to set up correctly, as the default installation options never seemed to work (even as of 2016, sheesh!).

But TortoiseGit now has better password management for HTTPS, and Github actually recommends using HTTPS URLs wherever possible.

SSH URL: git@github.com:User/repo-name.git

HTTPS URL: https://github.com/User/repo-name.git

The benefits of HTTPS are:

• No managing or generating of SSH keys
• No need to have pageant.exe constantly running (which requests your password on each launch)
• Using TortoiseGit from Australia, I find that clones over HTTPS are 5-10x faster than SSH

Answer 7

To fix this, I had to manually run Pageant from the start menu:

Afterwards, I saw pageant in the system tray:

I could add my key. Normally, keys are in %userprofile%\.ssh.

Answer 8

For me I was getting this error after upgrading GIT to 2.8.0. The issue was due to the $HOME directory being incorrectly read by bash and defaulting to some system location under the windows installation folder: /c/Windows/system32/config/systemprofile.

Turns out that a little environment variable cleanup was required. A long while ago I had installed a version of GIT (about 1.7.x) which had created a HOME variable in the system environment variables. This needed to be removed after upgrading to 2.8.0 due to some change in behaviour, rather than adding a further HOME user environment variable.

Answer 9

I had this same error, which randomly occurred out of the blue after having successfully pushed to my repository over many months. In my case, in Tortoisegit->Settings->Git->Remote, the Push URL field was somehow empty.

Answer 10

See my post here. I had this problem just now and tried everything posted here but I couldn't solve it. At the end was this exact same problem related to an existing PuTTy configuration => [TortoiseSVN keeps on asking me for my password

Answer 11

For me, I had to update my version of "msysgit" to a 1.7.10+ version. Once done I did not face the above mentioned error. I think you might need to check if you have installed msysgit and if not there install it.