Hello,
The fact that is was working with no shell access for the subscription (/bin/false) on Debian 10/Plesk 18.0.70 makes me wonder what has been changed, either at the system level or at the Plesk level, to make it necessary to enable SSH access in order for scheduled tasks to work...
Hello, it's my mistake I misread your message and only change the /bin/bash (chrooted) to /bin/bash in the Tool & Settings menu. Here is all I tested :
First I tested with :
Tools & Settings > Scheduled Tasks > Settings > Crontab shell > /bin/bash (chrooted)
Subscriptions > example.com >...
To be precise, I first switched the Planified Task "global" settings to /bin/bash.
Then, after executing the task, I am getting the same error on the concerned website for both wget commands (without and with --secure-protocol tlsv1).
But on a new Plesk website that I created, it could now...
Thank you for your proposition, unfortunately I am getting the same error.
[2025-10-06 08:47:25.338] 3015665:68e365fd1a96f ERR [panel] Task failed: id=49645, pid=3015665, type=scheduler-run-task, error=PleskUserException: Scheduled task failed
file: /opt/psa/admin/plib/Scheduler/RunTask.php...
Hello @Sebahat.hadzhi thank you for your fast answer.
The SSH Access for the website's user was indeed set on "Forbidden". (in /etc/passwd the user was on /bin/false)
After changing it to /bin/bash (chrooted), the user is on /opt/psa/bin/chrootsh.
Executing the planifed task is still giving me...
Hello.
Quick summary :
I upgraded a Debian 10 server to Debian 11 and then to Debian 12 using this Plesk documentation : https://support.plesk.com/hc/en-us/articles/12377714344983-How-to-perform-dist-upgrade-procedure-on-Linux-server-with-Plesk
While the server was on Debian 10 with Plesk in...