• 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 Chroot Problem

L

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?
 
You must log in or register to reply here.

Similar threads

T
Question Assistance Required for curl/libcurl Vulnerabilities in Plesk Chroot
Replies
1
Views
909
scsa20
scsa20
Y
Issue NPM build actions in Deploy Actions w the Git Extension
Replies
1
Views
3K
Raul A.
R
F
Question Git commands and sub-command available in Plesk
Replies
0
Views
1K
fabrizioi
F
M
Question Which Shell Should be used for Cronjobs?
Replies
16
Views
6K
MHC_1
M
T
Resolved On MariaDB update: "mariadb-dump: Got error: 1932: "Table 'psa.module_dnssec_dnsZone' doesn't exist in engine" when using LOCK TABLES"
Replies
2
Views
1K
TalkBuildHost
T
Back
Top