Updating and rolling back

Update

sudo smp-update

It installs the newest release, with the options you installed with. Your settings, sites and data stay as they are. Before anything changes, it checks the release the same way the first install did, with the release keys already on your server, never with keys from a new download.

When a release comes with a new version of the licence agreement, add --accept-eula, or type yes when it asks.
When there is nothing newer: "Already up to date."
It never installs an older release than the one you have.

Updating from 0.2.0 or earlier

Servers installed before 0.3.0 don't have smp-update yet. Update once with the installer run as a file, checking it the careful way, with your panel's domain and e-mail:

sudo bash install.sh --update --domain panel.example.com --email you@example.com --accept-eula

After that, sudo smp-update works.

Roll back

sudo smp-install --rollback

It switches the panel back to the previous release. Database changes made by the newer release stay; releases are written so the previous one still works with them. The last three releases are kept on the server.

If an update is refused

Message	What it means
"The release list has expired"	The list of releases on get.whitesmoke.cloud is renewed every week and is valid for 30 days. An expired list means it wasn't renewed in time. Nothing on your server changed, and everything keeps running: the panel, your sites, licence checks, certificates, backups. Try again later, or tell us.
"This server's clock looks wrong"	Fix the date and time (`timedatectl`), then try again.
"This update is signed with a newer key than this server knows"	We changed release keys and your server missed the changeover. Follow release keys.
"The release list is in a newer format"	Your `smp-update` is too old to read the list. See support.
"The release's signature does not verify"	The file isn't the one we published. Don't install it; tell us.

An expired list only stops new installs and updates. It never stops a running server.