Exact same issue.
So, after that I tried to run as sudo -su hestiaweb (/var/spool/cron/crontabs/hestiaweb is owned), and rerun:
/usr/local/hestia/bin/v-add-cron-hestia-autoupdate, then it gives me permission denied at line 10 & 126:
/usr/local/hestia/func/main.sh: line 10: /usr/local/hestia/conf/hestia.conf: Permission denied
/usr/local/hestia/func/main.sh: line 10: /usr/local/hestia/conf/hestia.conf: Permission denied
& that cron system is not enabled…
Error: CRON_SYSTEM is not enabled
/usr/local/hestia/func/main.sh: line 126: /usr/local/hestia/log/error.log: Permission denied
How to solve this?
Update: Seems this is a bug of some sort, and will be fixed in 1.9.3:
Another update: I fixed it per the code change here. Thanks for that.
Earlier line 65 was echo "$min $hour * * * sudo /usr/local/hestia/bin/$command" > "/var/spool/cron/crontabs/hestiaweb", and changing it to
sed -i -e "\$a$min $hour * * * sudo /usr/local/hestia/bin/$command" "/var/spool/cron/crontabs/hestiaweb" and then running the bin again, solved it.
You can check before & after with v-list-sys-hestia-autoupdate.
Final result: AUTOUPDATE: Enabled
