Changelog
What changed in ZoPanel, release by release: security hardening, performance under load, safer updates, backups and day-to-day operations.
Updates are installed from the panel or with zopanel update. Every update is signed, checked again by the root agent, and rolled back automatically if the new version is not healthy.
0.4.35 — Vibe-coded apps, new look
9 November 2026
Git deploy
- TanStack Start is detected. Lovable projects created since May 2026 (and other TanStack Start apps) render on the server, but were taken for static Vite sites, so the deploy served an empty page. They now build with
NITRO_PRESET=node-server(aNITRO_PRESETyou set yourself wins) and runnode .output/server/index.mjsor the project'sstartscript, with the usual health check and zero-downtime switch. Existing websites change only on their next deploy with Auto-detect on; if the new release does not pass its health check, the previous one keeps serving. See Git deploy. - Single-page app fallback. A React, Vue or Angular app's routes are not files, so a direct visit or a reload returned 404. A new Single-page app fallback switch on the website's Tools tab serves
index.html(status 200) for paths that match no file, while missing images, CSS and JavaScript still return 404. It is on by itself for new websites whose first deploy is Vite, Create React App or Angular; websites that already exist keep their behaviour until you turn it on. Static websites only. See static sites.
Panel
- New look. Blue and teal on navy, as on zopanel.net: new colours in light and dark mode, glossy primary buttons, a new sign-in page and the new ZoPanel mark. A white-labelled panel shows the first letter of its own name instead of ZoPanel's mark. The dashboard's quick actions use three colours (hosting, data and apps, administration) instead of a rainbow.
Security
- The compression library is updated (klauspost/compress 1.20.2, GO-2026-6865): a crafted zstd archive could crash the import of a cPanel or other backup.
0.4.34 — Security updates
5 November 2026
- Gitea 28.3.0. The App Store's Gitea is pinned to 28.3.0 (1 November 2026), which fixes twenty advisories of 28.2.0: an account takeover through OAuth2 auto-linking with an attacker-chosen username (GHSA-8p3x-w464-4g6v), stored XSS on the Gitea site through Actions artifacts (GHSA-9v6p-xpcp-7488), Actions runs from forks getting secrets and a write token (GHSA-32h8-5xqg-h466), and a dozen ways for "public-only" tokens to read or change private repositories, issues, packages and organisations. New installs get 28.3.0; installs on 28.2.0 or 28.1.0 show Security update: Gitea 28.3.0 on their Docker tab and update with one click (backup first, undone by itself if the new version does not keep running). Scripts that used a public-only token to reach private data stop working, as intended: give them a token with the right scope. See Gitea.
- Panel libraries. go-jose 4.1.6 (three crashes on crafted JSON or JWK input, used when talking to Let's Encrypt) and chi 5.4.0 (a client IP spoofing fix in a function ZoPanel does not use). Nothing changes for websites or customers.
0.4.33 — Fixes
30 October 2026
- SSL could not be issued for a website on a subdomain. A website such as
shop.example.comwas created withwww.shop.example.comtoo, which almost never has a DNS record; Let's Encrypt then refused the whole certificate ("domain does not resolve") although the subdomain itself pointed to the server. Issuing or renewing a certificate now leaves out the names that cannot be validated yet (no DNS record, or still pointing to another server) and says which in the job log; the website's own domain is always included, and a left-out name is added at the next renewal once its DNS is set. Websites already affected get their certificate with Issue certificate (or Re-issue) on the SSL tab after the update. - The new-website form ticks Also serve www.… for a domain (
example.com,example.com.vn) but no longer for a subdomain; it can still be ticked by hand.
0.4.32 — Fixes
26 October 2026
- MariaDB listened on every address on Debian 12. Debian's MariaDB package starts it through systemd socket activation (
mariadb.socket), where systemd, not MariaDB, holds port 3306, on every address, andbind-address = 127.0.0.1does not apply. The firewall still blocked the port, but one wrong rule would have exposed the database (Security Center: "MySQL/MariaDB (port 3306) is blocked by the firewall"). MariaDB now listens on 127.0.0.1 only, and on every address only while a database allows remote hosts, the firewall letting in just those hosts. Existing servers are fixed when they update (MariaDB restarts once, for a few seconds); if it does not start again, the previous setting is put back. - The Security Center's Open button for the firewall, Fail2ban and open-port items went to the page it was on, so nothing seemed to happen. It now scrolls to the firewall or Fail2ban card.
0.4.31 — Fixes
25 October 2026
- "database is locked" could make an action fail. A panel database transaction that read, then wrote just after another one had written, failed at once instead of waiting its turn (an App Store install failed now and then while the server was busy). Transactions now take the write lock when they begin and wait for it as intended.
- The App Store's reason for a disabled Install reads naturally when the plan's applications or websites are all in use.
0.4.30 — Fixes
24 October 2026
Monitoring, App Store and server
- Apps crashed when a customer installed several. Every app ran in the account's process limit (200 by default) with a cap of 512 each, and nothing checked that they fit: around the ninth app Open WebUI restarted in a loop and OpenClaw hung, while the install said "Completed" and the dashboard "Online". Apps are now planned for processes the way they were for memory: each app has a measured process cap (32 to 320, see Apps), an install must fit the package (its websites keep PHP children + 40 processes) whoever installs it, customers, resellers and administrators alike, and the server must have the RAM for it. Apps already installed get their cap at start, never below half again what they use. Math libraries (Open WebUI) now use one thread per CPU the app is given, not one per core of the server. Accounts reaching their process or memory limit notify the account and its provider, those whose apps need more than their plan are listed on the dashboard, and a crashed or crash-looping app shows as down.
- Apps take a website of the plan, which the App Store did not say ("0 of 14 applications" with no website left). It now shows websites, memory and processes left and why an app cannot be installed, and the package form warns when it allows more apps than websites.
- Uptime reported every HTTPS website as down. The check connected to the local web server without naming the website, which nginx refuses since it rejects unnamed TLS connections; dashboards showed websites "not responding" and owners could get "Website down" notices. The check now names the website. On the first check after the update, the wrong "down" states and hours are cleared quietly, without a burst of "Website recovered" notices.
- App Store installs failed on long domains (about 24 characters or more) with an nginx "variables_hash_bucket_size" error. Setup-lock and protected-folder variables now have short fixed names, existing websites are rewritten once, and domains longer than 41 characters get a valid app name. A failed install now removes everything it created: the data volume and its image file (which counted against the account's disk), the container and the website folder.
- Adding a long
www.alias could make nginx refuse the whole configuration (server_names_hash_bucket_size): the setting is raised to 256. - Time sync on Debian 12. When outgoing NTP is blocked, the Security Center fix switched to htpdate with HTTPS servers, which Debian 12's htpdate cannot use, so the clock stopped syncing while the check still passed. The fix now tries NTP first, then htpdate over HTTPS, then HTTP, and only replaces chrony once htpdate works; the check verifies that the clock is really in sync, and the agent repairs the setup left by 0.4.29.
- Webmail single sign-on entries of a deleted or recreated mailbox are removed at once, so a mailbox created again with the same address cannot be opened with an old sign-on link.
- Deleting a website or an account also removes its firewall (WAF) profile lines, including the
www.alias, and the webmail storage of its mail domains; leftovers from earlier versions are cleaned at start. - Firewall changes no longer wait (up to a minute) while a Security Center fix installs packages.
- The administrator's Resources page no longer calls endpoints meant for hosting accounts (two errors on load); it asks which account to show.
- Let's Encrypt accounts. Without an administrator e-mail, each customer's e-mail registered a Let's Encrypt account of its own (eight in a day on a test server; Let's Encrypt limits the accounts one IP address may create). The server now has one account: its contact is the administrator e-mail when one is set, otherwise none, never a customer's. Setting or changing the administrator e-mail updates the contact of that same account.
- App ports taken by another process. App ports are predictable, so a process of another account listening on the port the next app would get (a customer with SSH could do it on purpose) made that install or deploy fail. The panel now checks the port first and, when something else listens on it, gives the website another free one.
- Deleting an account now also removes its PHP-FPM sockets and links under
/run/zopaneland its PHP pool logs in/var/log/zopanel/php; those left by deleted accounts are removed when the panel starts. - A failed App Store install said "app data, if any, is kept" right after removing the data it had just created. The log now says what became of the data.
- The App backup settings of an uninstalled app, or of an install that failed, are deleted instead of left as empty entries; old empty entries are removed once.
- An app's upgrade record (used for Roll back) is deleted when the app is uninstalled or its website or account is deleted; it stayed before, so an app installed again on the same domain could offer a rollback to a deleted backup. Old records are removed once.
- Open WebUI showed "500: Internal Error" on the first visit of each browser: its first page load fetches about 180 files at once and the default flood guard (bursts of 100 requests) refused part of them. For apps and static websites, whose every file goes through it, the burst is now 300 (still 50 requests a second per visitor; PHP websites keep 100, their static files are not counted); existing websites are updated at start.
- Dovecot warned at every reload that the global
mail_pluginssetting "won't change the setting inside an earlier filter". The Sieve settings are now read after the main mail settings (no warning; the quota and Sieve plugins still apply) and the LMTP filter no longer lists the quota plugin twice. Existing servers are fixed when the panel starts.
Backups
- Open WebUI backups no longer include its model cache (
data/cache, about 900 MB on an empty install, so seven kept backups took about 6 GB of the customer's space). The app downloads the model again when it starts. - Accounts with a Python app could not be restored. The check before a restore refused the backup the panel had made itself, because a virtualenv's
python3links to/usr/bin/python3. Links in website files are now restored as links, wherever they point, while everything that could write through a link (an entry below a link, hard links, devices,..) is still refused. - Account backups now include PostgreSQL, MongoDB and Redis databases. They only held MariaDB before, while the page said "full backups". PostgreSQL is dumped as SQL, MongoDB with mongodump and Redis as the account's own keys, each with temporary least-privilege credentials, and restored as the account. The backup page says what is and is not inside (App Store apps have their own backups; the WordPress object cache is not kept).
- Restoring a WordPress database (account backup, database backup or import) empties the website's Redis object cache, so the site shows the restored content at once.
- The database Backups list and app backup lists refresh when a backup finishes, and the newest backup is marked. Customers who cannot restore an app backup are told to ask their provider.
- Restoring an account backup after a website was deleted and created again brought its files back but not its app (a Python or Node.js app deployed from Git): the website had no app and nothing ran. The app settings in the backup are now applied when the website has no app: the app is created again, deployed and started, and the log says so. A website that has an app keeps it, and one that is now another kind of website (WordPress, an App Store app) is left as it is.
Fixes
- Provisioning API without a panel domain.
panel_urlwas empty andPOST /accounts/{username}/loginreturned a relativeurl, so billing modules built broken links. Both are now always absolute: the panel domain, else the address the request came to when it is one of the server's public IPs or its host name, else the server's public IP, with the panel port. - Provisioning API packages.
POST /packages(andPUTof a new name) with only a few fields created a package with unlimited CPU, memory and processes and no SFTP. Fields left out now get the panel's New package defaults (100% CPU, 1024 MB, 200 processes, SFTP on, 5 websites, 5120 MB disk…), held to a reseller's own plan; an update still keeps the values it leaves out. Send0for unlimited. See provisioning API. - A reseller editing another owner's package (
PUT /api/packages/{id}) got "your own plan does not allow…", which told it the id exists; it now gets 404 first. - Git deploy of Laravel picked PHP 8.2 (the lowest version matching
^8.2) although 8.3 and 8.4 were installed, and the new website was warned at once that PHP 8.2 support ends soon. The newest installed PHP within composer's range that is not near its end of life is now picked (a redeploy keeps the site's version when it still qualifies). - Task logs showed raw terminal colour codes (
[36mvite…). Escape sequences are removed when a log is stored and read, also for the API, and a redrawn progress line keeps only its last state. - Update to latest on an app already on the newest release of its line restarted it, skipped the backup and said "Completed successfully". Nothing is done now, and the panel says the app is already up to date.
- The WordPress (and PHP app) installer suggested
adminas the admin login, which the panel's own WordPress security check then flags. It now suggests one made from the domain and 4 random characters (shop_k7m2), still editable. - Requesting a certificate without an administrator e-mail told resellers and customers to "set an administrator email in Settings", a page they do not have. Certificates are now issued without asking for one.
- Website members saw a New website button that failed with "choose the hosting account that will own this resource". The button is hidden for them, and the account's own pages (File Manager, databases, new websites) answer that they are for the account owner.
- White-label for a reseller's customers. The sidebar showed "v0.4.29 PRO", the sign-in page and tab title always said ZoPanel, customer notifications, e-mailed announcements and the AI assistant named ZoPanel,
/api/dnsreturned the server's nameservers and new zones had the server's nameserver in their SOA. A reseller's customers now see its brand in all of these, no version or plan, its nameservers in DNS, and new zones whose SOA names its primary nameserver. The rule is unchanged and now documented: a reseller's own brand comes with reseller accounts (Pro), the server-wide panel name needs the White-label feature (Business). See reseller docs. - A staging copy or clone at the website limit said only "allows 4 websites"; the message now says the copy is a website of its own and counts toward the limit.
- Messages gave
http://for websites with a certificate ("Uptime Kuma is available at http://…", "Ready: http://staging…"); they givehttps://once the certificate is there. - The WordPress install log was full of "Warning: File should not exist: wp-includes/php-ai-client/…". These are the leftovers of file names wp-cli's unpacker cut short: they are removed, with one line saying so.
wprun by the account (cron jobs, terminal, SSH) could not create its cache folder when HOME was the root-owned account folder;WP_CLI_CACHE_DIRnow points into the account's own~/.home.- Docker app websites no longer show the PHP & config tab (their rate limit is under Tools).
- Staging copies, and websites where WordPress was just installed, are listed under Hosting → WordPress at once (not after the next daily check), staging copies with a badge.
- Vietnamese: task names ("Install Ghost on…", "Back up…") and the descriptions of Open WebUI, OpenClaw and Flowise are translated, the Databases page no longer says MariaDB only, and "does not point to this server yet" (SSL) is translated.
0.4.29 — Automatic security updates
24 October 2026
Security: fixes from the package repositories ZoPanel adds (Docker, MongoDB, .NET, Redis, Debian backports) were never installed by the automatic security updates, which only covered the distribution and, since 0.4.27, PHP; they now install automatically, held to the major version installed. WordPress websites whose core has known vulnerabilities are now found and shown, with a one-click update to the fixed release of their branch. ZoPanel's own security releases can install by themselves within about an hour.
Security
- Fixes from the other repositories ZoPanel adds install automatically. Docker's (
download.docker.com, Debian 12), MongoDB's (repo.mongodb.org), Microsoft's (.NET on Debian), the .NET backports PPA (Ubuntu), Redis' (Ubuntu 22.04) and Debian's backports (the 6.12 kernel) were outside unattended-upgrades, so their fixes waited for someone to runapt./etc/apt/apt.conf.d/53zopanel-thirdpartynow adds them;50unattended-upgradesand your edits are left alone, and a file you delete stays deleted. Checked on Debian 12 and Ubuntu 24.04 withunattended-upgrade --dry-run -d, and with a real run on Debian 12 (Docker 29.9.0 → 29.9.2 and containerd 2.4.1 → 2.4.2, and MongoDB back to 8.0.34 from a test downgrade). - Never a new major version by itself.
/etc/apt/preferences.d/zopanel-majorsholds Docker, containerd and Redis at the major version installed, also for OS updates andapt upgrade(Docker 29 gets 29.x fixes, never 30). MongoDB's repository is one series: with an 8.2 repository added by hand, unattended-upgrades still kept 8.0 in our test. Microsoft's repository only supplies .NET packages and never replaces a package of the distribution. - Docker upgrades keep apps running. A Docker upgrade restarts
dockerd; with ZoPanel'slive-restorethe containers keep running (same processes in our tests) and their addresses pause for about 2 seconds. A server whosedaemon.jsonlackslive-restorekeeps Docker out of the automatic updates and gets a one-click update in the Security Center instead. - Services come back on the fixed build. MongoDB's package does not restart
mongod, and Debian has noneedrestart: after every apt run ZoPanel restartsmongod(andredis-server) when it still runs a replaced binary, and starts again any of its own units that failed meanwhile. On Ubuntu,needrestartno longer restarts the panel and its agent, which ZoPanel restarts itself under its update guard. - WordPress cores with known vulnerabilities. Every WordPress website's core is checked daily against WordPress.org's release list. A core listed as insecure is shown in red under Hosting → WordPress, at the top of the website's page (customers see it too) and, for administrators, under Needs your attention, with Update to X: the latest release of the same branch (7.1.1 → 7.1.3), as a safe update with a snapshot and automatic rollback. If WordPress.org cannot be reached the last list is used, and without one nothing is flagged. This is how websites installed before a fix are found, such as those affected by CVE-2026-87902.
New
- Install ZoPanel security releases automatically. A separate setting in Settings → Updates, next to Automatic updates (every release at 04:00): a release marked as a security release in its signed manifest installs within about an hour, at any time of day, with the same guard as any update (database snapshot, health check, automatic rollback). It waits while a backup, restore, import or account move runs, retries a failed download up to 3 times, and never installs again a release that was rolled back. On by default for new installs (
--no-auto-security-updatesto turn it off); servers installed before keep it off and are asked once on the dashboard. Each step is in the activity log, and the new Security release installed automatically alert says when it happened. - Release manifests can carry a
security_floor: a regular release published after a security release still tells a server that missed it that it lacks a fix. Panels before 0.4.29 ignore the field. - PHP 8.2 support ends on 31 December 2026. From 90 days before (3 October 2026), websites on PHP 8.2 show "PHP 8.2 gets security fixes until 31 December 2026" on their page and in the Security Center (No websites on a PHP version whose support ends soon); from 1 January 2027 they count as end of life. The dates come from one table of PHP's supported versions, so PHP 8.3 and later follow by the calendar. Nothing is switched by itself.
- Security Center: No updates waiting from … for each repository ZoPanel added, with a Fix that installs them now within the held versions; Fixes from the repositories ZoPanel added install automatically.
Fixes
- App Store on Ubuntu 22.04. Installing an app failed with "failed to setup loop device": on systemd 249 the agent's
ProtectClocksetting also limited it to the clock device, so it could not mount the app's data volume. The setting is removed; existing servers fix their agent unit by themselves at start. - Installing a component no longer fails at once when another
aptis running (the daily automatic updates, a fresh VPS's first-boot upgrade, an administrator's ownapt): it waits up to 10 minutes for it. - The web application firewall is shown as not available on Ubuntu 22.04, which has no ModSecurity module for nginx, instead of failing to install.
- Servers with dedicated IP addresses no longer reload Postfix every 10 minutes: the sending setup is only rewritten when it changed.
Documentation
- Updating explains security releases and the other repositories' updates; WordPress the core check; Websites has a table of PHP versions and their end dates.
0.4.28 — App Store security updates
23 October 2026
Security: Gitea 28.2.0 (nine advisories of 28.1.0, among them an account takeover through OpenID linking, GHSA-mf69-7pqq-86vx) and Flowise 3.1.3 (27 advisories of 3.1.2, several of them remote code execution) for apps installed earlier, applied with one click after a backup and undone by itself if the new version does not keep running; the Docker tab and the dashboard now say when an installed app has a security update waiting, and list the vulnerabilities that will never be fixed in File Browser and Ghost 5.
Security
- Gitea 28.2.0. The App Store's Gitea is pinned to 28.2.0 (18 October 2026), which fixes nine advisories of 28.1.0: an account takeover through OpenID account linking (GHSA-mf69-7pqq-86vx), SSH certificate principals matched to other users' keys (GHSA-vcp6-2qc6-gvq3), an unbounded request body in the Actions artifact API (GHSA-6f9g-7jgm-m5ph), draft-release and attachment leaks across repositories, an unauthenticated crash and three smaller ones. New installs get 28.2.0; installs made before keep 28.1.0 until an administrator updates them (see below). See Gitea.
- Flowise 3.1.3 for existing installs. Flowise is no longer offered (discontinued upstream), but installs made before 0.4.25 run 3.1.2, which has 28 published vulnerabilities, several of them remote code execution (sandbox escapes in the code nodes, the CSV agent, the SQLite record manager) and unauthenticated access. Update to latest now moves them to 3.1.3, which fixes 27. The last one is fixed only in 3.1.4, the project's final release, whose official image does not start (
this.db.exec is not a function, on new and existing installs alike): ZoPanel stays on 3.1.3 and the Docker tab lists GHSA-8gj2-2cvc-6xx7 as not fixed. In 3.1.3 the two ReAct Agent nodes no longer load (a fault of the official image): flows built on them must move to Tool Agent, which the notice says before you update. See Flowise. - Security updates are shown. When the catalog's pin of an app's version line fixes published vulnerabilities of what an install runs, its Docker tab shows Security update: with the advisories and an Update to button for administrators (customers see the notice and ask their provider), administrators get The app of has a security update waiting under Needs your attention on the dashboard, and
GET /api/sites/{id}/dockerreturnssecurity_update. They are not installed automatically: a new release may convert the app's data, so the administrator picks the moment, with one click. - Known unfixed vulnerabilities are listed. File Browser (archived upstream, no longer offered) has 18 published vulnerabilities in its last release, 2.63.23, that will never be fixed; its Docker tab now lists them and says to uninstall it or restrict access (a password-protected directory
/on the website's Tools tab). The Ghost 5 has reached its end of life notice now says that 27 published vulnerabilities of Ghost 5.130.6 are fixed only in Ghost 6, among them a SQL injection in the Content API. Both show as known vulnerabilities that will not be fixed on the administrator's dashboard. See Updates and security updates.
Changed
- Update to latest backs the app up first. The button now asks for confirmation, and with Back up the app's data first ticked (the default) the app's data is archived before the new image starts on it, like Back up now; if the backup fails, the app is not touched. Apps without data and updates to the build already running skip it.
POST /api/sites/{id}/docker/updatetakes{"backup": false}to skip it. - A failed update is undone. After a new build starts, ZoPanel watches the app for a minute and a half. If it stops or keeps restarting, the build it ran before is started again and the backup restored, and the task fails with … does not keep running, so the update was undone. Before, an update that crashed the app was reported as done.
- Containers created again for another reason than an update (after Docker's user-namespace isolation is turned on) keep the exact build they ran: an earlier pin of the app's line stays allowed by the agent for the installs that run it.
Fixes
- The vulnerability watch follows each line's current pin only (earlier pins kept for existing installs are left out of its inventory).
0.4.27 — Node.js and PHP security release
22 October 2026
Security: Node.js 22.23.4, 24.22.1 and 26.12.1 (CVE-2026-111497, a remote code execution in the Brotli decoder, and nine more), installed automatically on servers that already run Node.js 22 or 24, and Node.js apps restarted on them without downtime. PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 (PHP2Shell, CVE-2026-109618 and CVE-2026-109619, an unauthenticated remote code execution) installed right after the update, PHP fixes installed automatically from now on, and every website's running PHP moved to the fixed build without downtime.
Security
- Node.js security releases of 21 October 2026. Node.js 22 now installs 22.23.4 and Node.js 24 installs 24.22.1. They fix CVE-2026-111497, a remote code execution in the Brotli decoder, and nine other vulnerabilities. The checksums come from the signed
SHASUMS256.txtof each release, verified against the Node.js release keys. - Installed Node.js versions are patched in place. A couple of minutes after the panel restarts on this version, every installed Node.js major older than its new release is upgraded where it is: the new build is downloaded, checked against its pinned SHA-256, must run and report the right version, gets pnpm and yarn, and replaces the old one in one atomic rename (the old one is put back if the new one does not run). Node.js apps on that major are then restarted the way a deploy switches releases (the new process takes the traffic only once healthy), so visitors see no error. Stopped and suspended apps are left alone and start on the new build next time. Each step is in Tasks and the activity log. If nodejs.org cannot be reached, the installed version keeps running, ZoPanel tries again after a day or at the next restart, and the failure shows in the Security Center and under Needs your attention on the dashboard. See Node.js apps.
- Go 1.27.3 and 1.26.10 (security fixes to
crypto/x509, 19 October 2026) are the Go versions installed under Runtimes. Installed Go toolchains are not changed: reinstall them from the Go card. - uv 0.13.5. uv 0.13.4 removed the compromised emSign ECC Root CA - G3 from its certificate store (GHSA-hq85-5cpj-mr62). Runtimes now offers to install uv again when the installed one is older (Composer likewise).
PHP
- PHP2Shell (CVE-2026-109618, CVE-2026-109619) fixed on every server. PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 (21 October 2026) fix an unauthenticated remote code execution (CVSS 9.8). Right after the update to 0.4.27 the agent installs the fixed builds of the PHP versions installed on the server: only their
php*packages, nothing else, again every 5 minutes while apt is busy. Ondřej Surý's repository also published the fix for PHP 7.4, 8.0 and 8.1 (7.4.33-31, 8.0.30-25, 8.1.34-9), so those are updated too. - PHP fixes now install automatically. PHP comes from its own repository (packages.sury.org, the ondrej/php PPA), which unattended-upgrades did not include, so fixed PHP packages were only installed by hand. ZoPanel now adds it in
/etc/apt/apt.conf.d/52zopanel-phpon new servers and on existing ones with automatic security updates on;50unattended-upgradesand your own edits are left alone, and a file you delete stays deleted. - Running PHP moves to the fixed build. Each account's PHP-FPM master (and Adminer's and webmail's) kept running the old binary after an upgrade until it was restarted. After every PHP upgrade, by unattended-upgrades, OS updates or
aptby hand, ZoPanel now reloads each master still on a replaced binary (running requests finish) or restarts it, and records it in the Activity Log. - Security Center: new checks for PHP security updates waiting (with a Fix that installs them), PHP masters still running a replaced binary, PHP's repository missing from the automatic updates, and websites on PHP 7.4, 8.0 or 8.1, which get no official fixes (move them to 8.2 or newer; ZoPanel never switches them by itself).
New
- Node.js 26 can be installed under Runtimes (26.12.1). It is the Current line and becomes LTS on 28 October 2026; 24 remains the recommended version for production.
- End-of-life Node.js is flagged. Node.js 18 and 20 no longer get security fixes. They stay installable for the apps that need them, but the Runtimes card marks them end of life, an app running one shows "Node.js 20 has reached end of life and gets no security fixes; switch to 22 or 24" on its Deploy tab, and the Security Center lists those websites (No website runs an end-of-life Node.js). ZoPanel never switches an app to another major version by itself.
- The Deploy tab shows the exact Node.js version the running app uses (for example Node.js 24.22.1).
Documentation
- Node.js apps has a table of the supported versions with their end-of-life dates and explains how security updates are installed.
0.4.26 — Migrate from aaPanel, new-version notices
22 October 2026
New
- Migrate from aaPanel (beta). Migrate in → Move a whole server now reads an aaPanel server over SSH (root, or a user allowed to use
sudo): its websites, domains and aliases, PHP version, MySQL databases, certificates, FTP logins and cron jobs, from aaPanel's own database and vhost files. You review the list, choose which account each website goes into (one per website, or several in one account) and a package, and ZoPanel moves the files, dumps each database on the old server with its own login and imports it as the account (never as root), installs certificates that are still valid, and rewrites the website's config file (wp-config.php,.env) with the new database names. Every website gets its own system user and PHP-FPM pool here, and the old server is not changed. Cron jobs tied to a website run from the account's own crontab; custom rewrite rules, aaPanel's own tasks, email and Node/Python/Docker projects are listed in the report for you to handle. Without SSH from the new server,scripts/aapanel-export.shbuilds the same package on the old server for Upload a backup. It is a beta: tested against aaPanel 7 in our lab, not yet on many real servers, so move a few websites first and check them. See Migrate from aaPanel. - You see when a new version is out. When a newer release exists, full administrators get ZoPanel X is available in Needs your attention on the dashboard, with the first lines of the release notes, a What's new link to this changelog and an Update button to Settings → Updates, plus a dot on the Settings menu. A security release is shown as a warning. The panel uses its last check of the update server (at most every 12 hours and right after it starts): loading the dashboard never contacts it. Limited administrators, resellers and customers do not see these notices.
- The Update available alert includes the first lines of the release notes and the changelog link. It is on by default on servers installed with 0.4.26 or later; servers installed earlier keep the choice they had (off unless you turned it on).
Changed
- Release manifests can mark a security release (an optional
securityfield). Panels before 0.4.26 ignore it and verify and install such releases as before; notes that start with "Security:" mark a security release too.
Fixes
- The deploy log of an app no longer ends with empty brackets ("Deployed Node.js () to …") when the deploy has no commit, such as an upload: it names the runtime version when known and the commit only when there is one.
0.4.25 — App Store versions kept current
22 October 2026
App Store
- Ghost 6 for new blogs. Ghost 5 reached its end of life in January 2026 and no longer gets security fixes, so new installs now run Ghost 6, still with its SQLite database. Blogs installed earlier keep running Ghost 5 untouched: Update to latest stays on Ghost 5, and the Docker tab says Ghost 5 has reached its end of life. An administrator upgrades with Upgrade to Ghost 6: the blog's data is backed up first, and Roll back to Ghost 5 restores that backup if something is wrong. Check your theme before upgrading; the Ghost guide explains what to look at.
- Uptime Kuma 2 for new installs. Existing installs keep 1.x and are offered Upgrade to Uptime Kuma 2 in the same way (backup first, rollback available). The first start of version 2 migrates the database, which can take a while with a long history: see the Uptime Kuma guide.
- Flowise is no longer offered. The project has ended (its repository was archived in August 2026) and gets no more security fixes. Existing installs keep running and can still be managed, backed up and uninstalled; their Docker tab shows that Flowise is discontinued, and the Flowise guide explains how to move off it.
- No silent major upgrades. Updating an app, or recreating it after Docker's isolation is turned on, never moves it to a new major version: only the administrator's upgrade does.
Fixes
- Next.js standalone apps listen on the right address. Node apps now get
HOSTNAME=127.0.0.1as well asHOST, because theserver.jsof Next.js standalone builds readsHOSTNAME.
Documentation
- The security page now describes how PHP is really isolated: a systemd sandbox that only shows each account its own home directory, not
open_basedir. - Uptime checks are described as they run: each website about every 3 minutes, every minute while it fails.
- The partners page says white-label comes with the Business license, as the licensing page does.
0.4.24 — Package API for billing systems
19 October 2026
New
- Full package management in the provisioning API. Besides listing and
PUTby name,/api/v1now hasPOST /api/v1/packagesto create a package (409 if the name exists),GET /api/v1/packages/{name}for one package andDELETE /api/v1/packages/{name}to delete one. A package still assigned to accounts is not deleted (409package.in_use).
Changed
- Updating a package with
PUT /api/v1/packages/{name}keeps the limits the request leaves out. Before, they were reset to 0 (unlimited).
Fixes
- App Store: long image names no longer spill out of the app cards and break the grid. Cards show the name and version; the full digest appears on hover.
0.4.23 — Checked against other panels' known vulnerabilities
16 October 2026
We went through 29 kinds of vulnerability published for cPanel, DirectAdmin, Plesk, HestiaCP, CyberPanel, CentOS Web Panel and Webmin, checked how ZoPanel handles each, and added over 60 automatic tests so these protections cannot quietly break later.
Security
- FTP sub-logins stay in their folder. A customer who replaced a folder in a sub-login's path with a link could make that login open somewhere else. Each sub-login's folder is now mounted on a root-owned path when it is saved and at startup, and is refused if its path contains a link. Existing sub-logins are moved over automatically.
- No requests to internal addresses on a customer's behalf. Pulling a Docker image, following a WordPress site's redirects during its health check, the Git build sandbox and importing a backup from a URL all refuse loopback, private and the server's own addresses.
- The WordPress one-click login only opens on the website's own domain or aliases.
- The file manager refuses links that lead outside the home folder, including links whose target does not exist.
- Cron jobs run in the same sandbox as the website's PHP.
- New installs set the firewall to deny incoming connections by default, and the Security Center warns when a server's firewall default is not deny.
- MariaDB only reads and writes files in a dedicated, locked folder (
secure_file_priv), and MongoDB only listens on the server itself. - Admin notifications to Discord and Slack can no longer mention
@everyonefrom text a visitor typed, and notification webhooks no longer follow redirects. - Disk quotas that could not be applied are now reported in the Security Center and by
zopanel doctor.
Fixes
- Importing a cPanel or DirectAdmin account that contains links no longer stops halfway: links inside the account are kept and rewritten, links leading outside are dropped.
0.4.22 — Hardening from an external security review
15 October 2026
Security
- Database growth is checked far more closely. Imports read only the file that was checked (no FIFOs or swapped files), are bounded, reserve their space first and are stopped when the database outgrows what they reserved. Database sizes are now measured every 2 minutes instead of up to every hour, and an account over its package loses write access to its databases until it is back under. This is not a hard limit: between two measurements a database can still grow past the package. Restoring the database permissions now gives back exactly what each user had (before, a lock and unlock could leave a read-only user with all privileges).
- Backups are counted by what they expand to. Mail archives and database dumps inside a backup are scanned and reserved by their real size; sparse and nested compressed entries are refused. Concurrent restores reserve their staging space.
- App backups and storage are kept in check. App backups reserve their size on the server's disk, are bounded and run one at a time; buckets and app data volumes share one allocation, kept across a crash.
- Fail closed at boot. Apps start only when the firewall rules are in place; an IPv6 firewall error is no longer taken for "no IPv6"; the panel refuses to start an app whose data volume is not mounted; installation stops if the firewall cannot be enabled.
- HTTPS proxies to an IP address verify the certificate, and a comment can no longer skip that check in custom nginx settings.
- Verified installation. The recommended install downloads
install.shwith its signature and checks it against the release key before running it. The storage engine image is pinned by digest. - Release signing works on a snapshot of what was checked.
Fixes
- Backups to your own S3 storage that fail are retried, and a local backup is kept until its remote copy is confirmed; remote copies are checked by SHA-256.
- Reserved local ports are merged with the system's own reservations.
0.4.21 — Every runtime and database checked
14 October 2026
Security
- App ports are closed to the outside. An app that listened on all addresses could be reached directly on its second (zero-downtime) port, bypassing nginx, the WAF, IP blocks and TLS: that port range overlapped the FTP passive ports opened in the firewall. App ports now accept connections from the server itself only, and the FTP passive range moves to 18000–18100 (existing servers switch by themselves once no FTP session is open; open 18000–18100 in your cloud provider's firewall if it has one).
Fixes
- Redeploying a PHP app (Laravel and others) no longer drops requests, and no longer briefly interrupts the account's other PHP websites.
- Deleting a Redis database deletes its keys too, also when the whole account is deleted.
- A
.python-versionfile with a comment line before the version is read correctly. - New automated check of every runtime (Node, Python, Ruby, Java, .NET, Go, PHP) and database engine (MariaDB, PostgreSQL, MongoDB, Redis) with real sample apps, run before each release.
0.4.20 — Fixes from a role-by-role test
14 October 2026
Security
- A suspension set by your provider stays in place. A customer could lift a website suspension made by its reseller (or a reseller one made by the administrator) by suspending the site again and then lifting it. A second suspension now keeps the first one's owner.
- A limited administrator without the DNS area no longer sees the DNS cluster's secrets.
Fixes
- A limited administrator follows the tasks it starts (backups, website setup) and sees only the tasks of the accounts it manages, on the task list and the dashboard.
- The mail and DNS areas of a limited administrator open the Email and DNS pages.
- File manager errors are shown in your language and never include server paths.
- A page your hosting package leaves out says so, without a button to create something.
- A reseller changing its own package is refused with a clear message instead of being ignored.
- Object storage engine details are shown to administrators only.
0.4.19 — Fixes for a freshly installed server
13 October 2026
Fixes
- Autoreplies and mail filter rules work right after a fresh install. The panel's agent starts before the mail service is installed in the background, and it treated the mail folders as foreign until its next restart, so saving a filter or an autoreply failed. It now recognises the mail service's folders as soon as mail is installed.
- The Backups page no longer crashes on a new server before its first incremental snapshot: the snapshot list answered something the page took for a list.
Security
- Hosting accounts can no longer use the names of system service accounts (for example
vmail), and the root agent trusts the mail system's account only when it really is that system account. - Shrinking an app's data volume is safe across a panel restart: the app is always put back, and a volume is never mounted while it is still being resized.
- The error report service limits how much any sender can upload.
- Smaller fixes: the dhcpcd rule is placed among the global options, error reports are never dropped from the queue by mistake, support bundle previews of other administrators are kept.
0.4.18 — Several apps per account
12 October 2026
Fixes
- An account can run as many App Store apps as its package allows. Until now the first app's data volume took all the disk space the package had left, so a second app was refused with "no disk space left". Each new app now gets an even share of what is left for the apps the package still allows.
- Servers that already have such a full-size volume fix themselves on the next app install: the old volume is checked and shrunk (only down to its data plus a safe margin, with the app stopped for a few seconds), then the new app installs.
0.4.17 — First website in one step, error reports
12 October 2026
Easier to start
- New website works on an empty server. With no hosting account yet, the dialog offers My own website (the panel creates a separate, isolated hosting account for you and puts the site in it) or For a customer (create the account right in the dialog, then the site). Database, mail and other "new" dialogs offer the same instead of an empty owner list.
- Starter packages on new installs: Basic, Business and Pro, with SSH, custom Docker and App Store containers off until you turn them on. Existing servers keep their packages.
- Resellers without a package can create one from the account form, within their own plan.
- A Getting started card on the dashboard shows the steps (packages, first account, first website) until the first website exists.
Fixes
- On servers whose network is brought up by dhcpcd (some VPS images), creating a Docker network could make dhcpcd delete the server's own routes and cut it off the network until a reboot. ZoPanel now keeps dhcpcd off Docker's interfaces.
Support
- Anonymous error reports (on by default, one switch in Settings → Support to turn off): when a task fails or the panel crashes, the panel sends the version, OS, task type and error code — never domains, usernames, emails, IPs or file contents. See the "Error reports" guide for exactly what is sent.
- Send to support on a failed task and in Settings → Support: preview the diagnostic bundle, then send it or download it.
0.4.16 — The panel speaks your language, paged lists
10 October 2026
Easier to use
- Error messages in your language. Every message the panel shows (limits reached, invalid input, failed tasks) now appears in Vietnamese or English, following the language you chose. API clients keep the same English text and get a stable error code alongside it.
- Long lists are paged and searchable: websites, mailboxes and accounts, plus databases, DNS records, backups, tasks, the activity log and more. Servers with hundreds of accounts open quickly.
- A page that fails to load says so, with a Retry button, instead of looking like an empty list. Settings forms that fail to load are not shown, so empty values can't be saved over real ones by accident.
- Failed tasks leave "Needs your attention" once you have opened the task list, or once the same task ran again and succeeded.
Security
- Security hardening of error messages: they no longer include notification URLs or server paths.
0.4.15 — Ubuntu 26.04, fixes from a full feature check
10 October 2026
Operating systems
- Ubuntu 26.04 LTS is supported. PHP 8.5 comes from Ubuntu until the multi-PHP repository publishes packages for 26.04; the panel then offers the other PHP versions by itself.
- Mail works with Dovecot 2.4 (Ubuntu 26.04 and Debian 13), and PHP 8.5's
mail()reports refused messages as failed.
Fixes
Found by testing every feature as an administrator, a reseller and a customer:
- WordPress Publish to live clears the page cache, so visitors see the new version at once.
- A mistyped two-factor code followed by the right one signs in.
- A reseller's new package starts within the reseller's own plan.
- Cron jobs get a writable home folder (
~/.home), like SSH sessions. - Edited files are served fresh within 10 seconds.
- The backup list names the websites in each backup.
- Mail filed into a folder by a rule still gets the autoreply.
- Icon buttons are named for screen readers, and limit messages use correct plurals.
0.4.14 — Fairer disk accounting, sturdier backups and app installs
10 October 2026
- Package disk space counts what is promised. App data volumes and storage buckets get their share of the package's space when they are created, and a bigger package spreads its extra room among them.
- Remote backup copies are retried. An account backup whose copy to remote storage failed is uploaded again (hourly, before the account's next backup, or with a Retry button) and is never pruned in the meantime.
- Database imports stay within the package: an import is checked against the package's remaining space before it starts, and backups are sized and staged on disk first.
- App Store installs that fail leave nothing behind (website, port, container) and say why. App ports come from a pool, so very large servers never run out.
- On a fresh server, remote backup copies can be listed and fetched before the license is restored, so disaster recovery starts right away.
- Changing a password, suspending or deleting an account ends its sessions and API tokens in the same step.
- The Security Center shows disk quotas that are enabled but wait for a restart as their own state.
- Security hardening of backup restores, the temporary folders of older installs and team members with view-only access.
0.4.13 — Security hardening, app backups off the server
10 October 2026
Backups
- App backups off the server. Backups of App Store apps, Docker deploys and the S3 storage component are copied, encrypted, to the remote storage used for account backups, and can be fetched back on any server for disaster recovery.
- Remote backups must be encrypted (an administrator can still accept an older unencrypted one). SFTP remote storage can sign in with a private key, and its host key is pinned.
- Account backups are bound to their owner and checked before every restore.
- A failed remote copy of an app backup is never reported as done, and it is retried.
Limits
- Hard limits on app data volumes, PostgreSQL and MongoDB databases; storage buckets never exceed the package.
- Accounts close to or over their disk space are measured again every 10 minutes.
- Setup needs disk quotas (or an explicit
--allow-no-quota), and the Security Center reports quotas that are off.
Security hardening
- Sign-in: cross-site sign-in requests are refused and only one two-factor step is pending at a time.
- Updates: strict version checks, release keys that can be rotated and revoked, and protection against an older release being replayed. Third-party components installed as root come only from pinned, checked releases.
- Security hardening of custom nginx, PHP and MariaDB settings, Docker builds, reseller plan features, staging push, webhooks and "sign in as" sessions.
Panel
- Form fields are labelled for screen readers; the Usage page is for administrators and resellers.
- Importing the configuration keeps the backup repository password of a server that has its own.
0.4.12 — Disk limits that hold, safer first sign-in
9 October 2026
- Accounts over their disk space are held, not only warned: their databases become read-only (deleting is still allowed, to make room) and their Docker apps are paused until they are back under the limit.
- An account's disk use now counts mail, databases, app data and app backups as well as its home folder. Mailbox sizes stay within the package's disk space.
- The shared Redis gets a memory cap (10% of RAM).
- Safer first sign-in: the installer prints the panel certificate's fingerprint to compare in the browser, and an SSH tunnel command that needs no certificate check.
- Security hardening of updates, uploads and archives, the firewall for containers and app ports (closed from boot on), app ports (never shared between accounts), server settings edited in the panel, and connections between servers.
- Adminer, SnappyMail, ionCube and Docker images are pinned to checked releases.
- Documentation: Ubuntu 24.04 or Debian is recommended; the web application firewall is not available on Ubuntu 22.04.
0.4.11 — Fixes from role-by-role acceptance tests
9 October 2026
- App Store apps can be uninstalled; the data you choose to keep stays with its owner.
- Customers can start, stop and restart their own apps.
- Account shells (terminal, SSH, SFTP) no longer see other accounts' names and domains.
- WordPress maintenance mode shows visitors the maintenance page while wp-admin and the panel's one-click login keep working.
- S3 backups: restored accounts get their mail back, and endpoints may be written with
https://. - Fixed: accounts could not be edited from the panel; a cron schedule out of range stopped the account's other jobs; welcome e-mails and alerts were not always delivered; changing your password now changes the SSH/SFTP password too; duplicate FTP logins and package names are refused.
- Ubuntu 22.04: newer Redis and restic, and the web application firewall is shown as unavailable.
- Fixed: new WordPress installs could miss files with long names; nginx no longer remembers a missing file for a minute after it is uploaded; a refused Let's Encrypt contact address no longer blocks every certificate.
- Security hardening from an internal audit.
0.4.10 — App backups, two-factor self-recovery, app runtimes
9 October 2026
- App and S3 storage backups with their own schedule: back up now, daily or weekly, how many to keep, restore. A restore puts the old data back if the app does not start.
- Two-factor authentication: a lost phone can be recovered without an administrator.
- Mail: every mailbox starts with a calendar and an address book; the mail certificate names the mail host name; a forwarder can no longer replace a mailing list.
- WordPress switches to
https://when its certificate is issued. Laravel one-click install on a Laravel website. - Traffic and bandwidth count static files; a month of website logs is kept.
- Cron jobs run inside the account's limits. Upload size can be set per website (Nextcloud gets 10 GB). The File Manager trash is emptied of old items daily. Administrators manage an account's SSH keys.
- Java, .NET, Python and Ruby apps run the version they ask for. Docker deploys get build arguments, persistent paths and builds within the account's limits; the panel's variables are merged into a shared
.env. - Fixed: accounts could not be created on Ubuntu 22.04.
0.4.9 — Fixes and 36 new guides
9 October 2026
- Mail: a catch-all no longer takes the mail of real mailboxes.
- SSH keys can open a terminal.
- PHP apps require the PHP versions that are actually installed; three App Store and Docker deploy fixes.
- Malware alerts count only what still needs a look; a clearer message while an upload is busy.
- The tuning page no longer fails on a fresh server; the installer adds the PHP repository more reliably.
- Documentation: 36 new guides in English and Vietnamese.
0.4.8 — Container isolation, tighter API tokens
9 October 2026
- Containers are isolated: no connections between containers or to private and internal addresses, and only the server's web, mail and DNS ports are reachable. A customer's own Dockerfile or image needs a package option (off by default).
- API tokens can only reach an explicit list of actions.
- The root shell was removed from the panel. Administrators open a hosting account's shell from Terminal and the server's own over SSH.
- Go and dependencies updated; releases are blocked while a known vulnerability is open.
- The sign-in limiter uses bounded memory.
0.4.7 — Move whole cPanel and DirectAdmin servers
9 October 2026
- Move a whole cPanel or DirectAdmin server over SSH. The panel signs in to the old server (the password or key is never stored), lists its accounts and moves the ones you choose in the background, with live progress.
- DirectAdmin backups bring their DNS zones.
- Account moves between ZoPanel servers carry SSL certificates, DNS zones, and SFTP and FTP passwords.
- Updating from the panel works again, and downloads retry after a short network failure.
- The malware scan no longer flags comment-only "Silence is golden" files.
- Faster account deletion.
- Security hardening from a second full internal audit (local services, imports, file permissions, sales website and license server).
0.4.6 — App Store setup lock, new dashboard
8 October 2026
- Setup lock: apps whose first visitor becomes the administrator answer only their owner until setup is finished.
- App images are pinned to the versions tested with each release; free disk space is checked before an install or update; Vaultwarden gets an admin token; Ghost can send mail through your SMTP server.
- Dashboard: a "Needs your attention" list with a fix button for each item, your websites at a glance, a getting-started checklist and a backup card for customers.
- Security hardening of the setup lock and app ports.
0.4.5 — App Store fixes
8 October 2026
- Docker on Debian 12 moves to Docker's own packages, so current images (n8n and others) install; existing apps and their data are kept.
- OpenClaw works behind the panel's proxy, and new browsers are approved from the panel.
- PHP's
putenvis allowed for websites (MediaWiki and many frameworks need it). - Guides: what each App Store app does, and its first-time setup.
0.4.4 — Hardening and fixes
8 October 2026
- Security hardening of the panel database's file permissions and of backup file access.
- Fixed: redirects, hotlink protection and password-protected folders could stop being applied.
0.4.3 — Reseller tools, file manager, SSH and remote backups
8 October 2026
Accounts and resellers
- Move an account to another ZoPanel server. Websites, databases, mail and cron jobs move in one job; the old copy keeps serving until DNS points to the new server and is removed afterwards.
- Log in as a customer (administrators, and resellers for their own customers), welcome e-mails with sign-in details, announcements shown in customers' panels, a reseller overview and reseller branding (panel name and own nameservers).
- Accounts list with filters, sorting and bulk actions; move a customer to another reseller; suspension reasons shown to the customer.
- Monthly bandwidth limits with warnings at 80% and 100%, and optional suspension until the next month.
- Feature Manager per package; limits on forwarders, mailing lists and domain aliases; administrators limited to chosen areas.
Hosting
- File manager: permissions dialog and "Fix permissions", move, search, trash with restore, folder upload and image preview.
- FTP with the account's own login (TLS required), and a FileZilla site file.
- SSH for accounts with shell access (git, rsync, scp, sftp), inside the sandbox.
- Database users with chosen privileges on each database; repair and optimize.
- PHP extensions per version (ionCube, memcached, APCu and more) and more per-site PHP settings; MariaDB and PHP server overrides, undone if the service cannot start.
- Cron output by e-mail, mail client autoconfiguration (Thunderbird, Outlook, Apple), whole access and error log downloads, and customers can upload and restore an account backup.
Backups and migration
- Remote backups to SFTP, FTP, Google Drive, Dropbox and Backblaze B2, encrypted.
- Migration over SSH: package a cPanel account on the old server and import it.
Security and performance
- Country blocking at the firewall (never your own address); fail2ban trusted addresses; the blocklist check covers every public IPv4 of the server.
- Security hardening from internal reviews: database imports, API tokens, "sign in as" sessions and website folders.
- Faster account lists, dashboard and uptime checks on servers with many accounts.
0.4.2 — Several servers, AI for customers, panel on phones
7 October 2026
Several servers
- Automatic placement. When a server is full (disk, memory or a number of websites you set), new hosting accounts — from the panel, the provisioning API or WHMCS — are created on the connected server with the most room. The package goes with them, billing keeps talking to one server, and calls for those accounts are passed on.
- Accounts already running are never moved by themselves (their IP would change). The panel lists the largest ones with a one-click move and warns once a day while a server is full.
AI assistant for customers
- Explains why mail lands in spam (MX, SPF, DKIM, DMARC) and why a website is slow (plan limits and the last 24 hours of CPU and memory), and looks at backups and snapshots.
- Proposes everyday tasks for the customer to confirm: databases, mailboxes, forwarders, cron jobs, FTP accounts, backups and restores. Passwords are generated by the panel and never pass through the AI.
- Each package sets how many questions a day its accounts may ask.
Panel
- Works on phones: tables become cards, tabs scroll, nothing runs off the screen.
- Customers and resellers get their own menu, a Contact support link (yours, or the reseller's own) and an activity log in plain words; tools the server or plan does not offer are hidden.
- The tuning advisor opens at once instead of measuring for a minute on large servers.
Fixes
- Security: a new account could see the activity (sign-ins, IP addresses) of a deleted account that had the same internal ID. IDs are never reused now, and activity from before an account existed is never shown.
- Resellers that host websites themselves could not create customers unless overselling was on.
- Accounts whose system user had disappeared could not be deleted.
2026-10 — Security and operations release
The largest release so far. It went through several rounds of internal security audit and was measured on real VPS servers under heavy load.
Performance and capacity
- Sized to the server automatically, from a 2 GB VPS to large machines. Settings shows the memory plan: the limit for customers and the reserve kept for the system.
- PHP on demand. A website's PHP pool starts with its first request and stops when idle, so quiet accounts use no PHP memory. Restarts and PHP version changes happen without dropping requests.
- Faster wake-up: compiled PHP code is cached on disk, and pools stay ready under an "always on" policy where you choose it.
- Memory compression in RAM. On Linux 6.8 and newer, customers' idle memory is compressed in RAM instead of hitting the limit, and it is never swapped to disk.
- Overload recovery in minutes. Short request queues make overload fail fast instead of collapsing; when memory is badly short, requests that have waited too long are dropped and their visitors see a "busy" page, so the server recovers soon after the load stops. Measured on our test servers: back to normal in 2 to 5 minutes after a heavy overload.
- Page cache: expired pages are refreshed in the background and kept for a day; cached pages are also served to visitors arriving from ad campaigns; a WordPress site's cached pages are cleared when its content changes; cache entries are keyed by site, not only by host name.
- Scheduled work and account creation stay fast with hundreds of accounts; settings are applied to web server configurations in batches after updates.
- Fixed: on servers with several hundred sites, nginx could keep an old configuration after a change.
- Database sizes in the list are read from the files on disk, so the list loads quickly.
WordPress
- Scheduled tasks run by the server. For new installs, WordPress's visitor-driven wp-cron is switched off and a timer runs due tasks every 5 minutes, as the account, at low priority. Scheduled posts and shop e-mails run on time on quiet sites, and busy sites lose an extra request per visit. It follows the site's PHP version, pauses while the account is suspended and can be switched off per site.
- New WordPress and PHP apps are warmed up right after installation, before the first visitor.
- Installations retry the WordPress download after a network hiccup, and wp-cli's download is no longer left in the account.
Security
- Docker apps isolated with user namespaces; app data is closed to hosting accounts.
- Mail sending limits cannot be bypassed from account processes: PHP command line, cron jobs, forwards, catch-alls, plus-addresses and Bcc headers all count.
- No root file access through customers' links. Backups, dumps, restores, ownership changes and scans read customer files as the customer or one path step at a time, never following an account's symlinks.
- Resellers cannot grant more than their own plan: packages, disk and website totals stay within it unless overselling is allowed.
- Two-factor authentication: attempts are throttled before the code is checked, codes cannot be reused, recovery codes are available, and 2FA can be required for administrators or for everyone.
- IP allowlist applies to connections from the server itself too.
- API tokens are revoked on password and 2FA changes, created only with the password, and cannot change security settings, backups, hooks or administrator logins, or read secrets. Single sign-on from a billing system opens customer sessions only.
- Shared Redis denies scripts to account users.
- Secrets encrypted at rest: panel settings, 2FA secrets, external database passwords, app environments.
- Tamper-evident activity log (hash chain, visible in the Security Center), with a copy in the system journal and optional remote syslog.
- Malware quarantine moved to a root-only folder.
- Custom nginx directives are checked against an allowlist; proxying to the server's own addresses is refused.
- Websites that are subdomains of another account's domain need an administrator.
Updates and disaster recovery
- Safe updates: a database snapshot is taken first, the new version is health-checked, and the binary and database are rolled back automatically if it is not healthy.
zopanel rollbackundoes an update by hand. - Disaster recovery: the configuration backup now carries the whole panel database and its keys, encrypted;
zopanel ctl dr-restorerebuilds the panel on a new server. Daily local database snapshots are kept for 7 days. A disaster-recovery runbook is in the documentation. - Installer: brings a fresh server up to date first, installs a newer kernel where supported (asking once, with a single restart), and accepts a license key with
--license.
Backups
- Remote backups are encrypted before upload, with checksums checked after downloads and before every restore, and a weekly repository check.
- Nightly full and incremental backups cut short by a restart are resumed or caught up, without false alerts.
- No backup starts on a nearly full disk.
Operations
- Service watchdog: installed services are probed every minute and restarted when stopped or hung, with an alert for each event.
- Suspension stops everything: mail logins, FTP, cron jobs, Node.js and Python apps, Docker apps and Redis. Incoming mail is kept, and websites answer 503.
- Terminated accounts are kept for a grace period (7 days by default): files and mailboxes moved aside, databases dumped first. Interrupted terminations resume where they stopped.
- New alerts: mail queue growth, the server's IP on a blocklist, accounts without a recent backup, expiring certificates, update failures and new versions.
- Usage history per account (CPU, memory, disk I/O) and hourly website uptime, with graphs.
zopanel ctl doctorandzopanel ctl support-bundlefor troubleshooting; the advisor reports memory compression.- The panel's own certificate renews itself, and mail and webmail pick it up.
- Docker image pulls and object-storage setup retry after registry or network failures.
Migration
- cPanel imports carry DNS zones (including
wwwCNAME records), FTP accounts with their existing passwords, and SSL certificates.
Licensing
- Plans and prices are managed on the license server; licenses carry a database limit. The Free plan allows 10 websites and 10 databases per server.
Fixes
- The PHP idle policy picker shows the saved value at once on servers with hundreds of sites.
- The website Tools tab no longer fails when a site has no redirects, error pages or PHP settings.
- The Hooks page loads when no webhook is configured.
- Customers can open the activity log and App Store, and one-click webmail login is no longer blocked by the browser.
- Removing an account also removes its Docker apps.
- Limits are applied when a username is re-created; database users can connect over 127.0.0.1.