Cron job not running (or not doing anything)

For hosting customers · Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Good to know
  5. Still not working?

Cron jobs run as your own user, in your account's own sandbox: they see your home folder, a private temporary folder and nothing of the server's configuration. Most "not running" jobs actually run, but fail at once — and the error is not shown anywhere unless you send it to a file.

Symptoms

  • The task the job should do (emails, imports, cleanup) does not happen.
  • It works when you open the script in the browser, but not from Cron Jobs.
  • It runs at the wrong hour.

Causes

Most likely first:

  1. The command fails — a wrong path, a relative path, or a command that only works in a website.
  2. The wrong PHP — the command line PHP is not the version your website uses.
  3. The schedule is not what you think — wrong field order, or the server clock is in another time zone.
  4. The account is suspended (no cron jobs run), or the disk is full so the job cannot write.
  5. The job runs too long — it is stopped after 6 hours, or it never finishes and overlaps itself.

Fix

First: log the output

Change the command so its output and errors go to a file in your home folder. In Cron Jobs (section Advanced), delete the job and add it again with this ending:

/usr/bin/php /home/username/public_html/cron.php >> /home/username/cron.log 2>&1

After the next run, open cron.log in File Manager. The error tells you which cause it is.

1. The command fails

  • Use full paths (/home/username/public_html/…), not paths relative to the website. A job starts in your home folder.
  • The command runs with /bin/sh, not bash: avoid bash-only syntax, or run bash -c '…'.
  • The command must be one line of at most 1000 characters.
  • To call a page of your website instead of a script, use for example curl -s https://example.com/wp-cron.php > /dev/null.

2. The wrong PHP

/usr/bin/php is the server's command line PHP. To use the same version as your website, use the PHP of that version. On servers with the OpenLiteSpeed web server (the usual setup), for PHP 8.3:

/usr/local/lsws/lsphp83/bin/php /home/username/public_html/cron.php

(lsphp82 for 8.2, lsphp84 for 8.4 and so on; the PHP page shows the version of each website.) Settings from the PHP page and limits like max_execution_time apply to websites only, not to cron jobs.

3. The schedule

The five fields are minute hour day month weekday, using numbers only (for example 30 2 * * * = every day at 02:30; */15 * * * * = every 15 minutes). Names like MON or @daily are not accepted. Jobs run by the server's clock, which may be in another time zone than yours (often UTC). Test with a job every 5 minutes first.

4. Suspended account or full disk

Cron jobs stop while the account is suspended. A job that writes files fails when Disk space or Files and folders in Resource Usage is full; see Disk quota exceeded.

5. Long jobs

A cron job is stopped after 6 hours. A job that runs every minute and takes longer than a minute starts again while the previous one still runs; both count towards your account's processor and process limits. Space the schedule out or make the script stop when another copy is running.

Good to know

  • Your plan sets how many cron jobs you can have (Limit on the Cron Jobs page).
  • Mail sent by a cron job (PHP mail() or sendmail) goes out through your account and counts towards the hourly email limit.

Still not working?

Send the job's command and the contents of your log file to your host through Support.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.