The serial console connects to your instance without requiring a working network connection. The serial console helps you troubleshoot boot issues, network configuration, and SSH configuration issues. If you’ve turned on EC2 Serial Console for Linux, then you can use the serial console to troubleshoot supported Nitro-based instance types. There are four methods for verifying permissions and directories on the instance: For more information, see How do I add new user accounts with SSH access to my Amazon EC2 Linux instance? There are permissions issues on the instance or you're missing a directory If the user trying to access the instance was deleted from the server, add the user back as a new user.

The user trying to access the instance was deleted from the server or the account was locked Resolution You're using the incorrect user name for your AMI when connecting to your EC2 instanceįor a list of valid user names, see Error: Server refused our key or No supported authentication methods available. For more information, see the Dependency failed errors section in Why is my EC2 Linux instance not booting and going into emergency mode?

The operating system couldn't mount ( /etc/fstab) home directories.

Now I can't access my instance using SSH. For more information, see I made changes to my EC2 instance's sshd_config file.

SSH server settings in /etc/ssh/sshd_config were changed.

For more information, see the Verify that the private key is correct section in Why am I receiving 'imported-openssh-key' or 'Putty Fatal Error' errors when connecting to my Amazon Elastic Compute Cloud (Amazon EC2) Linux instance?

You're using the incorrect private key file when connecting to your EC2 instance.

There are permissions issues on the instance or you're missing a directory.

The user trying to access the instance was deleted from the server or the account was locked.

The usual user names are ec2-user, ubuntu, centos, root, or admin.

You're using the incorrect user name for your AMI when connecting to your EC2 instance.

The following are some common reasons that you might receive this error: There are multiple reasons why an SSH server (sshd) refuses a private SSH key.

Server refused our key filezilla