I performed a fresh installation of HestiaCP with version 1.9.2, but found that my Cron on the Cronjobs Panel is not working. On another server that initially used version 1.8.12 and was updated to 1.9.2, the cron job runs as it should. Then I checked the user with the command less /etc/passwd and found a difference user between a fresh install of 1.9.2 (hestiaweb & hestiamail) and an upgrade from 1.8.12 to version 1.9.2. Where the Cronjobs Panel uses the sudo command. Is there a solution to this problem?
1 Like
There are moved to Server Setting → Panel cronjobs.
The “admin” user can’t execute sudo command any more on new installs
I have found the location of the Cronjobs Panel, but for some reason, cron is not running as it should. For example, backups are not being executed according to the scheduled time in cron. However, if executed manually (sudo /usr/local/hestia/bin/v-backup-users) with the root or hestiaweb user, the backup process can be completed. The problem also arises when the
Create Backup button is pressed; no backup process occurs as expected. I am using Ubuntu OS 22.04.5 with Hestia Control Panel v1.9.2 (fresh install)
I figured it out! The crontab was using UTC, even though I’d changed the server’s time to UTC+8 (the right time zone). That’s what was throwing everything off. Thanks for the response @eris