• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk and SSH authorized_keys

S

saschahb

Guest
hi,

normally logging into the ssh-account without password but with ssh-publickey does not work because the home directory of each plesk user is write-protected.

But for all of us who want to provide this feature to users I will show you a little quick and dirty workaround. Perhaps you'll be happy with it ;)

- Edit /etc/ssh/sshd_config (this is the debian sshd-config file. Perhaps it is called a little bit different in other linux distros)
- Add this line or change on existing one to this:
AuthorizedKeysFile %h/private/.ssh/authorized_keys
(the .ssh directory isn't expected within the root-homedir anymore. Now sshd searches within the private directory of each user)
- save and restart the sshd

to add an authorized keys file all users have to do the following:
- login to their account
- cd private
- mkdir .ssh
- chmod og-xrw .ssh (important!)
- now they have to copy their authorized_keys file to this directory

voila! it is done...

greets
Sascha
 
Hey indeed !! That's some great info !

Thanks for sharing that with the rest :)

I came across the same problem .. but never looked further to solve it.

Thanks again mate !
 
Back
Top