ssh permission denied publickey gssapi keyex gssapi with mic. The SSH permission denied Error appears after changing the permission-related settings on the SSH server. Typical scenarios include installing a new package or creating new users.

In this discussion group, you will learn how to fix the SSH permission denied Error and reconnect to your SSH server.

previous requirements

  • SSH client on the local engine and SSH server on the remote system
  • A user account to access the distant server (for a password connection)
  • A user account with sudo or root rights

What causes SSH permission denial (public key, gssapi-keyex, gssapi-with-mic)?

An SSH permission denied Error appears when trying to SSH into a server:

After the Permission Denied statement, the parentheses contain the attempted authentication methods that failed to establish the connection. The Error submits that the public key is the problem, which is misleading.

One of the reasons for the Error may be sshd_config, the file that contains the SSH server configuration. And The other possibility is that the authorized_keys file has lacking agreements. This file holds the list of public keys of clients authorized to connect in SSH to the server. Hence, the inability of the system to read the file results in the Permission Denied Error.

How to Resolve SSH Permission Denied (public key) Error

SSH keys are an excellent method to authenticate SSH sessions without the need for a password at each login. However, like all technologies, SSH keys are imperfect, and you may encounter errors when using them. One of the most common errors when working with SSH keys is the Permission denied (public key) error.

1: Authorized Keys and Directory Permissions

One of the causes of this Error could be the permissions and ownership configured for the .ssh directory and authorized_keys file.

o resolve this issue, set the .ssh directory permissions to 700 and the authorized_keys permissions to 6oo.

sudo chmod 700 ~/.ssh sudo chmod 600 authorized_keys

2: SSH Incorrect Configurations

Another common cause of the public key Error is an incorrect configuration in the sshd_config file. To resolve this issue, edit the /etc/ssh/sshd_config file and change the following entries.

#PermitRootLogin prohibit-password
#PasswordAuthentication yes

The above entries should be as shown below:

PermitRootLogin yes

PasswordAuthentication yes

Save the configuration and restart the service:

Sudo systemctl restart sshd.service

3: Missing Keys

Another possible cause of the public key Permission denied Error could be missing keys from your local machine. If you have your keys added to the authorized_keys file of the server but are missing the corresponding private keys, this may cause an error.

To resolve this issue, edit the ssh configuration file, disable public key authentication, and enable password login as follows:

PubkeyAuthentication yes
#PasswordAuthentication yes

Change To the following entries:

#PubkeyAuthentication yes
PasswordAuthentication yes

Once you edit the configuration, save the file, and restart the SSH service:

Sudo systemctl restart sshd.service

If you are confident that your keys have been compromised, you can remove them from authorized_keys or add a specific key to the revoked list in SSH.

Why is Permission denied for SSH?

“Permission denied (public key)” and “Authentication failed, approval denied” errors occur when: You try to log in using the wrong username for your AMI. The file permissions in the operating system are incorrect on the instance. The bad SSH public key file (.pub) is in the authorized_keys file.

How to Fix SSH Permissions Denied in Windows?

ssh permission denied publickey gssapi keyex gssapi with mic If you want to use a code word to contact the SSH server, a workaround to fix the Permission Denied Error is to enable password login in the sshd_config file. In the file, find the line PasswordAuthentication and make sure it ends with yes. Look for the ChallengeResponseAuthentication option and disable it by adding no .

Why is my SSH key denied?

The GitHub Permission Denied (Public Key) error is usually caused by one of three issues: You used the wrong email address in the GitHub SSH URL. You haven’t configured your public SSH key in your GitHub account. You need to create GitHub SSH keys for use by the secure shell.


ssh permission denied publickey gssapi keyex gssapi with mic After the Permission Denied statement, the parentheses contain the authentication attempts that failed when starting the connection. The error suggests that the public key is the problem, which is misleading.The SSH Permission denied error appears after permission-related settings are modified on the SSH server. Usual scenarios include a new package installation or the creation of new users.

Both solutions contain steps you need to perform on the server-side. Start by opening the terminal on your server and proceed with one of the solutions below.