CyberPanel v3.0.0 is now available. This major release adds Ubuntu 26.04 installation and upgrade support, strengthens every local backup path, and consolidates version handling across the panel, installer, API, CLI and restore system.
The release was tested through clean installations on Ubuntu 22.04, 24.04 and 26.04. The final Ubuntu 26 validation went beyond installation: we logged into the panel, created a website, installed WordPress, opened CyberSMTP, issued SSL, created backups, deleted the live test site and restored it under the same domain.
Ubuntu 26.04 support
CyberPanel 3.0.0 supports Ubuntu 26.04 with the distribution’s current Python and MariaDB packages. The installer now handles package-manager locks, DNS handoff and long-running setup steps more reliably while keeping the installation session alive.
- Python 3.12 panel runtime on Ubuntu 26.
- Distribution MariaDB packages where older vendor repositories are unavailable.
- Compatible mail-scanning dependencies and Memcached fallback behavior.
- DNS resolution is verified before package downloads begin.
- Ubuntu package operations wait for temporary dpkg locks instead of skipping required components.
The Ubuntu-specific work does not replace the established installation paths for Ubuntu 22.04, Ubuntu 24.04, CentOS/RHEL-family systems or OpenEuler.
Backups tested through real deletion and restoration
Backup reliability was a central part of this release. The test WordPress site was backed up, deleted and restored twice. Its files, database tables, database grants, PHP version, SSL certificate and active plugins were verified after restoration.
- Full backups: archives must be complete, stable and structurally valid before CyberPanel accepts them.
- Scheduled backups: full archives no longer include local incremental repositories inside themselves, preventing uncontrolled archive growth.
- Legacy incremental backups: Restic snapshot IDs are parsed reliably even when the command saves a snapshot and then prints a warning.
- V2 local backups: Rustic repositories work directly from local storage without requiring a configured Rclone remote.
- Database restoration: V2 restores now verify both the Rustic read and MySQL import processes instead of reporting success after a failed import.
Restore metadata now also preserves whether the source site actually had an automatic mail. child domain. CyberPanel no longer invents one during restoration.
Get exclusive access to all things tech-savvy, and be the first to receive
the latest updates directly in your inbox.
Safer archive extraction and cleaner diagnostics
All backup extraction paths validate archive members before writing files. Parent traversal, absolute paths, escaping links, special filesystem entries and unsafe writes through existing destination symlinks are rejected.
Backup diagnostics no longer record repository access tokens or database passwords. Child-domain deletion also cleans up its dedicated certificate and exact-domain ACME state without following certificate links into another domain’s files.
Security and reliability improvements
- Web Terminal authentication and token validation were hardened.
- Terminal secret and authorized-key files receive stricter ownership, permission and symlink checks.
- Generated website configurations block sensitive files such as environment files and repository metadata.
- Domain alias listing, SSL issuance and deletion work together again.
- PHP 8.5 memory-limit parsing now targets the correct directive.
- PowerDNS SOA serials advance after DNS record changes.
- The free WordPress installation path remains accessible from website management.
Consistent 3.0.0 version reporting
CyberPanel’s runtime, API, installer, upgrader, backup metadata and CLI now share one version source. Fresh installations write the JSON format expected by the CLI, and upgrades synchronize the database-backed version returned by the API.
Version comparisons now use semantic tuples instead of decimal-number comparisons, so multi-digit releases and future backup formats are handled correctly.
How to upgrade
Before upgrading a production server, take a provider snapshot or a verified full backup and schedule a maintenance window. Then open Version Management → Upgrade in CyberPanel, or follow the CyberPanel upgrade guide.
For the detailed technical change list, see the CyberPanel changelog.
