Automation on Hold After a Move or a Copy
WISECP records where an installation runs. If the same database later runs somewhere else, automation waits there until you choose the live installation. A test copy or a server you left behind can then no longer suspend or delete accounts on your real servers.
Opening the Screens
The hold appears on the Automation screen: Settings then Automation. You end it on the License screen under Help, after reissuing the license in your wisecp.com account.
What the Hold Is
At its first automation round an installation saves its folder path and server name in the database. Every later round compares them. If either differs, automation is put on hold in that place.
When it starts
- The files and the database were copied to another folder or another server.
- A backup was restored in a different place from where it was taken.
- The server name changed.
- The installation was upgraded from 3.x and its automation has not run on 5.x yet.
An installation that stays in its place never waits. Updating WISECP does not start a hold.
What waits and what keeps working
While the hold lasts, no invoice is created and no service is suspended, cancelled or removed from a server. No domain operation runs, no card is charged, and no email or SMS is sent. Scheduled backups are not taken either. Waiting jobs are not deleted: they continue when the hold ends.
These keep running: license and update checks, WISECP updates, exchange rate updates and security checks. What you do by hand in the panel also works, such as suspending a service or running one task with its play button.
Tasks
Start automation on the live installation
- Decide which installation is the live one and open its Automation screen. Continue only there, and only once the red band is showing: a reissue made earlier does not end the hold.
- In your wisecp.com account, open the service page of the license. In the Reissue License card click Reissue and confirm.
- In the panel of the live installation, click Verify License in the red band. The License screen opens.
- Click Force License Update. The license now belongs to this installation.
- Within a minute the band disappears and the waiting jobs continue.
Another 5.x installation that uses this license stops at its next license check, within a day. To stop it sooner, switch its automation off or remove its cron job.
The copy uses another license key
The band then adds a line about the different key. Reissuing that key does not end the hold. On the License screen click Change License Key, enter the original key and click Save & Verify. Then follow the steps above.
After an upgrade from 3.x
The upgraded installation waits until you reissue the license once, with the same steps. Do it on the live installation only. A 3.x installation that keeps running is not stopped by the reissue, so remove its cron job yourself.
Things to Watch
Reissuing on a test copy starts automation there and stops your live installation. If the installation is a test copy, leave the band as it is.
The hold ends only with the license key the database was running under. Move with that key, then change the key. If that license is already cancelled, contact support.
A setup that moves to a new release folder on each deployment waits after every deployment. In Docker, give the container a fixed hostname, or each new container counts as a new place.
It uses the server's mail function, because notifications wait during a hold. If that function is off, no email arrives. The band and the notification still appear.
In 5.0-beta.4 and earlier, the automation of a copy runs like the original's. There, remove the cron job on every copy yourself.
Related Articles
Agradecemos pelo feedback!
Nossa equipe de suporte está disponível a qualquer hora para ajudar com o que você não encontrou acima.