my Cloud runs on a webhosting server and it seems background jobs do not run as they should. The webhosting does not have a command line pointing to the cloud installation, and I would like to have these jobs executed correctly. Is there a way to fix the execution of background jobs without command line? screenshot
Run a wget --spider https://your-nextcloud-server/cron.php in a cron job on any server.
Yes, if you call it in a browser or via curl, but the command posted by @theking2 won’t give this message, and it will trigger the background job to run, even if it’s set to system cron.
You can easily test this by going to “Administration Settings” → “Basic Settings” in your Nextcloud, then sending the command and refreshing the page. If successful, the message under background jobs should change from “Last job ran X minutes ago” to “Last job ran a few seconds ago”.
Or you could set the background jobs to Webcron instead of system cron, which would be the correct setting for this scenario, and which will give you a success message when you call it via curl or browser.
true when setting background settings to webcron, https://your-nextcloud-server/cron.php will return ‘success’. However my settings displays some background jobs have not been executed since one year.
That is weird. Could you check the logs? I see this when running the cron job:
83.97.87.43 - - [27/Apr/2025:16:12:49 +0200] “GET /cron.php HTTP/1.1” 200 675 “-” “Mozilla/5.0 (X11; Linux x86_64; rv:137.0) Gecko/20100101 Firefox/137.0”
thank you for helping. Webcron seems to take some time, and after a while overwiew shows much less errors. Basic settings however still show 'some jobs haven’t run since 1 year. Protocol looks like this:
I got cron (recommended) working on a container in OMV.
I had to add this to crontab -e
*/10 * * * * sudo docker exec -u www-data nextcloud php /var/www/html/cron.php
where the container for nextcloud was called, well nextcloud
See my complete instructions for omv and nextcloud on
https://github.com/theking2/srv-nas-pi