WHMCS Cron Not Running: 11 Fixes for 8.13 and 9.x (2026)
Most WHMCS cron failures come from a wrong schedule, HTTP calls blocked in WHMCS 9, a bad cron.php path or command-line PHP that differs from web PHP. Here are 11 fixes.
When the WHMCS cron is not running, invoices stop generating, overdue services stay active, card payments are not attempted and tickets are not escalated. The cause is almost always one of the eleven fixes below: the cron runs too rarely, calls cron.php over HTTP (blocked by default since WHMCS 9.0), points to the wrong path, or runs a command-line PHP that differs from your web PHP. This guide is for self-hosted WHMCS 8.13 and 9.x installs; WHMCS Cloud manages the cron for you.
Key takeaways
- WHMCS needs one system cron that runs
crons/cron.phpevery five minutes, or at least once per hour. Daily tasks run during the Time of Day hour set in Automation Settings. - Copy the exact command from
Configuration > System Settings > Automation Settingsby clicking the first badge. - In WHMCS 9.0 and later, HTTP requests to
cron.phpreturn403 Access Deniedunless the caller's IP is allowlisted. Run the cron from the command line instead. - The cron's PHP must match the web PHP version and include ionCube Loader, the required extensions and a
memory_limitof at least 64 MB. Utilities > Automation StatusandConfiguration > System Healthtell you whether the cron ran and why it failed.
How do I check whether the WHMCS cron is running?
The WHMCS Automation Status page at Utilities > Automation Status (or the gear icon in the Admin Area) shows the cron's health in one badge. The badge meanings are the same in 8.13 and 9.x:
| Badge | What it means |
|---|---|
| Green Ok | The cron was invoked in the last 120 minutes and the daily tasks completed in the last 24 hours. |
| Yellow Warning | The cron ran in the past but has not been invoked in the last 120 minutes. |
| Red Error or Not Ok | The cron has never been invoked, or the daily tasks have not completed in the last 24 hours. |
Click the badge for the recent run report, then Learn more next to any failed item. Next, open Configuration > System Health and look for System Cron Tasks, Cron PHP Version Mismatch, Cron PHP Timezone, Cron HTTP Access Blocked and PHP Memory Limit. Finally, check the Activity Log at Configuration > System Logs: you should see entries beginning Cron Job every day, ending with Cron Job: Completed. No entries at all means the cron job itself is not set up correctly. If nobody on your team checks these pages each week, monthly WHMCS maintenance can cover it.
What is the correct WHMCS cron command?
The WHMCS system cron command is a PHP command-line call to cron.php, scheduled every five minutes. The WHMCS System Cron documentation gives this example:
*/5 * * * * php -q /home/username/crons/cron.phpYour real path depends on where WHMCS lives, so copy the command shown in Automation Settings and add the full PHP binary path if your server needs one (fix 5). The script also accepts arguments such as all, do, skip, -F (force) and -vvv (verbose), which need the PHP register_argc_argv directive enabled.
Fix 1: The WHMCS cron runs once a day instead of every five minutes
Symptom: Automation Status shows a yellow Warning, or you get the "Daily System Cron Attention Needed" email saying the cron did not run during your configured hour. Ticket escalations, email campaigns and domain syncs lag behind.
Check: Open the cron entry in your control panel. Older setups often use 0 9 * * * or an hourly schedule.
Fix: Change the schedule to */5 * * * *. WHMCS never runs a task more often than its schedule allows, so a five-minute cron does not repeat daily invoicing. The warning email can keep arriving until the next Time of Day hour, up to 24 hours later.
Fix 2: The WHMCS cron calls cron.php over HTTP and gets a 403
Symptom: The cron stopped after you upgraded to WHMCS 9.x. A wget or curl job returns 403 Access Denied, System Health shows Cron HTTP Access Blocked, and the Activity Log records the blocked request.
Check: Look for a command that starts with wget, curl or GET, or an external URL-pinging service.
Fix: Replace it with a command-line call such as php -q /path/to/whmcs/crons/cron.php. If your host gives you no cron access, add the scheduler's IP address or CIDR range to Cron HTTP Access Restriction in the Security tab at Configuration > System Settings > General Settings. WHMCS 8.13 accepts HTTP calls without an allowlist, but browser time limits still apply. If you are still planning the move, a WHMCS 9 upgrade should include this cron change.
Fix 3: The path to crons/cron.php is wrong
Symptom: Your cron daemon emails Could not open input file: /path/to/crons/cron.php or No input file specified every five minutes, and Automation Status says the cron has never run.
Check: Run ls -l /home/username/public_html/whmcs/crons/cron.php in a terminal. Typical mistakes are a missing public_html or WHMCS subfolder, an old path after a server move, or a staging path.
Fix: Copy the command from Automation Settings again and use the absolute path to the file.
Fix 4: The crons directory was moved but WHMCS was not told
Symptom: The cron returns Unable to communicate with the WHMCS installation, or a moved cron worked until the last WHMCS update.
Check: In the moved directory, config.php must exist (renamed from config.php.new) with an uncommented $whmcspath line pointing to the folder that contains init.php. The WHMCS configuration.php must contain a $crons_dir line with the new location.
Fix: Set both values, update the cron command and any email piping forwarders, and after every WHMCS update copy the new crons files from the release into your custom directory. WHMCS says skipping that copy causes automation errors.
Fix 5: The WHMCS cron uses a different PHP version from the website
Symptom: System Health shows Cron PHP Version Mismatch, or the cron fails with fatal errors right after a PHP upgrade while the site works.
Check: Compare Loaded Configuration File at Utilities > System > PHP Info with the output of php -v and php -i | grep "Loaded Configuration File". Run these as the account that owns WHMCS, not as root.
Fix: Put the full PHP binary in the command. On cPanel servers with EasyApache 4, cPanel's PHP documentation lists the CLI binaries as /usr/local/bin/ea-php##, so PHP 8.3 becomes /usr/local/bin/ea-php83 -q /home/username/public_html/whmcs/crons/cron.php. On DirectAdmin, WHMCS says to include the full PHP path. On Plesk, pick a compatible PHP version in Scheduled Tasks. WHMCS caches the mismatch warning until the next daily run (see Resolve a Cron PHP Mismatch).
Fix 6: ionCube Loader or a PHP extension is missing from command-line PHP
Symptom: Cron output says the file is encoded and needs the ionCube Loader, or shows Call to undefined function curl_init() or Could not connect to database.
Check: Run the same PHP binary your cron uses with -v; the output should mention the ionCube PHP Loader. Run it with -m and look for curl, PDO and pdo_mysql.
Fix: Install ionCube for that exact PHP version (in WHM, through EasyApache 4) or add its zend_extension line to the CLI php.ini, and enable missing extensions. WHMCS 9.1 needs ionCube Loader 15.0.0. A Could not connect to database error can also mean wrong database details in configuration.php.
Fix 7: PHP memory or time limits stop the WHMCS cron
Symptom: The run dies with Allowed memory size of 33554432 bytes exhausted (a 32 MB limit) or Maximum execution time of 30 seconds exceeded.
Check: Run your cron's PHP binary with -i | grep -E "memory_limit|max_execution_time".
Fix: Raise memory_limit to 128 MB (64 MB is the minimum) and max_execution_time to 120 seconds, or 300 on large installs. You can also set both in the command: php -d memory_limit=128M -d max_execution_time=300 -q /path/to/whmcs/crons/cron.php.
Fix 8: File permissions or the wrong system user
Symptom: The cron starts but tasks fail, System Health lists missed System Cron Tasks, or files in templates_c become owned by root.
Check: Compare the owner of the WHMCS files (ls -l) with the user whose crontab runs the job. Confirm that user can read configuration.php and write to templates_c, attachments and downloads.
Fix: Run the cron from the crontab of the account that owns WHMCS, not root, and correct file ownership. Keep configuration.php at the 400 permissions WHMCS recommends (440 or 444 if your server needs them). Calling the file through php means cron.php does not need execute permission.
Fix 9: The cPanel cron entry has a syntax problem
Symptom: The job appears in cPanel but never runs, or cron emails show shell errors such as "command not found".
Check: Open Home > Advanced > Cron Jobs. The five time fields should read */5, *, *, *, *, and the Command field should hold only the command, on one line, with absolute paths. A bare % in a crontab command starts a new line, so escape it as \%.
Fix: Choose Once Per Five Minutes under Common Settings, paste the command and save, following cPanel's Cron Jobs guide. Set a Cron Email address while testing so you see the output, and add >/dev/null 2>&1 only once the job works.
Fix 10: Daily tasks run at the wrong hour
Symptom: Invoices or suspensions happen at unexpected times, or System Health shows Cron PHP Timezone.
Check: Compare Time of Day in Automation Settings (9:00 am server time by default) with your cron schedule, and compare date.timezone in the web and CLI php.ini files.
Fix: Run the cron every five minutes so it always lands in the configured hour, and set the same timezone for web PHP, CLI PHP and WHMCS.
Fix 11: The WHMCS cron runs but a task inside it fails
Symptom: Automation Status shows x icons next to some tasks, the Activity Log has no Cron Job: Completed entry, or WHMCS 9.1 shows Down for Maintenance (Err 2) after you uploaded a patch set that includes the install folder.
Check: Click Learn more on each failed task, review Utilities > Module Queue for failed suspensions and terminations, and read the verbose output from the manual test below. A dead server in Configuration > System Settings > Servers can time out the usage metrics step.
Fix: Correct the specific error, such as server credentials or an unreachable host, then let WHMCS retry; it retries failed suspensions and terminations daily. For the 9.1 maintenance notice, finish the upgrade at install/install.php. When the error comes from a hook or custom module, hourly WHMCS bug fixing is usually the quickest route.
How do I test the WHMCS cron manually?
A manual WHMCS cron test from the command line shows the real error that a scheduled run hides. WHMCS's cron troubleshooting guide uses the same approach.
- Enable Display Errors in the Other tab at
Configuration > System Settings > General Settingsfor the test. - Open a terminal as the account that owns WHMCS: SSH, or
Home > Advanced > Terminalin cPanel. - Run the exact cron command with
-Vadded. It prints the WHMCS version and exits, which proves the PHP binary, ionCube and path all work. - Run the command with
-vvvto process due tasks with full output. - If you need every task, run
php -q /home/username/public_html/whmcs/crons/cron.php all -F -vvv. It should end with[OK] Completed. WHMCS says not to do this more than once in 24 hours. - For failures that only happen on schedule, append
-vvv >> crondebug.txtto the cron entry, wait past the Time of Day hour, then read the file in your home directory. - Turn Display Errors off, wait five minutes, and click Refresh on Automation Status.
Frequently asked questions
How often should the WHMCS cron run?
Every five minutes. WHMCS accepts once per hour as a minimum, but tasks such as ticket escalations, email campaign queues and job queues are designed to run as often as every few minutes.
Why does the WHMCS cron work when I run it by hand but not on schedule?
The scheduled job usually runs with a different PHP binary, php.ini, user or environment than your terminal session. Use the full PHP path in the cron command and log the scheduled output with -vvv >> crondebug.txt to see the difference.
Can I run the WHMCS cron with wget or curl?
Only with extra setup in WHMCS 9.0 and later, which block HTTP requests to cron.php with a 403 unless the caller's IP is in Cron HTTP Access Restriction. WHMCS recommends the command line for both 8.13 and 9.x.
Will a five-minute cron create duplicate invoices?
No. WHMCS runs daily tasks such as invoice generation once per day during the Time of Day hour, and other tasks only when they are due.
Where do I find my WHMCS cron command?
Go to Configuration > System Settings > Automation Settings, click the first badge and copy the value under Cron Command.
Do I need a separate cron for pop.php?
Only if you import support email over POP3, in which case crons/pop.php also runs every five minutes. WHMCS recommends email piping instead.
If the cron still will not run cleanly, our WHMCS cron job fixing service can find the cause and get invoicing, suspensions and terminations running again.