A cron job that silently stopped is one of the more expensive problems to have, because nothing appears broken until renewals quietly stop being invoiced. Check it deliberately.

Run it manually first

From a shell on the server:

php /path/to/whmaz/index.php cronjobs run

CLI runs are always permitted and do not need the secret key. If this works but the scheduled job does not, the problem is with the cron entry, not with WHMAZ.

Check the system cron log

tail -f /var/log/syslog | grep CRON

On RHEL-based systems use /var/log/cron instead. You are looking for an entry at the scheduled time each day.

Check the application log

WHMAZ writes to application/logs/. Open the current day's log and look for the cron entries and any errors recorded during the run.

Common reasons it does not run

• Wrong secret key — the request is rejected. Re-copy it from Settings → Automation.
• Wrong PHP binary — the CLI PHP version differs from the web one. Use the full path, such as /usr/local/bin/php.
• Curl not installed on the server running the cron entry.
• The URL redirects — if curl is not following a redirect from a non-canonical hostname, the task never executes. Use the exact canonical HTTPS URL.
• Execution timeout on a large install. Prefer the CLI method, which is not subject to the web server's time limit.

A simple monthly check

Confirm that renewal invoices exist for services due next month. If they do, the automation is working.