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

Cronjob + Chroot Problem

futureweb

Regular Pleskian
Hello,

following Problem: Cronjob was created with BASH (CHROOT) Setting on User.
Later the CHROOT Setting got deleted (User got fully BASH Access) - but within the CRON the CHROOT definition was not deleted ... (Environment variable SHELL = /usr/local/psa/bin/chrootsh)

Only affecting my installation or a general Bug?

Andreas Schnederle-Wagner
 
Hello,

following Problem: Cronjob was created with BASH (CHROOT) Setting on User.
Later the CHROOT Setting got deleted (User got fully BASH Access) - but within the CRON the CHROOT definition was not deleted ... (Environment variable SHELL = /usr/local/psa/bin/chrootsh)

Only affecting my installation or a general Bug?

Andreas Schnederle-Wagner

sysuser has (or has no) access to server independently with cron tasks.
The users cron tasks always created under chrootsh environment for security reasons. At the same time, user may have(or have no) ssh access to server because it's independent and different permissions.
You may set all these permissions on subscription customization screen or in service plan properties:
- Management of access to the server over SSH
- Scheduler management
 
Back
Top