How to schedule a website task with cron

Cron runs a command on a schedule. Applications use it for tasks such as queue processing or scheduled maintenance. Your hosting account must include permission to manage scheduled tasks; you do not need or receive server administrator access merely by creating a website cron job.

The Control Center does not create cron jobs. Open Virtualmin through your service's Hosting login and use its permitted scheduling module, or request assistance from support.

Prepare the command #

Get the exact command and recommended frequency from your application's documentation or developer. Confirm the script path, required working directory, and PHP executable with your host. The command-line PHP version may differ from the website's version.

Do not put passwords or private tokens into a URL or a command that could appear in logs or process listings. Use the application's supported private configuration method. Avoid scheduling a job twice through both the application and the hosting panel unless its documentation requires that arrangement.

Create the schedule #

1. Open Scheduled Cron Jobs if your host exposes it. Some accounts show it under Webmin → System; restricted accounts may have a direct module link.
2. Choose Create a new scheduled cron job.
3. Confirm that the job runs as your hosting user. Do not select a privileged server account.
4. Enter the reviewed command and a useful description.
5. Select the intended minutes, hours, and day fields. Confirm the scheduler's time zone, including how daylight-saving changes affect the job.
6. Save and record how you will receive output or review a private task log. Virtualmin scheduling guide, Webmin cron module

Verify a real run #

Use a safe test action or wait for the first scheduled run. Confirm the application's expected result as well as the absence of an error. A saved schedule does not prove the command completed. Keep diagnostic output until the job works, while ensuring it does not contain credentials or customer data.

Troubleshooting #

For “file not found,” check absolute paths and the working directory. For PHP or extension errors, confirm the command-line runtime. For repeated or overlapping work, lengthen the interval and ask the developer about locking; a job that takes ten minutes should not start another copy every minute.

Disable a failing job while you investigate repeated effects. Give support the schedule, sanitized command, run time, and error. Do not request a server reboot for a single application task.

Related: PHP versions and settings, reading website logs.