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

Issue Composer Not Found PHP

Actually, the most secure option is the chrooted shell. This jails the user to his own webspace. A webspace user should not be able to access anything outside of his own webspace. If you provide full access through another shell type, hackers will use this opportunity to install malware on your server. This will occur through unsecure or malicious plugins of the website software. Enabling full shell access can also lead to a total desaster as that user can then remove files and directories.
 
Ok, so I set up chroot, as I guessed, and then use the su command to log into root.
But at this point, couldn't hackers do the same?
 
When you login to a shell from within a subscription, your user account that logs in is the subscriber. When you chroot the environment, the subscriber is jailed to the subscription. The subscriber cannot escalate privileges to root.
 
Ok and here we are, but maybe you don't understand me?
I need to disable root, so first I need to create a user from which I can use the su command........
 
I suggest adding a new user using the Linux commands:
# adduser anotheruser

Next, set a password:
# passwd anotheruser

And add the new user to the wheel group that allows the user to su to root:
# usermod -aG wheel anotheruser

That should be enough to ssh to the server with the new user and become root.
 
Back
Top