From the case notes,
I understand you are getting error while connecting to the EC2 instance from Filezilla app and the error message is
No supported authentication methods available (server sent: publickey,gssapi-keyex,gssapi-with-mic)
Error: Could not connect to server”.
I did not find any EC2 instances or IP address listed in the case notes, I verified your account and found an EC2 instance “i-085c8a8e45e58c98a” is hosted in ap-south-1 region with CentOS, configured with elastic IP address “184.108.40.206”.
I assume, you are trying to connect with this EC2 instance.
Please correct me if my understanding and assumption differ from the issue
1) First of all, I tried testing the connectivity to port 22 for the elastic IP address “*****” and able to reach the port successfully with telnet command.
(Command logs for your reference below)
$ telnet *** 22 Trying ***... Connected to ****. Escape character is '^]'. SSH-2.0-OpenSSH_7.4 ^]
q => This clarifies the instance is reachable on port 22.
2) I suggest you to crosscheck the SFTP Filetransfer configuration for FileZilla following the below AWS article. I had a feel the issue is due to the "the SSH private key into the FileZilla connection." By reconfiguring it with below reference article you may be able to overcome the error.
3) If it fails, I suggest you to test the SSH/SFTP connectivity with a different app like from command line, Putty or WinSCP with the same credentials or key that is used in filezilla, thereby we can isolate the issue i with FileZilla client or at the server end. below reference article will guide you in connecting to the server with Puty or WinScp utility.
3) If the SSH connectivity fails with above utilities, Please share us the output of below command executed from a command line interface.(If you are using windows, run it from power shell or equivalent command line utility)
$ssh -vvv -i keyfile.pem [email protected]******
=> Replace the keyfile.pem with your private key file name and centos with the username you are trying to connect.
=> Based on my assumption, I provided the IP address of the EC2 instance, if incorrect change it with the right IP address.
4) If the connection succeeds with above command, then you have to review the connection settings in filezilla app for addressing the issue. I found below forms from filezilla that depicts our issue.
Kindly note, FileZilla is a third party application and Application level troubleshooting falls out of scope of support that AWS Premium Support Provides.
This is due to the fact that AWS Premium Support engineers don’t have an expertise in handling such situations, However, I totally understand the situation and hence, I’ll try to assist you to the best of my abilities on the best effort basis.
I hope the above information will help you in addressing the issue, please share us the above logs in order to deep drive our troubleshooting if the ssh connectivity fails from command line.