Setting Up Cron Jobs on DirectAdmin Hosting
for Automation

What is a Cron Job and Why Does It Matter

A Cron Job is a time-based task scheduler on Linux servers that automatically executes scripts or commands at specified intervals. The name comes from Chronos (Greek god of time), and "crontab" is the configuration file that stores the schedule.

On web hosting, Cron Jobs are invaluable for automating repetitive tasks — backing up a database every night, sending weekly reports, clearing cache files, or syncing data from external APIs without any manual intervention.

On AsiaGB Hosting powered by DirectAdmin, you can configure Cron Jobs directly from the control panel GUI — no SSH or manual crontab editing required.

Understanding Cron Syntax

Cron syntax consists of 5 time fields followed by the command to execute. Each field represents a different time unit:

* * * * *  /path/to/command
│ │ │ │ │
│ │ │ │ └── Day of week (0-7) (0 and 7 = Sunday)
│ │ │ └──── Month (1-12)
│ │ └────── Day of month (1-31)
│ └──────── Hour (0-23)
└────────── Minute (0-59)

Special Characters in Cron

• * = every value (wildcard)
• */n = every n units, e.g. */5 = every 5 minutes
• n,m = multiple values, e.g. 1,15 = 1st and 15th
• n-m = range, e.g. 9-17 = hours 9 through 17

Setting Up Cron Jobs in DirectAdmin

Configuring a Cron Job in DirectAdmin is straightforward. Follow these steps:

1. Log in to DirectAdmin Panel at yourdomain.com:2222
2. Navigate to Advanced Features
3. Click Cron Jobs
4. Fill in the Minute, Hour, Day, Month, Weekday fields
5. Enter your command in the Command field
6. Click Add to save

Running PHP Scripts via Cron

There are two main ways to execute PHP scripts from Cron: PHP CLI and curl/wget:

Method 1: PHP CLI (Recommended)

/usr/local/bin/php /home/USERNAME/public_html/cron/backup.php

Replace USERNAME with your DirectAdmin account name and adjust the script path accordingly.

Method 2: Curl to URL

curl -s https://yourdomain.com/cron/backup.php > /dev/null 2>&1

Simpler but be mindful of security since the URL is publicly accessible.

Finding PHP Path on DirectAdmin

If you're unsure about the PHP binary path, common locations are:

• PHP 8.x: /usr/local/bin/php
• PHP 7.4: /usr/local/bin/php74

Common Use Cases on Hosting

1. Nightly MySQL Database Backup

0 2 * * * /usr/local/bin/php /home/USERNAME/public_html/backup-db.php

Runs every day at 02:00 — ideal for low-traffic hours.

2. Weekly Email Newsletter

0 9 * * 1 /usr/local/bin/php /home/USERNAME/public_html/send-newsletter.php

Runs every Monday at 09:00.

3. Clear Old Cache Files

0 */6 * * * /usr/bin/find /home/USERNAME/public_html/cache/ -mtime +7 -delete

Runs every 6 hours, deletes files older than 7 days.

4. WordPress WP-Cron

*/15 * * * * /usr/local/bin/php /home/USERNAME/public_html/wp-cron.php > /dev/null 2>&1

Run WP-Cron every 15 minutes. Recommended to disable WordPress's built-in WP-Cron and use this server-side alternative for better performance.

5. Regenerate Sitemap

0 */6 * * * /usr/local/bin/php /home/USERNAME/public_html/sitemap-generate.php

Regenerate sitemap every 6 hours so search engines always get fresh data.

Cron Syntax Reference Table

Troubleshooting Cron Jobs

If your Cron Job is not running as expected, troubleshoot in this order:

1. Check Full Paths

Cron runs in a minimal environment where $PATH is not set the same as your login shell. Always use absolute paths:

# ❌ May fail
php /home/user/backup.php

# ✅ Correct
/usr/local/bin/php /home/user/public_html/backup.php

2. Check File Permissions

chmod 755 /home/USERNAME/public_html/cron/backup.php

Scripts must be executable by the file owner.

3. Check Email Log from Cron

By default, Cron emails any output to the DirectAdmin account email. Check your inbox for error messages when a job runs.

4. Test Script Manually First

/usr/local/bin/php /home/USERNAME/public_html/cron/backup.php

Run the script directly in SSH to confirm it works before scheduling.

5. Verify Server Timezone

Best Practices and Caveats

Don't Schedule Too Frequently

A Cron Job that runs every minute and takes 5 minutes to complete will spawn multiple concurrent instances, consuming hosting resources and potentially slowing your website. Only schedule as frequently as your task genuinely requires.

Use Output Redirection

# Keep a log file
0 2 * * * /usr/local/bin/php /home/USER/backup.php >> /home/USER/cron.log 2>&1

# Suppress all output
0 2 * * * /usr/local/bin/php /home/USER/backup.php > /dev/null 2>&1

Test Before Deploying

Always run your script manually first to confirm it completes without errors before adding it as a Cron Job.

Check Resource Limits

Some hosting plans limit the number of Cron Jobs or CPU time per job. Avoid running heavy tasks during peak traffic hours to maintain website performance for visitors.

Frequently Asked Questions

Want hosting with full Cron Job support via DirectAdmin? View AsiaGB Hosting Plans →