I have read the GitHub questions here rather thoroughly, but couldn't find the clue to my problem. I have created new git repo and now I'm trying to push it to GitHub: I get:
Jun 17, 2017 Yes, all I did after posting my problem was doing each step of these tutorials very slowly and when it got to step four where it says to generate a key pair or copy the public key, I just went to Digitalocean where the public key is and copied that instead. Oct 19, 2016 Same problem. I'll keep an eye on this issue and also see if I can find a solution. Since this is only a Putty problem there must be a setting somewhere.
ClergymanClergyman
6 AnswersWhen I choose plink.exe to perform the authentication, Here are my steps
Mr. HAMr. HA
I ran into the same error message trying to get Git, Git Extensions, and GitHub working with 64-bit Windows 7. I was able to solve the problem while continuing to use Putty. I created a .profile file in C:UsersMyUserName with the following contents: Had to use 'touch .profile' within git bash to create the file since Windows GUI chastises you for trying to create files starting with period. Can't take credit. I just put a windows spin on the answer provided here.
Community♦
kemidakemida
The solution is somehow change default ssh client for git from pegeant to openSsh. E.g. reinstall git and check openSSH in the corresponding window (not pegeant or something), if you have just installed git and haven't started to work woth it yet.
ClergymanClergyman
Could the section 'No supported authentication methods available' on GitHub help at all? You should be aware of the environment variable See this post for a longer discussion.
VonCVonC
![]() Have you properly set up your ssh keys on github? You need to create a ssh key, and put your public key on github. The two top references are and
jkeeshjkeesh
My co-worker have this error crop up on him today using TortoiseGit. He had inadvertently moved his Putty Private Key file (myprivatekey.ppk) into a different folder. So ensure the path to your private key file is correct. In TortoiseGit, go to Settings...Git...Remote. See the screenshot below:
James LawrukJames Lawruk
Not the answer you're looking for? Browse other questions tagged gitgithub or ask your own question.SSH to my AWS server just broke for both Putty and Filezilla. I'm making some effort for this post to be a comprehensive troubleshooting list, so if you share links to other stack overflow pages, I'll edit them into the question.
However, the only thing I could think that would impact a previously working system is:
What other possibilities are there? Solution to this one (per the accepted post below) is that for AWS EC2 all 3 of these need to have proper permissions (777 not ok for any of these). Here's one example that works: /var/log/secure will tell you which one is throwing an error, consult this video tutorial to get access if you're completely locked out:http://d2930476l2fsmh.cloudfront.net/LostKeypairRecoveryOfLinuxInstance.mp4
AvadData
AvadDataAvadData
15 AnswersFor me this error appeared immediatey after I changed the user's home directory by It can also happen because of lack of proper permission to authorized_key file in ~/.ssh. Make sure the permission of this file is 0600 and permission of ~/.ssh is 700.
Iman SedighiIman Sedighi
You will also receive 'Disconnected : No supported authentication methods available (server sent :publickey)' when you have a correct Linux user but you haven't created the file .ssh/authorized_keys and saved the public key as indicated in Managing User Accounts on Your Linux Instance
rodolkrodolk
There is another cause that would impact a previously working system. I re-created my instances (using AWS OpsWorks) to use Amazon Linux instead of Ubuntu, and received this error after doing so. Switching to use 'ec2-user' as the username instead of 'ubuntu' resolved the issue for me.
OwenOwen
PuTTY does not natively support the private key format (.pem) generated by Amazon EC2. PuTTY has a tool named PuTTYgen, which can convert keys to the required PuTTY format (.ppk). You must convert your private key into this format (.ppk) before attempting to connect to your instance using PuTTY. The steps how to perform this are described here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html This solved the problem.
René WinklerRené Winkler
Comprehensive answer is here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html Your problem can be related to incorrect login which varies depending on AMIs.Use following logins on following AMIs:
If you are using OS:
Good luck.
Witold KaczurbaWitold Kaczurba
I had the same problem, by accident mistake. I'll share it here, in case someone may have made the same mistake. Basic steps, as others described.
Good luck!
Tony XuTony Xu
in most cases, got no authentication method error when using the wrong username for logging in. But I do find something else if you still struggle with connection issue and you have tried all the options above. I created couple Linux VM and try to reproduce such connection issue, one thing I found is, when AWS asked you name your key pair, DO NOT user blank space (' ') and dot ('.') in key pair name, even AWS actually allow you to do so. ex. when I named the key pair as 'AWS.FREE.LINUX', connection always be refused. When I named as 'AWS_FREE_LINUX', everything works fine. Hope this will help a little bit.
Michael ZhangMichael Zhang
For me, I just had to tell FileZilla where the private keys were:
Rob StoeckleinRob Stoecklein
Based on multiple instances, if the key file and username are correct, this seems to occur when changing certain directory permissions associated with the root user.
Karan ModiKaran Modi
A similar issue happened with me today. I also had searched alot about this.No one help. I just made two changes and its get working properly as well.
Hope it will help you.
Asharam SeerviAsharam Seervi
I had the same problem, I used Public DNS instead of Public IP. It resolved now.
user3966432user3966432
In my case the problem was that the ppk file was placed in %USERPROFILE%Downloads instead of %USERPROFILE%.ssh folder. After I moved the file, the problem disappeared.
avpavp
I am using OpsWorks and wanted to register a new existing Linux instance from my Windows machine on AWS Cli. Frist problem was, that I had to use my Putty generated .pkk file. Second problem was that I needed to quote the absolute path to that .pkk file like that: aws opsworks register --infrastructure-class ec2 --ssh-username ec2-user --ssh-private-key 'C:key.ppk'
Sebastian ViereckSebastian Viereck
While trying to connect to a SiteGround server via Putty I had the same problem. Their instructions are pretty thorough, and must work for some people, but didn't work for me. They recommend running pageant.exe, which runs in the background. You register your key(s) with Pageant, and it's supposed to let Putty know about the keys when it tries to connect. In a couple of places I found suggestions to specify the key directly in the Putty session definition: Putty Configuration > Connection > SSH > Auth > 'Private key file for authentication', then browse to your key file in .ppk format. Doing this without running Pageant resolved the problem for me.
Community♦
Andy GieslerAndy Giesler
During ssh session my connection broke, since then I cannot ssh my SRV, I had started a new instance, and I'm able to ssh the new instance (with the same key). I mounted the old volume to the new machine, and check the .ssh/authorized_key and couldn't find any problem with permission or content.
Elia WeissElia Weiss
protected by Community♦Jun 7 '17 at 7:34Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count). Not the answer you're looking for? Browse other questions tagged amazon-web-servicessshputty or ask your own question.
0 Comments
Leave a Reply. |