Cron Jobs let you schedule commands or scripts to run automatically (every minute, hourly, daily, weekly, etc.). Jobs run as your account user inside a restricted shell, so they can act on your files without needing full server access.

Who can use this

The signed-in account owner. Resellers/admins can view and manage cron jobs for your account.

Before you start

• Use absolute paths to programs and files (cron has a minimal environment).
• Test your command in the Terminal first.
• If running PHP, call the desired CLI (e.g., php83) and point to the full script path.
• Make scripts executable: chmod 755 /home/<user>/scripts/task.sh and add a shebang (e.g., #!/bin/bash).

What you see on this page

• An Email address for notifications (MAILTO) field — where cron sends output (leave empty to disable).
• A table listing each job’s Time and Command, with Edit/Delete actions.
• An “Add Cron Job” row to create new jobs using a standard 5-field schedule and the command to run.

Add a cron job (step-by-step)

1) In the top row, enter Time (5 fields like * * * * *) and your Command.
2) Click Add Cron Job. Duplicate jobs are prevented automatically.
3) If the job produces output, cron emails it to MAILTO. To silence a job, append >/dev/null 2>&1.

Edit or delete a job

• Click Edit, change the schedule/command, then Save.
• Click Delete to remove it. The table refreshes automatically.

MAILTO (email notifications)

• Set an address and click Update to receive output from your jobs.
• Leave it blank to disable emails globally.
• You can override per job by redirecting output: … >/dev/null 2>&1 (no email).

Schedule format (quick guide)

The 5 time fields are: minute (0–59) hour (0–23) day (1–31) month (1–12) weekday (0–7, Sun=0 or 7).
Examples:
• Every 5 minutes → */5 * * * *
• Daily at 03:15 → 15 3 * * *
• Sundays at 01:00 → 0 1 * * 0
Tip: For more patterns, see crontab.guru/examples.

Useful examples

• WordPress cron (every 5 min):
*/5 * * * * php83 /home/<user>/public_html/wp-cron.php >/dev/null 2>&1
• Run a PHP script nightly at 02:30:
30 2 * * * php83 /home/<user>/apps/cleanup.php
• Run a shell script weekly (Sunday 01:00):
0 1 * * 0 /home/<user>/scripts/backup.sh >/home/<user>/logs/backup.log 2>&1

Best practices

• Always use full paths (e.g., /usr/bin/find, /usr/bin/curl, php83).
• Log output for important jobs to files you rotate (not only email).
• Stagger heavy jobs to off-peak hours. Avoid running resource-intensive tasks every minute.

Troubleshooting

• “Invalid time format”: you must provide exactly 5 fields (minute hour day month weekday).
• No output / “command not found”: cron’s PATH is minimal — add full paths or call the correct PHP binary (e.g., php83).
• Script runs in terminal but not in cron: add a shebang (#!/bin/bash), use absolute paths, and ensure file permissions allow execution.
• Too many emails: redirect output to /dev/null or logs; or clear MAILTO.
• Permission denied: ensure the script is inside your home and owned by your user; make it executable if needed.