Does anybody know why all the Chrome jobs would be missing I’m assuming they have been seen for quite some time I just now noticed this.
Is there a way to be able to restore them to default?
If not maybe a picture of what’s supposed to be there and I can rebuild it? I was wondering why backups stopped working. It looks like this happened sometime last March, March of 2025.
OK I see them there but they’re not in the normal place, They should be under Cron jobs and backups should be working.
Again, Need my backups to be working and they’re not working so regardless of wherever the jobs are they’re not working and I don’t have any control over them. Backups have not run since early 2025.
OK so this shows there’s not enough space, That would do it but I gave the web server 50 gigs and I’m nowhere near that on websites I’m not sure why I am out od space.
root@webserver:~# v-backup-user admin
Error: not enough disk space available (7620 mb) to perform the backup of admin. ( 8629 mb * 2 = 17258
root@webserver:~# df -h --total
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 794M 800K 794M 1% /run
/dev/sda1 48G 39G 7.5G 84% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 794M 0 794M 0% /run/user/0
total 58G 39G 17G 70% -
/dev/sda1 is using 48 gb
Here’s the websites and sizes for them I don’t see how any of that would total up to 50 gigs? And databases are only using maybe one gig.
Because since version 1.9.x of Hestia Control Panel, maintenance jobs are executed by the user hestiaweb (not the administrator user like in older versions), and you can see those jobs where I mentioned earlier.
The users’ cron jobs section only shows jobs that users have added themselves. If you haven’t added any for the admin user, you won’t see any… and the same applies to the rest of the users.
The reason it doesn’t work is that one of your sites may have large files, and it needs to calculate the total capacity. If the capacity is insufficient, it will not back up. Specifically, you can add a log record to the backup script to find out whether it is working and, if it is working, why it fails.