• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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