Panel update failed: what happened and what to do
On this page
Before an update, the panel saves a snapshot of its current code and database. If the installation of the new version stops with an error, the previous version is put back automatically and keeps running. Websites, email and databases stay online either way.
Symptoms
- Updates (section Server) shows Last update: with failed and a message.
- One of these messages:
- "The installer stopped with an error, so version … was put back and is running. See the log."
- "Download failed"
- "Checksum mismatch: the download is corrupted or was tampered with. Nothing was changed."
- "The installer stopped with an error and the automatic restore of … did not finish; see the log. A snapshot of … is in …"
- "An update is already running." when you click Update to ….
Causes
Most likely first:
- A step of the installer failed — a package download, the package manager busy, a service that did not start in time.
- The release could not be downloaded or did not match its checksum (network or proxy problem).
- An update is still running (for example the nightly fix release).
- The automatic restore failed — rare; the snapshot is still there.
Fix
Read the log
On Updates, open Update log: it shows each step and the error. The full log is /var/log/panel-update.log on the server:
tail -n 100 /var/log/panel-update.log
1. The installer failed, previous version running
The panel works on the previous version. System packages the installer had already updated stay updated; the previous version works with them. Fix what the log names (for example free disk space, or wait for system updates to finish), then click Update to … again.
2. Download or checksum
Nothing was changed. Check that the server can reach the internet over HTTPS, then try again later. A checksum mismatch that repeats means something between the server and the update server changes the download; do not install it by other means.
3. Already running
Wait a few minutes and reload Updates. Fix releases install themselves around 3 am when Install fix releases automatically at night is on (Server Settings → Fixes and error reports).
4. The restore did not finish
The message names the snapshot folder, /root/panel-snapshots/<version>-<date>. Restore it on the server as root:
cd /root/panel-snapshots/<version>-<date>
tar -xzf code.tar.gz -C /usr/local/sahaab
zcat database.sql.gz | mysql sahaab
systemctl restart sahaabd
The last three snapshots are kept.
Good to know
- During a normal update the panel may be unavailable for about a minute while its services restart.
- The update restarts the background agent so it runs the new code.
- When Send error reports is on, a failed update is reported automatically.
Still not working?
If the panel does not open after an update, see Control panel does not open. Send /var/log/panel-update.log to support with your version (sahaab version).
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- Tasks stay "Queued" and changes are not applied
The panel warns that tasks have been waiting over 2 minutes and nothing you change takes effect. Check and restart the background agent sahaabd on the server.
- A task failed in the panel: read the error and retry it
A change shows "Failed" in the Task Queue. Find the error in the task output, let the AI assistant explain it, fix the cause and run it again.
- Control panel does not open (port 2083 or 2087)
The control panel or admin panel does not load: timed out, refused or a certificate warning. Check the address, firewall, your IP and panel services.