All chapters

Updates

The panel updates itself from a signed update channel, one press at a time. Before anything changes it copies its own programs and database aside, and if the new version does not answer its health check, it puts that copy back by itself. Websites, mail and databases keep running throughout.

Where it lives

On Settings, the Panel version card. It names the version running now and, once checked, the channel's latest version and the security floor. The pill says where the server stands:

  • UP TO DATE, UPDATE AVAILABLE, or SECURITY UPDATE when the new version fixes a security problem.
  • BELOW SECURITY FLOOR: the publisher has said this version must not keep running; update as soon as you can.
  • HELD AT …: you asked the panel to stay where it is (below).
  • NOT CHECKED, CHECK REFUSED: the card says in words why, for example that the channel could not be reached.
  • UPDATING or ROLLING BACK while one is under way, and NEEDS A PERSON if the last update could neither finish nor put the previous version back by itself.
  • NO UPDATE CHANNEL or DEVELOPMENT BUILD: a build that was not installed from a signed release, which cannot update itself.

The check runs by itself once a day. Check now runs it at once, and checks the licence in with cpleks.com on the way.

The Panel version card on Settings with the pill NO UPDATE CHANNEL and the version the test machine runs, above the Licence card.
The Panel version card on the test machine. That machine runs a development build with no update channel, so its card says it cannot update itself; a release installed from cpleks.com shows Check now and the Update button described here.

Update

  1. When an update is offered, press Update to v….
  2. Read the confirmation: the panel stops for a minute or two while the new version is installed, websites, mail and databases keep running, and the programs and the database are copied aside first. Press Update to v… again to go ahead.
  3. The card says The panel is restarting and reconnects by itself when it is back. A toast then says Updated to v…, or that the previous version was put back and why.

After an update, the configuration the panel writes for sites, PHP, mail, DNS and the rest is rendered again by the new version, so improvements reach the server at once rather than at the next change. The server's firewall baseline is the one thing left as it was.

Which updates you can install

The licence decides: the card offers only the releases your update year covers. A release published after your update year ended is listed with the reason, renew at cpleks.com to receive it, and nothing else changes on the server. The server also needs a recent check-in with cpleks.com (Your licence).

Hold at a version

Hold at v… keeps the panel at the version it runs now until you press Release the hold. The daily check still runs, and a security floor raised past the held version is still reported.

Roll back

After an update, Roll back to v… puts the previous version back exactly as it was when the update started. The confirmation asks you to type the version, because every change made in the panel since the update is lost with it. Websites' files and customers' databases are not part of that copy and are not touched. You may have to sign in again.

Updating by hand

You can also install a newer release the way you installed the first one: run its installer on the server (Installing cpleks). The installer is safe to run over an existing installation and keeps its data.