• 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.

SSH Access Plesk 12 (user based) doesnt work?

Maik

New Pleskian
Hi,

for the first Time now i was trying to grant a User SSH Access via Plesk Panel (chrooted/non chrooted), but it doesnt work out really .. Abonnement > Edit Permissions > Allow Access chrooted (or non chrooted doesnt matter) doesnt change anything when im trying to Login with the created System User by Plesk. Login doesnt work!

Regular SSH Login as root works as always without any problems, but even via "su user" it doesnt works.

Till now i didnt had any Problems with my VPS Setup based on Centos 6.6 and Plesk 12.0.18 #50.

Any recommandations how to solve this Issue?

Thanks for your Help!
 
What do you mean exactly "it doesnt work"? What sort of error message do you have? Incorrect password or something else? Have you tried troubleshoot it? Any results?
 
Hi,

there is no Error Message ... This is the output from /var/log/secure as example:

Single sign on:

Code:
Jun 16 13:10:07 host sshd[15008]: pam_unix(sshd:session): session opened for user mypleskuser by (uid=0)
Jun 16 13:10:07 host sshd[15008]: pam_unix(sshd:session): session closed for user mypleskuser

or su via root

Code:
Jun 16 13:32:00 host su: pam_unix(su:session): session opened for user mypleskuser by root(uid=0)
Jun 16 13:32:00 host su: pam_unix(su:session): session closed for user mypleskuser

Greetz
 
It's really difficult to help somehow without any details in scope of forum's discussion.
I can only recommend to create a request to support team to do in-depth investigation to find the reason and to fix it. Please create a ticket to support at https://www.odin.com/support/request/ .
You may have free support, please check what kind of Plesk license you use for available support options at http://kb.odin.com/en/121580 .
If there’s no free support in your case, you can order Plesk per-incident support at http://www.odin.com/support/buy-support/ Support team will contact you as soon as purchase is processed, and they will do the best to resolve it.
If it is found that your problem was caused by product bug w/o available solution or workaround from Parallels, then your purchase will be re-funded.
 
Back
Top