• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved SSH access

Jürgen_T

Regular Pleskian
(Server: Ubuntu 18.04 and Plesk Osidian)
I managed to have a ssh access to my server for user root with keys and without password. Next step was to enable a root access for the user "admin_XXX" which are usually become installed during the first setup of Plesk.
This was done by Plesk Panel /webspace access / ssh allowed /bin/sh. Works fine with the given Password.
Now, I have acces via ssh with keys as root but could not manage right now to get ssh access for the user "admin_XXX" with keys, too.
Question, what are the steps to enable also keys for the admin_XXX-user different from user root in Plesk as it does not reside in the home-directory?
 
Back
Top