Error No supported authentication methods available on AWS

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.

Disconnected : No supported authentication methods available (server sent :publickey)

The error is familiar from when I set up the connection almost a year ago. If you're setting up AWS SSH for the first time, these address the most common problems:

• Wrong username: Disconnected : No supported authentication methods available (server sent :publickey)
• Incorrect .ppk file: Unable to connect to amazon server using putty

However, the only thing I could think that would impact a previously working system is:

• Wrong IP: Restarting an AWS instance (or creating an image) is not guaranteed to keep the same IP address. This would obviously have to be updated in putty.

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:

/home/ec2-user/ - 700
/home/ec2-user/.ssh/ - 600
/home/ec2-user/.ssh/authorized_keys - 600

Answer 1

Your problem can be related to incorrect login which varies depending on AMIs. Use following logins on following AMIs:

• ubuntu or root on ubuntu AMIs

• ec2-user on Amazon Linux AMI

• centos on Centos AMI

• debian or root on Debian AMIs

• ec2-user or fedora on Fedora

• ec2-user or root on: RHEL AMI, SUSE AMI, other ones.

If you are using OS:

• Windows - get PEM key from AWS website and generate PPK file using PuttyGen. Then use Putty to use the PPK (select it using left-column: Connection->SSH->Auth: Private key for authorization)

• Linux - run: ssh -i your-ssh-key.pem login@IP-or-DNS

Good luck.

Answer 2

Diff from other answers above:

I received this authentication error- No supported authentication methods available (server sent: publickey) repeatedly while connecting to my google cloud platform and connecting thru FileZilla, even when I had spent hours checking my each of my steps again and again by watching diff youtube videos and reading articles over Digital Ocean and similar.

But finally succeeded in a second, when I went into GCloud> Desired Project> Compute Engine> Metadata (in the left bar)> Metadata (in the main Pane)> and there I changed ' enable-oslogin' from 'True' to 'False'.

I had, sometime in my overzeal, had put in this key yesterday while doing something else.

You can even check out the details from the AWS Training.

Comments

Hey @Bathinda, I am not pretty sure about GCP, but yes maybe this could also be the case in AWS.