• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Chroot Problem

lindakind89

New 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?
 
It is unclear whether you are saying, that without external intervention the user gained access to the full shell, or whether this was deliberately configured and you are wondering why the cron job did not gain access, too.
Could you please clarify what exactly you are expecting and what is happening instead?
 
Back
Top