https://docs.whmcs.com/9-1/tags/system-cron/Recent content in system-cron onHugo -- gohugo.iohttps://docs.whmcs.com/9-1/installation-guide/initial-configuration/enhancing-security/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/installation-guide/initial-configuration/enhancing-security/Enumerates ten security hardening steps for self-hosted installations: securing writeable directories, configuration.php, and crons, restricting Admin Area access by IP, renaming the admin directory, enabling SSL, and restricting database privileges.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/troubleshooting-the-system-cron/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/troubleshooting-the-system-cron/Lists linked troubleshooting articles grouped into general Cron Errors and Timezone-Specific Issues categories, and points to Check the Cron Job Status and Cron Failures for further diagnostic steps.https://docs.whmcs.com/9-1/installation-guide/initial-configuration/move-the-cron-directory/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/installation-guide/initial-configuration/move-the-cron-directory/Walks through moving the crons directory above the web root, updating cron tasks and email forwarders, editing the crons config.php and configuration.php files with the new path, and updating the system cron command in cPanel.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-the-database/could-not-connect-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-the-database/could-not-connect-errors/Documents the system cron’s “Could not connect to database” error caused by configuration.php misconfiguration or a missing PHP extension, with fixes to verify database settings, TLS certificate matching, and the required PDO, PDO MySQL, and MySQLi extensions.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-failures/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-failures/Troubleshoots incomplete system cron runs by checking the Activity Log for Cron Job Completed entries, running cron.php from the browser with Display Errors enabled, and running the cron.php command line script with the all -F -vvv verbosity flags to surface the specific task error.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-frequency-warnings/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-frequency-warnings/Covers the Automation Status warning that the system cron has not run within the past two hours, attributes it to an incorrectly configured cron job, and gives the fix of scheduling cron.php to run at least hourly, with every 5 minutes recommended.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-http-access-denied-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-http-access-denied-errors/Covers the 403 Access Denied error returned by crons/cron.php or the legacy admin/cron.php alias when a direct HTTP request’s IP address is not on the Cron HTTP Access Restriction allowlist, and gives the fix of invoking cron via CLI or adding the caller’s IP address or CIDR range to the allowlist in General Settings’ Security tab.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-input-file-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-input-file-errors/Covers the Could not open input file: /path/to/crons/cron.php error, attributes it to the cron.php file being absent from the configured directory path, and gives the fix of correcting the path and confirming the file exists there.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-metrics-polling-timeout/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-metrics-polling-timeout/Covers cron timeouts during Tenant Usage Metrics polling, attributes them to an offline or misconfigured server under Configuration > Servers, and gives steps to remove inactive servers, test each connection, verify Server Name and Port, or disable Update Usage Statistics.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-system-queue-timeout/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-system-queue-timeout/Covers cron runs that stall on the Executing System Queue step due to database backup generation and zipping slowing as the database grows, and gives the fix of running system cleanup tasks and disabling FTP/SFTP and Daily Email Backups under Database Backups.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-time-of-day-issues/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/cron-time-of-day-issues/Covers the Daily System Cron Attention Needed warning stating the cron did not execute within its configured hour, attributes it to a misconfigured hosting control panel cron entry, and gives the fix of setting the cron command’s Minute field to */5 with Hour, Day, Month, and Weekday set to *.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/fatal-memory-size-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/fatal-memory-size-errors/Covers the Fatal error: Allowed memory size of 33554432 bytes exhausted message, attributes it to the cron job exceeding a 32 MB PHP memory_limit, and gives the fix of raising memory_limit to 64 MB minimum or 128 MB recommended, in the PHP configuration or the cron command.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/intermittent-cron-failures/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/intermittent-cron-failures/Covers cron runs that complete manually but fail intermittently on schedule, and gives steps to enable Display Errors, append -vvv » crondebug.txt to the cPanel cron command, and compare the resulting crondebug.txt output against sample failing and successful task-queue runs to find the error.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-the-database/large-database-backup-failures/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-the-database/large-database-backup-failures/Explains failing or timing-out database backups caused by large database size exceeding PHP and cron processing limits, with fixes recommending cPanel Backup or an external tool like mysqldump instead of FTP or email backups.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/no-input-file-specified-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/no-input-file-specified-errors/Covers the No input file specified error emailed every five minutes by the server’s cron daemon, attributes it to an invalid cron.php path in the server’s cron job configuration, and gives the fix of correcting that file path in the cron command.https://docs.whmcs.com/9-1/system/automation/system-cron/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/system/automation/system-cron/Lists the cron.php and pop.php cron task commands, the crons directory location, the all/do/help/list/skip arguments and -F/-v/–email-report/-V/–no-ansi/-h options, the full table of individual task flags (such as –CreateInvoices, –AutoSuspensions, –DatabaseBackup) with their frequencies, and how to schedule custom task runs or invoke cron via HTTP GET request, which WHMCS blocks by default unless the caller’s IP address or CIDR range is on the Cron HTTP Access Restriction allowlist.https://docs.whmcs.com/9-1/troubleshooting/system-health/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/system-health/The System Health page, at Configuration > System Health, provides an overview of the WHMCS installation and system environment status, highlights potential configuration and security issues that need attention, indicates whether updates are available for the installed version, and links to the change log and release notes. This page documents each System Health check and its recommended solution, including Automatic Update Requirements, Certificate Authority verified SSL detection, the Cloudflare proxy check, the CloudLinux MySQL extension check, the Cron HTTP Access Blocked check, Cron PHP timezone and PHP version mismatches, cURL, TLS, and OpenSSL version warnings, customising default paths, custom templates, deprecated modules that remain active and configured after an update, error reporting, event handling, invoice immutability, the obsolete invoice mutability variables in the configuration.php file, legacy Smarty tags, MySQL server configuration, OPcache status, permissions, PHP error levels, the PHP memory limit, PHP session support, the PHP version, POP cron ticket import, recommended and required PHP extensions, required PHP functions, secure TLS and SSL support in cURL, the sensitive directory check (including exposed Storage Settings directories and directories that could not be evaluated), system cron tasks, the system URL check, two-factor authentication storage encryption, and website SSL.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/system-timezone-issues/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/system-timezone-issues/Covers timezone symptoms like incorrect timestamps, two-factor authentication code errors, and cron frequency warnings, attributes them to a mismatch between the webserver’s and cron engine’s PHP date.timezone settings, and gives steps to compare them via SSH before updating the server clock, php.ini, or cron command.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/unable-to-communicate-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/unable-to-communicate-errors/Covers the Unable to communicate with the WHMCS installation error seen with cron.php, pop.php, or pipe.php, attributes it to a customized crons directory, and gives the fix of uncommenting and correcting the $whmcspath line in /crons/config.php to the full WHMCS installation path.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/undefined-curl_init-function-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/undefined-curl_init-function-errors/Covers the Error: Call to undefined function curl_init() message, attributes it to a missing or disabled PHP cURL extension checkable with the php -m command, and gives the fix of installing and enabling the cURL extension.https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/whoops-exception-errors/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-cron-issues/whoops-exception-errors/Covers the Maximum execution time of 30 seconds exceeded Whoops exception, attributes it to the cron job exceeding a 30-second PHP max_execution_time value, and gives the fix of raising it to 120 or 300 seconds or setting it directly in the cron command.https://docs.whmcs.com/9-1/system/automation/cron-tutorials/check-the-cron-job-status/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/system/automation/cron-tutorials/check-the-cron-job-status/Shows how to check cron health via the Admin Dashboard Automation Overview widget and the Automation Status page’s Ok, Warning, and Error/Not Ok badges, and how to open the Cron Status report to find and resolve individual failed tasks.https://docs.whmcs.com/9-1/system/automation/cron-tutorials/configure-the-system-cron-job/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/system/automation/cron-tutorials/configure-the-system-cron-job/Gives copy-paste cron command setup steps for cPanel Cron Jobs, Plesk Scheduled Tasks, DirectAdmin Cron Jobs, and manual crontab entries, including the */5 * * * * schedule and PHP binary paths for each control panel.https://docs.whmcs.com/9-1/system/automation/cron-tutorials/configure-when-daily-tasks-run/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/system/automation/cron-tutorials/configure-when-daily-tasks-run/Gives the steps to set the Time of Day value under Automation Settings > Scheduling that controls the hour during which the system cron executes daily tasks, and recommends running the cron every five minutes.https://docs.whmcs.com/9-1/system/automation/cron-tutorials/find-the-cron-php-ini-file/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/system/automation/cron-tutorials/find-the-cron-php-ini-file/Gives two methods to identify the php.ini file used by the cron engine: running php -i | grep “Loaded Configuration File” over SSH or cPanel Terminal, or writing that output to a phpoutput.txt file from a temporary once-a-minute cron job.https://docs.whmcs.com/9-1/system/automation/cron-tutorials/resolve-a-cron-php-mismatch/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-1/system/automation/cron-tutorials/resolve-a-cron-php-mismatch/Walks through comparing the web server’s Loaded Configuration File path in PHP Info against the cron’s php.ini path, then resolving a version mismatch via cPanel MultiPHP, and notes the System Health Cron PHP Version Mismatch warning caches until the next daily cron run.