ISPmanager 6 updates without stopping the web server, but the control panel update itself can lock the interface and API for a couple of minutes. Here is how to check the current version, safely update ISPmanager 6, and roll back if something goes wrong after the upgrade.
When you should update the panel
ISPsystem releases ISPmanager 6 updates several times a month: they patch vulnerabilities, fix bugs in the DNS and mail modules, and add support for new PHP versions. Install security updates within a day; install regular cumulative updates during the next planned maintenance window.
The license type affects the feature set but not the update procedure: Lite, Pro, and Host all update the same way through the same mechanism. The difference between plans is covered in the article about ISPmanager 6 license types.
How to check the current version
The panel version and build number are shown in the bottom right corner of the interface, and also through the server console. Connect over SSH and run:
/usr/local/mgr5/sbin/mgrctl -m ispmgr version
cat /usr/local/mgr5/etc/ispmgr.versionThe command prints the build number and release date. Compare it with the changelog on the vendor's site before running the update manually.
Update procedure through ispmgr
By default, ISPmanager 6 updates automatically on a schedule from the stable channel. A manual run is needed if auto-update is disabled in security settings or if you need a specific build.
| Update channel | What it includes | When to use it |
|---|---|---|
| stable | Tested builds for production | Live client servers |
| beta | Pre-release versions with new features | Test stand, not production |
| fix | Targeted security patches | Urgent vulnerability fix |
You can trigger a manual update with a single command:
/usr/local/mgr5/sbin/mgrctl -m ispmgr core.update sok=okThe process downloads the package, stops the ispmgr daemon, deploys new files into /usr/local/mgr5/, and brings the service back up. Client sites and mail keep working during this time; only the panel itself becomes unavailable.
What to do if the update hangs or breaks the panel
If the panel does not open after the upgrade, check the update log and the core log first — they almost always show the cause: not enough disk space, a module conflict, or an unfinished configuration database migration.
tail -n 200 /usr/local/mgr5/var/ispmgr.update.log
service ispmgr restartIf a restart does not help, roll the package back to the previous build from the local distribution cache and start the core again. After rolling back, be sure to check the module logs — a detailed walkthrough is in the article about ISPmanager 6 logs and diagnostics.
Backup before the update
Do not run major upgrades or a channel switch without a fresh copy of the panel configuration. Minimum checklist before updating:
- Back up the /usr/local/mgr5/etc/ directory with the core and module configuration
- Save a dump of the ispmgr configuration database
- Check free space on the panel partition: at least 2 GB is required
- Make sure scheduled backups of sites and mail are already configured
How to set up regular backups of the panel and site data is described in the article about ISPmanager backup.
Summary: a safe update checklist
- Check the current version and compare it with the changelog
- Back up the ispmgr configuration and database
- Pick an update channel: stable for production, fix for urgent patches
- Run the update and check the ispmgr.update.log file
- After the update, open the panel and check client sites and mail