Rootinsertkvmipheres Password Permission Denied Please Try Again

Introduction

The SSH Permission denied fault appears afterward permission-related settings are modified on the SSH server. Usual scenarios include a new package installation or the creation of new users.

In this tutorial, you will learn how to troubleshoot the SSH Permission denied error and reconnect to your SSH server.

Prerequisites

• SSH client on the local auto and SSH server on the remote arrangement
• A user account to access the remote server (for password-based login)
• A user account withsudo orrootprivileges

What is Causing SSH Permission Denied (publickey,gssapi-keyex,gssapi-with-mic)?

The SSH Permission denied error appears when trying to SSH into a server:

          Permission denied (publickey,gssapi-keyex,gssapi-with-mic)        

Following the Permission denied statement, the bracket contains the attempted hallmark methods that failed at the initiation of the connection. The error suggests that the public key is the result, which is misleading.

I reason for the error may be sshd_config , the file that contains SSH server configuration. The other possibility is that the authorized_keys file has insufficient permissions. This file contains the listing of public keys for the clients allowed to SSH into the server. Consequently, the system's inability to read from the file results in the Permission denied error.

How to fix SSH Permission denied

Both solutions incorporate steps you demand to perform on the server-side. Showtime by opening the final on your server and proceed with i of the solutions below.

Solution 1: Enable Password Authentication

If you want to employ a password to access the SSH server, a solution for fixing the Permission denied error is to enable password login in the sshd_config file.

To do this, open the file in a text editor.  This case uses the nano editor:

          sudo nano /etc/ssh/sshd_config        

In the file, find the PasswordAuthentication line and make sure information technology ends with yes .

Discover the ChallengeResponseAuthentication option and disable it by calculation no .

If lines are commented out, remove the hash sign # to uncomment them.

Save the file and get out.

Restart the SSH service by typing the following command:

          sudo systemctl restart sshd        

Solution 2: Change File Organisation Permissions

Using the password-based login as the SSH authentication method is not recommended due to security concerns. Therefore, the following solution may be preferable since it troubleshoots the public key authentication method.

First, open the sshd_config file using a text editor:

          sudo nano /etc/ssh/sshd_config        

In the file, make certain the following options are set every bit follows:

          PermitRootLogin no PubkeyAuthentication yes        

Note: The steps above are considered all-time security practices. If you need to use root login, set the relevant line to yeah .

Comment out the GSSAPI-related options by adding the hash sign at the beginning of the line:

          #GSSAPIAuthentication yes #GSSAPICleanupCredentials no        

Also, brand certain the UsePAM line is set to yes :

          UsePAM yes        

Save the file and restart the sshd service:

          systemctl restart sshd        

Now navigate to your abode binder and check the permissions:

          ls -ld        

If your owner permissions are not set to read, write, and execute ( drwx------ ), utilize the chmod control to modify them:

          chmod 0700 /home/[your-username]        

Now go to the .ssh folder and recheck the permissions:

          ls -ld        

This directory should also have read, write, and execute permissions for the file owner. To enforce them, apply chmod over again:

          chmod 0700 /home/your_home/.ssh        

The .ssh folder contains the authorized_keys file. Check its permissions with:

          ls -ld authorized_keys        

The file owner should have read and write permissions. To set them, use:

          chmod 0600 /home/[username]/.ssh/authorized_keys        

Now attempt logging in with the key pair once again. The output below shows a successful login attempt.

Decision

This tutorial covered the steps necessary to troubleshoot the SSH Permission denied (publickey,gssapi-keyex,gssapi-with-mic) mistake. By completing the steps in the guide, y'all should fix the fault and successfully SSH into your server.

Was this article helpful?

Yes No

rileysinince.blogspot.com

Source: https://phoenixnap.com/kb/ssh-permission-denied-publickey

Share this post