Cronjobs not running

  • Resolved fresch

    (@fresch)


    1 year, 1 month ago

    I’ve had issues with my wordpress site since the beginning, and maybe I’m misunderstanding how cronjobs work, or misconfigured wordpress.
    Since the start I’ve had some scheduled item keep missing its schedule, and after cancelling it, a new one would pop up. After following it, I found that all my cronjobs don’t seem to be working.

    I’ve also had issues with all my scheduled posts missing their scheduled date, so I’ve had to get a plugin installed that posted them when the next viewer came to the site.

    I’ve attached images of what I see.

    Sorry for any stupid things I might say, I recently moved from wordpress.com to a custom host, but decided to stick with wordpress, and am really new to all of this web hosting stuff.

    View post on imgur.com

    • This topic was modified 1 year, 1 month ago by fresch.
Viewing 11 replies - 1 through 11 (of 11 total)

  • Cronjobs are triggered by calls in the frontend. If the frontend is not called, they are not executed. Is your frontend publicly accessible?

    This behaviour of the cronjobs can also be changed to system cronjobs. Then they are executed by a cronjob in the hosting – and thus possibly more regularly. To do this, you need to set the DISABLE_WP_CRON constant to true in wp-config.php and set up a cronjob in the hosting. See: https://kinsta.com/knowledgebase/disable-wp-cron/

    Thread Starter fresch

    (@fresch)

    I’m not too sure with what you mean with my “frontend”, but yes, the site is public and accessible by all. I’ve had a handful of visitors, on average I get between 2 to 5 a day.

    The problem with setting the hosting to activate crons is that the plan I’m on doesn’t support cronjobs. Is there potentially any plugin that could assist instead? Or is it a fundimental issue?

    Then you probably have some other problem that is preventing the cronjobs from running. Take a look under Tools > Site Health. Is there anything there?

    Thread Starter fresch

    (@fresch)

    there are 5 errors.

    View post on imgur.com
    • This reply was modified 1 year ago by fresch.
    surviving404

    (@surviving404)

    Hey Hey,

    I saw you are using infinityfreehost. Free hosting companies always have a problem with cron jobs running freely since they can add load on servers too.

    Last year (Aug. 2023) Infinityfreehost Announced that they will be disabling cronjobs.
    You can read more about it HERE.

    Thread Starter fresch

    (@fresch)

    ah, I can’t believe I overlooked that. So sorry for the trouble.

    Guess there is no alternative but to either get premium hosting or to manually perform the scheduled actions.

    surviving404

    (@surviving404)

    @fresch

    It’s fine. I am glad we found the actual issue.

    Thread Starter fresch

    (@fresch)

    I’d assume the remaining issues such as loopback requests are also from the host and aren’t that vital, right?
    I mean, the site I’m hosting is a tiny one with little daily traffic anyways, so it’s not that big a deal if things are a little janky…

    surviving404

    (@surviving404)

    yes I visited your site and did not experience any bad behaviour, but you as admin might.

    threadi

    (@threadi)

    Interesting article, but I don’t think it has anything to do with WordPress cronjobs. The hoster has deactivated the system crons, for good reason as they also describe. However, you cannot influence or switch off the WordPress cronjobs from the outside, as this works completely differently. To deactivate it, an entry in the wp-config.php of the respective WordPress installation is necessary, as described above. Or you can block the requests to wp-cron.php via a firewall on the server. I’m still not sure whether this is an explanation. I think an enquiry to their support should provide an explanation.

    Thread Starter fresch

    (@fresch)

    huh. Interesting.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Cronjobs not running’ is closed to new replies.

Tags