Yes that’s a bit strange because on the other same server, from same company with same install, it works
Is there a way maybe to run that with a batch script or another “patch”
You can add the cron job 18 00 * * * /usr/local/hestia/bin/v-backup-users to root user… as root crontab -e
If you do that, remember to remove the cron job from hestiaweb user.
Thank you so much, this way it worked!
You’re welcome.
Anyway, keep in mind that this is a workaround, if cron jobs for hestiaweb are not working then there is a problem.
I’m going to send you a private message to see if we can find the root cause.
1 Like
Just for the record.
This evening, I have been looking into the issue with @botefa, and we have fixed it. The problem is a bug in the way Hestia modifies the crontab of the hestiaweb user.
The real issue is that Hestia does not delete the backup file it creates and cron only reads the hestiaweb.vst.back file instead of reading the new hestiaweb.
I have opened a PR to fix the issue:
7 Likes
Yes, I have also encountered this issue. A few days ago, after installing it on my new server (including editing the time via the web on the old server, which also failed to work properly), the automatic backup has not been functioning correctly. Today, I tried modifying the file in the PR first to see if it will work properly tomorrow morning.
PR is working!!! ty @sahsanu
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.