{"id":18111,"date":"2022-08-18T06:26:52","date_gmt":"2022-08-18T06:26:52","guid":{"rendered":"https:\/\/linuxways.net\/?p=18111"},"modified":"2022-09-05T16:52:18","modified_gmt":"2022-09-05T16:52:18","slug":"how-to-fi-ssh-permission-denied","status":"publish","type":"post","link":"https:\/\/linuxways.net\/de\/linux-commands\/how-to-fi-ssh-permission-denied\/","title":{"rendered":"How to Fi SSH Permission Denied"},"content":{"rendered":"

How to Fix ssh Permission Denied<\/strong><\/h2>\n

Working with SSH is time-saving and secure but can get frustrating when you get the ssh permission denied error and can\u2019t figure out what is causing the error.<\/p>\n

With ssh, you can easily login into your remote server and perform all activities, including installing software and working with files.<\/p>\n

If you\u2019ve installed SSH on your client and server but still have issues accessing the server, the problems result from the configurations in most cases. Few rules need to be in check for the smooth running of SSH. This guide covers how you can easily fix the SSH error in several ways.<\/p>\n

What Is SSH?<\/strong><\/h2>\n

Secure Shell (SSH) is a protocol that allows a client machine to connect to a Linux server remotely and securely using a text-based interface. Upon a successful connection, a shell session will open from where you can work with your server.<\/p>\n

What Causes the ssh Permission Denied Error?<\/strong><\/h2>\n

The common reasons include:<\/p>\n

    \n
  • Incorrect SSH public key contained in the authorized_keys <\/strong>file<\/li>\n
  • Incorrect file permissions<\/li>\n
  • Misconfiguration in the SSH server config file<\/li>\n<\/ul>\n

    Fixing the error is straightforward and we will consider various methods you can use.<\/p>\n

    How to Resolve the SSH Permission Denied Error<\/strong><\/h2>\n

    If you get an error like the one below, we have a solution for it.<\/p>\n

    <\/p>\n

    Solution 1: Enable Password Authentication<\/strong><\/h3>\n

    You first need to check the PasswordAuthentication <\/strong>and ensure it is enabled.<\/p>\n

    You need to open the sshd_config<\/strong> file on your server using an editor. In our case, we are using nano editor and the command would be:<\/p>\n

    $ sudo nano \/etc\/ssh\/sshd_config<\/pre>\n
    Once opened, locate the PasswordAuthentication <\/strong>line and ensure it is set to end with yes.<\/strong><\/p>\n
    <\/p>\n
    Also, below the PasswordAuthentication, ensure the ChallengeResponseAuthentication <\/strong>is disabled and ends with a no.<\/strong><\/p>\n
    Once you make the changes, save your file and exit. You must restart the ssh service using the command below.<\/p>\n
    $ sudo systemctl restart sshd.service<\/pre>\n
    <\/p>\n
    Next, proceed to try the connection again.<\/p>\n
    <\/p>\n
    If the solution doesn\u2019t work for you, try the others below.<\/p>\n
    Solution 2. Check Other Configurations<\/strong><\/h3>\n
    Your sshd_configuration file determines if the ssh connection goes through or not. Therefore, everything needs to be checked to fix the ssh permission denied error. For this solution, you must locate various lines and ensure they match the ones listed below.<\/p>\n
    First, open the configuration file as we did before.<\/p>\n
    $ sudo nano \/etc\/ssh\/sshd_config<\/pre>\n
    Once opened, locate and edit the lines below to ensure they match. Most of them are commented but you can un-comment them by deleting the # before them. From there, you can edit and align them to match the ones below.<\/p>\n
    PermitRootLogin no\r\n\r\nPubkeyAuthentication yes\r\n\r\nUsePAM yes<\/pre>\n
    <\/p>\n
    Finally, save and exit the file. Then, restart sshd<\/p>\n
    $ sudo systemctl restart sshd.service<\/pre>\n
    Your ssh connection should now successfully log in to the server.<\/p>\n
    Solution 3. Change File Permissions<\/strong><\/h3>\n
    The owner permissions of your home directory should be set to read, write, and execute. You can verify so using the command below.<\/p>\n
    $ ls -ld<\/pre>\n
    If not set to drwx——, <\/strong>set them using the chmod <\/strong>command.<\/p>\n
    <\/p>\n
    $ chmod 0700 \/home\/your-username<\/pre>\n
    Also, the owner permissions for the authorized_keys<\/strong> in the .ssh <\/strong>directory should be set to read and write.<\/p>\n
    Verify so using the command below.<\/p>\n
    $ ls -ld authorized_keys<\/pre>\n
    If not properly set, use the command below.<\/p>\n
    $ chmod 0600 \/home\/your-username\/ .ssh\/authorized_keys<\/pre>\n
    Once you restart sshd, your ssh will start connecting normally and will fix the ssh permission denied error.<\/p>\n
    Conclusion<\/strong><\/h2>\n
    SSH is a must-use when working with a remote Linux server. There are other alternatives, but the protocol offers you a secure remote login. While using SSH, you can encounter the permission denied error which mainly results from a misconfiguration. We\u2019ve seen the various options you can use to resolve this and any of them or at least one will work for your case.<\/p>","protected":false},"excerpt":{"rendered":"
    While using SSH, you can encounter the permission denied error which results from a misconfiguration. The options you can use to resolve this is discussed here.<\/p>","protected":false},"author":104,"featured_media":18161,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1049],"tags":[],"class_list":["post-18111","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux-commands"],"_links":{"self":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/18111","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/users\/104"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/comments?post=18111"}],"version-history":[{"count":1,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/18111\/revisions"}],"predecessor-version":[{"id":18163,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/18111\/revisions\/18163"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media\/18161"}],"wp:attachment":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media?parent=18111"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/categories?post=18111"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/tags?post=18111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}