Setting Up Scheduled Tasks

90 vues Markdown

Scheduled tasks are what makes WISECP run on its own. Invoices, renewals, reminders, suspensions and provisioning all happen because a cron entry on your server wakes the panel up every minute. Until you add that entry, none of it runs.

Opening the Screen

Open Automation Settings and choose the System tab. The Crontab Setup card there gives you the exact command for your server, already filled in with your own address and key.

What Is on the Screen

The card offers the same job in three forms, on three tabs. Pick the one your hosting supports; you only need one of them.

Hosting PanelThe command to paste into cPanel, Plesk or DirectAdmin's own cron screen.

CLIThe command-line form, for adding to the server crontab over SSH. The best option when you have shell access.

CURLAn HTTP call, for shared hosting where PHP cannot be run from the command line.

Run Self-TestCalls the HTTP cron address from your browser and shows the response. Use it to confirm the address answers before you trust a schedule to it.

The rest of the tab holds worker scaling, how long finished job records are kept, and the secret that protects the HTTP address.

Tasks

Add the Cron Job

Open Automation Settings and go to the System tab.
Choose the tab that matches your hosting and copy the command exactly as shown.
Add it to your server's cron, set to run every minute.
Wait a couple of minutes, then open Automation and confirm jobs are appearing.

Check That It Is Really Running

Use Run Self-Test for the HTTP form, and watch the recent jobs list for a minute or two. A schedule that was added but never fires produces an empty list, not an error.

Things to Watch

Every minute, not every hour

One entry, running every minute, drives everything. WISECP decides internally which work is due; the schedule only has to wake it up. Setting it to run hourly or daily does not reduce load, it delays every renewal, invoice and reminder by that much.

A missing cron job looks like a healthy panel

Nothing turns red. Invoices are not issued, services are not suspended, reminders are not sent, and orders sit waiting. If automation seems to have stopped, check that the cron entry still exists before looking anywhere else.

Run it as the right user

Scheduled tasks write into the installation's own directories. Adding the entry as root, when the site runs as another user, leaves files that the web server can no longer write to. Use the same account the site runs under.

The command line has its own PHP settings

Command-line PHP often has a different configuration from the one the browser uses, including its own list of disabled functions. That is why something can work in the panel and not on schedule. When a task fails only when scheduled, compare the two.

Cet article vous a-t-il été utile ?

Merci pour votre retour !

Besoin d'aide supplémentaire ?

Notre équipe d'assistance est disponible 24h/24 pour tout ce que vous ne trouvez pas ci-dessus.

Nous contacter Ouvrir un ticket