Panel update failed: automatic rollback and snapshots

For server administrators · Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. How the automatic rollback works
  5. Still not working?
  6. Common questions

Before every update, the control panel saves a snapshot of its current version. If the new version cannot be installed, the previous version is put back by itself. This page explains what you see and what to do.

Symptoms

On Updates (section Server), the card says Update to … failed with one of these messages:

  • Download failed or Checksum mismatch: the download is corrupted or was tampered with. Nothing was changed.
  • The installer stopped with an error, so version … was put back and is running. See the log.
  • The installer stopped with an error and the automatic restore of … did not finish; see the log. A snapshot of … is in …

Causes

  1. The download failed or was damaged. Nothing was changed; your version keeps running.
  2. The installation stopped with an error (for example a package that could not be installed). The previous version was restored.
  3. Rare: the restore did not finish either. The snapshot is still on the server.

Fix

The download failed

Check that the server can reach the internet over HTTPS, then click Check for updates and Update to … again.

The previous version was put back

Your panel runs the previous version and works normally. Open Update log on the Updates page to read the error, correct the cause if it is on your server (for example a full disk: check with df -h), and try the update again later.

The automatic restore did not finish

Restore the snapshot by hand as root (over SSH). The message names the snapshot folder; the snapshots are in /root/panel-snapshots/<version>-<date>/, each with code.tar.gz and database.sql.gz.

cd /root/panel-snapshots/<version>-<date>
tar -xzf code.tar.gz -C /usr/local/sahaab
zcat database.sql.gz | mysql sahaab
systemctl restart sahaabd

How the automatic rollback works

  • The snapshot holds the panel's code and the panel's own database. Websites, email and customer databases are not part of it and are not touched.
  • On failure, the previous code is put back. The panel's database is restored too when the new version had already changed it.
  • System packages that the new version already installed stay; the previous version works with them.
  • The last three snapshots are kept; older ones are deleted.

Still not working?

Read the full log on the server in /var/log/panel-update.log and check that the agent runs:

systemctl status sahaabd

If the panel does not open at all, restart its web server with systemctl restart nginx.

Common questions

Can I go back to an older version on purpose?

There is no button for it. The snapshots in /root/panel-snapshots/ let you restore the previous version by hand, as shown above.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.