• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Question Sudo user doesn't have permission to use sudo

zigojacko

Basic Pleskian
Server operating system version
CentOs 7.9
Plesk version and microupdate number
18.0.45
I've granted sudo access manually to the main subscription user within Plesk yet when I do su username, it doesn't have access to use the sudo command, for example:-

sudo: command not found

I'm not sure if there is something I have missed. Surely it is possible to do this?
 
Permission and access are separate things. You may have permitted the user to use sudo, but that doesn't help if the user can't access the sudo binary.

Try su - username, does that change anything?

Is the subscription user in a chroot jail?
If yes, I strongly recommend against putting sudo in there because it defeats the purpose of the jail.
 
Permission and access are separate things. You may have permitted the user to use sudo, but that doesn't help if the user can't access the sudo binary.

Yes, this is the exact case in this scenario I now know.

Try su - username, does that change anything?

If I do that logged in as root, then it does switch shell to the user but there is no difference at all with what they can or can't run.

Is the subscription user in a chroot jail?
If yes, I strongly recommend against putting sudo in there because it defeats the purpose of the jail.

Yes, the user is in this one according to /etc/passwd - /usr/local/psa/bin/chrootsh
 
Back
Top