Configuring and Troubleshooting WHMCS Crons

Posted on by Helpful Humans of Liquid Web | Updated:
Reading Time: 4 minutes

Over the years WHMCS has made some changes to where it stores certain directories, specifically directories outside of public_html. The goal of this is to increase overall security by moving sensitive files to a more protected location. While this change does help to improve WHMCS security, it also adds a few steps of complexity.

This article is meant to help simplify this complexity, or at least provide a reference configuration that you can use to troubleshoot cron issues, or gain a better understanding of WHMCS crons in general. I used WHMCS 7.3 for this article, but the general concept and instructions should apply for any 7.0 version of WHMCS.

General Troubleshooting Steps

Regardless of whether you’re troubleshooting a new install of WHMCS, existing install, or a post migration site, there area few steps you can take to make troubleshooting easier.

  1. Check configuration files, ensure that cron directories are valid, and match up between config files (cron config.php and whmcs configuration.php)
  2. Check directory and file permissions. These directories must be owned by the cpanel user, and have at least 750 permissions.
  3. Check crontab and ensure that the crons are actually created / running.

If WHMCS crons / automated tasks are not running, odds are that one of the 3 items above is the source of the issue.

WHMCS Cron Related Configuration Files

There are two main configuration files which contain cron related settings for WHMCS. Make sure these two files are using the proper directories, ideally ones that match up with each other. If you detect differences in the paths, odds are that’s where the issue is.

The two directories where WHMCS cron configuration files are stored are:

  • /home/$user/whmcsdata/crons/config.php
  • /home/$user/public_html/configuration.php


If WHMCS was customized during install the paths below may not exist, or may have a different name.

Once you’ve confirmed that both configuration files are correct, you’ll want to make sure that there’s an actual cron configured to run for the user. See the instructions below on modifying the configuration file for your crons in WHMCS.

WHMCS Cron configuration file – config.php

There’s a noteworthy configuration file located under the crons directory called “config.php”. There’s one variable specified here “$whmcspath”, that should point to the directory where WHMCS is installed. If you are migrating an existing WHMCS site, be sure to modify this file to point to the new whmcs install location (if cpanel user / location changed).

You can view the WHMCS cron config file by running this command (replace $user with actual cpanel user)

cat /home/$user/whmcsdata/crons/config.php

There should be one setting in this file, which should point to the WHMCS install directory

$whmcspath = '/home/$user/public_html/';

WHMCS General configuration file – configuration.php

In addition to the cron config file, there’s one more configuration file to cover – the main WHMCS configuration.php. Run the command below to view this file.


If you installed WHMCS in a directory under public_html you will need to adjust the command.
cat /home/$user/public_html/$whmcs_dir/configuration.php

You should see a “$crons_dir” variable in this file.

$crons_dir = '/home/$user/whmcsdata/crons/';

cPanel Cron Setup

Once you’ve confirmed that the cron directory paths are correct, and set in both config files, we will want to make sure there’s a cron set up for that user. If no cron is set up for the user, WHMCS will notify you that the cron status is not ok.

  1. To set up a cron, log into cPanel.
  2. Scroll to the cron jobs section. This can be found under the “advanced” section inside of cPanel.
  3. Click on the icon to enter the Cron Jobs control panel.

Cron Jobs

Cron Jobs

Adding a new cron

Before you add a new cron, look at the existing entries, if there’s already some for WHMCS, verify that the command is using the proper path to cron.php.

If you do not see any crons in place, you will want to create a new one that looks like the screenshot below. Replace “$user” with the actual cpanel user.

Add New Cron Job

Once you click “add new cron job” you should be all set. If you set the cron to run every 5 minutes, take a quick break, then log into the WHMCS admin area to check on the status.

Verifying WHMCS Automation Status

  1. To check the last time WHMCS ran a cron, log into the WHMCS admin area, hover your mouse over the Setup tab. A drop-down menu will appear, select Automation Settings.
    Automation Settings
  2. At the very top of the automation settings page you will see a red or green box with a Cron status. If the box is green it means you’re all set!
    automation settings green status
  3. If the box is red, then I suggest reviewing this article and checking the 3 main areas outlined at the start of this article.

Softaculous One Click Installer

WHMCS Data Directory

When you install WHMCS via Softaculous there will be a Data Directory section near the top of the page.

The WHMCS data directory stores the following:

  • Attachments
  • Downloads
  • Templates_c
  • Crons

By default the field is populated with “whmcsdata”, which will be created in the user’s home directory (/home/$user/whmcsdata/).

Feel free to modify the name if you want, just make sure you create this directory under the user’s home directory!

By default the field is populated with whmcsdata

Avatar for Helpful Humans of Liquid Web

About the Author: Helpful Humans of Liquid Web

Latest Articles

How to install Puppet Server on Linux (AlmaLinux)

Read Article

Deploying web applications with NGINX HTTP Server

Read Article

Email security best practices for using SPF, DKIM, and DMARC

Read Article

Linux dos2unix command syntax — removing hidden Windows characters from files

Read Article

Change cPanel password from WebHost Manager (WHM)

Read Article