Many sites have work tied to time rather than clicks: nightly reports, hourly exchange-rate updates, clearing abandoned carts, sending newsletters. Cron lets the server run these jobs itself. In ISPmanager cron jobs live in the Scheduler section and run as your hosting account user.
Reading a cron schedule
A job has five schedule fields followed by a command: minute, hour, day of month, month and day of week. An asterisk means "every" and */5 means "every fifth".
| Schedule | Meaning |
|---|---|
*/5 * * * * | every 5 minutes |
0 * * * * | at the top of every hour |
30 3 * * * | daily at 03:30 |
0 9 * * 1 | Mondays at 09:00 |
Times follow the server's time zone, so if a job must fire at an exact hour, check the log after the first run to confirm it started when you expected. Spreading heavy jobs across quiet night hours instead of stacking them all at midnight also keeps your sites responsive.
Creating the job
Open ISPmanager from the sayt.uz cabinet and go to Scheduler (cron) (Cron jobs in some versions). Enter the command with full paths, set the schedule in basic mode or type the five fields in expert mode, add a comment explaining the job, and decide whether output should be emailed; that is handy while testing but floods your inbox later. Cron starts in the user's home directory, not your site folder. Site files usually sit under a path like /var/www/USER/data/www/misol.uz, which you can confirm in the panel's file manager.
Running PHP scripts
Call the PHP binary that matches your site's version, because plain php may point to a different one. Extra versions often live at paths like /opt/php82/bin/php; support can confirm the exact path:
/opt/php82/bin/php /var/www/u1234/data/www/misol.uz/cron/rates.php >/dev/null 2>&1
Or request the script over HTTP, protected with a secret key:
wget -q -O /dev/null "https://misol.uz/cron/rates.php?key=long-random-key"
The trailing >/dev/null 2>&1 discards all output. When you want a record, send it to a log instead with >> $HOME/cron-rates.log 2>&1, so you can see at a glance whether each run succeeded or failed.
Example: a travel agency's exchange rates
A travel agency in Bukhara shows tour prices in dollars and sums on misol.uz, refreshed hourly by rates.php with the schedule 0 * * * *. Because a slow run could overlap the next one, the command is wrapped in flock:
flock -n $HOME/rates.lock /opt/php82/bin/php /var/www/u1234/data/www/misol.uz/cron/rates.php
WordPress and Laravel
WordPress checks wp-cron.php on page loads, which delays tasks on quiet sites and adds load on busy ones. Add define( 'DISABLE_WP_CRON', true ); to wp-config.php and schedule it properly:
*/15 * * * * wget -q -O /dev/null "https://misol.uz/wp-cron.php?doing_wp_cron"
Laravel needs one entry that runs every minute:
* * * * * cd /var/www/u1234/data/www/misol.uz && /opt/php82/bin/php artisan schedule:run >> /dev/null 2>&1
When a job does not run
Run the command manually over SSH first; if it fails there, the script is the problem. If it works in the terminal but not in cron, look for relative paths, a different PHP version or missing environment variables. Temporarily emailing the output shows the exact error. Avoid heavy jobs every minute, since they waste resources and can hit plan limits. If you are stuck, send sayt.uz support a ticket with the command and schedule.