Nhật ký thay đổi
All notable changes to AIO Panel are documented in this file. The format is based on Keep a Changelog and the project follows Semantic Versioning.
Unreleased
0.3.49 - 2026-11-19
Added
- Accounts on all servers (Servers): one list of every hosting account of every server, with search
and a server filter. New account on a chosen server or automatically on the one with the most
room for its package (free disk, memory and CPU; the dialog shows the ranking), with a fleet-wide
check that the username and domain are free everywhere. Open (single-use sign-in on that server),
Suspend, Unsuspend and Move from the same list. Servers talk through a new peer API
(
/api/cluster/peer/*, administrator tokens only); other servers need 0.3.49 or newer. - Move any account between any two servers from the account list (the copy runs on the source server, which adds the target to its Servers when needed; moving to this server hands the source a one-day token).
- Balance (Servers): disk, memory and CPU of every server, and suggested moves off a server fuller than the limit, largest accounts first, to the server that stays emptiest.
- Versions and updates (Servers): the version of every server and Update selected, one server after another; each must answer on the new version before the next starts, this server goes last.
- Packages on every server (Servers): compares this server's packages with the others' and copies them over (creates missing ones, aligns different limits and features; never deletes).
0.3.48 - 2026-11-19
Added
- Single sign-on (Settings > Security > Single sign-on) with the company's identity provider: OpenID Connect (Google Workspace, Microsoft Entra ID, Okta, Keycloak, Authentik, GitLab...) and SAML 2.0 (Entra ID, Okta, ADFS, OneLogin, JumpCloud...). A "Sign in with ..." button per provider on the sign-in page. A provider account is linked to the existing panel login with the same verified e-mail on its first sign-in, then by its subject id; nobody is created by a sign-in. Per provider: who may use it (administrators, resellers, hosting accounts, team members), allowed e-mail domains, and "only this provider" to turn password sign-in off for linked logins. Profile > Security lists a login's linked sign-ins.
Fixed
- After
aio updateinstalls the GeoIP2 module, country blocking is ready within minutes instead of the next morning (the panel checks its visitor protection config again five minutes after start).
0.3.47 - 2026-11-19
Added
- Visitor protection per website (Websites > site > Security), all in Nginx on this server:
- Flood protection (Normal or Strict): page requests and parallel connections per visitor, answered 429 above the limit. Pictures, styles and scripts are not counted; this server itself is never limited.
- Under attack mode (Always on or Automatic): a short browser check (a proof-of-work puzzle,
under a second) before the website, then 8 hours of free passage with a signed cookie that Nginx
checks itself. Search engines, link previews, uptime monitors, Let's Encrypt and this server pass.
Automatic mode switches it on above a requests-a-minute threshold and off again 30 minutes after
the traffic drops, and notifies the owner and administrators. Paths such as
/api/can skip it. - Country blocking: block a list of countries or serve only them, with the free DB-IP country database the panel downloads and updates monthly.
- Visitor addresses behind Cloudflare and load balancers (Server > Web Server): Nginx takes the
visitor address from
X-Forwarded-Foron requests from Cloudflare's published ranges (refreshed daily) and from proxies the administrator adds. Logs, statistics, Fail2ban, the WAF, rate limits and PHP now see the visitor instead of Cloudflare, and Fail2ban can no longer ban a Cloudflare address. - Use Cloudflare for this website switch on the CDN card: off, the panel never calls Cloudflare for that website.
- The installer and
aio updateinstall the GeoIP2 module for Nginx (libnginx-mod-http-geoip2).
Changed
- The crawler rate limit and the new limits share one
limit_req_status 429line per server block.
0.3.46 - 2026-11-18
Added
- CDN card per website (Websites → site → Optimize → CDN) for websites whose DNS zone is linked to Cloudflare: the zone and its plan, whether each hostname goes through Cloudflare's proxy, Purge this website (its hostnames only, on every plan) and Purge addresses (up to 30).
- Purge after each Git deployment: a deployment or atomic release switch to a website behind Cloudflare purges that website's cache right after; the deployment log shows it. On by default, switchable per website.
- Optimized pictures behind a CDN are handled. With image optimization on and Cloudflare (or any
other CDN) in front, pictures tell the CDN not to store them (
Cloudflare-CDN-Cache-Control/CDN-Cache-Control: no-store), so no browser is handed a format it cannot show. On Cloudflare Pro and up, Cache each picture format separately sets a "Vary for images" rule instead, and the pictures stay cached at Cloudflare. The panel re-checks what is in front of a website every hour.
Changed
- Purge cache on the page cache card now purges only the website's hostnames at Cloudflare, not the whole zone with its other websites.
- The image optimization card no longer asks again before switching on behind a CDN: it says how the pictures are kept right instead.
0.3.45 - 2026-11-18
Added
- Atomic releases for Git deployments. Switch them on under a repository's Settings: every
deployment is copied into a release folder of its own and built there, and the deploy folder (now
a symbolic link) switches to it in one step once the build succeeded. Visitors never see a
half-updated site, a failed build never reaches it, and Switch back to one of the kept
releases (5 by default) is instant, without a fetch or a build. Uploads,
.envand other files that are not in the repository are kept as shared paths; the card lists the candidates before you switch on, and the deploy folder as it was is kept after the first release. PHP runs the new release from the first request: Nginx websites pass PHP the resolved release path, and for Apache and OpenLiteSpeed websites the PHP that serves them is reloaded gracefully right after the switch. Switching off turns the deploy folder back into a plain folder. - The installer test switches atomic releases on for a real repository, deploys twice, checks the link, a shared file and the path PHP sees, switches back without a build and switches off again.
Fixed
- Connect repository: on a phone, a long repository URL squeezed the HTTPS hint into a narrow column.
0.3.44 - 2026-11-18
Added
- Preview environments for Git deployments. Open a repository, go to Previews and switch them
on: every branch other than the deployed one gets its own checkout and its own website at
<branch>.preview.<website>. A push creates or updates the preview, deleting the branch removes it, and a preview nobody pushed to for a while (14 days by default) is cleaned up. A repository that restarts an app gets a second instance of that app per preview, on its own port with a copy of the app's variables. Previews are markednoindex, count as subdomains of the account, and can be limited to branch patterns such asfeature/*. When the DNS zone is hosted on the server the record and the certificate come by themselves; otherwise one wildcard record (*.preview.<website>) is enough, and the tab shows it. - The installer test deploys a real Git repository, creates a preview of a second branch, checks that it is served at its own address and removes it by deleting the branch.
Fixed
- Tab strips that scroll sideways in a narrow window no longer show a scrollbar under the tabs.
0.3.43 - 2026-11-18
Added
- Image optimization warns when a website is behind Cloudflare or does not point to this server:
a cache that ignores
Vary: Accepthands one picture format to every browser. The warning is shown on the card and again before the feature is switched on.
Fixed
- The reverse DNS check could report a healthy server as broken.
aio doctorand Mail health asked the local resolver, which answers for the server's own address from/etc/hosts- with the short name ("srv1"), whatever the provider has published. Both now ask real DNS servers. The same goes for the checks of the server's own name and its SPF record. - A switch whose value arrived right after it was drawn could show its knob on the "off" side while being on. The knob now always follows the value.
- Mail health: tile captions were cut off on phones.
Changed
- Mail health refreshes the server checks and the blocklists every six hours instead of once a night, so a problem (or a fix) shows up the same day - also for customers.
- The installer test installs WordPress, hardens its uploads folder and checks an upload picture as an AVIF browser, a WebP-only browser and an old browser, and that PHP in uploads is refused.
0.3.42 - 2026-11-18
Fixed
- Image optimization: "Optimize now" and the hourly run could convert the same website at the same time. Only one conversion per website runs now; a second request waits for the first.
0.3.41 - 2026-11-18
Fixed
- Image optimization did nothing for WordPress uploads on websites with the "no PHP in uploads"
hardening rule. That rule answers every request under
wp-content/uploadsitself, so the image rule never applied there - and uploads are where most pictures are. The uploads rule now carries the image rule. Websites that already had optimization on are corrected by the next hourly run.
0.3.40 - 2026-11-18
Changed
- Image optimization converts at the lowest CPU and disk priority and waits while the server is busy, so converting a large website does not slow the websites down.
0.3.39 - 2026-11-18
Fixed
- Image optimization with AVIF switched on: a browser that accepts WebP but not AVIF (older Safari) got the original picture instead of the WebP copy. It now gets the WebP copy.
0.3.38 - 2026-11-18
Fixed
- System packages a new release needs only arrived one update later. An update is carried out by the update script of the version being replaced, which installed its own list of packages. The new version's script now finishes the update, so its requirements apply at once. On servers that updated to 0.3.37, the image converters (WebP, AVIF) are installed by this update.
Changed
- The installer test also runs
aio update, so the updater is exercised on every release.
0.3.37 - 2026-11-18
Added
- Image optimization (Websites → Optimize → Images). WebP and, optionally, AVIF copies are written next to JPEG and PNG pictures and served under the same address to browsers that accept them; everyone else gets the original. The originals are never changed, a copy is kept only when it is smaller, and new pictures are converted every hour. One click removes the copies again.
- Imports from Virtualmin, ISPConfig and CloudPanel, and a generic import of website files and database dumps for Enhance and any other panel. Virtualmin brings websites, databases with their password, the DNS zone and mailboxes; the others bring website files and databases.
- cPanel API: whole domains.
AddonDomain::addaddondomain,listaddondomains,deladdondomainandPark::park,listparkeddomains,unpark.
Fixed
- cPanel API:
DomainInfo::list_domainsnamed the wrong main domain on accounts whose first website is not the primary one. - Installer: the "Internet" check gave up after one attempt, so a name server that was slow for a moment ended the installation. It now tries three times.
Changed
- The installer test installs the panel the way customers do - the script piped into
bash, downloading the prebuilt archive - and checks image optimization on the installed server.
0.3.36 - 2026-11-18
Fixed
- The installer stopped at "Configuring hostname" on container-based servers. It replaced
/etc/hostsby renaming a new file over it, which fails where that file is a mount. It is now rewritten in place.
Changed
- Every release is now installed on a fresh Ubuntu 24.04 by the build pipeline, and once a week on the whole matrix: Ubuntu 22.04, 24.04 and 26.04, Debian 12 and 13, x86-64 and arm64, and a web-only install. The test logs in, creates an account with a website, a database and a mailbox, checks Nginx, PHP, MariaDB, BIND, Postfix and Dovecot for them, and runs the installer a second time over the installation.
0.3.35 - 2026-11-18
Added
- Mail health for customers (Email → Mail health, every account). Who refused the mail an account's own domains sent in the last 24 hours and why, the DNS problems of its mail domains and any of its domains on a blocklist. Only the account's own mail is shown; when the mail server itself is refused, the page says that the administrator has to fix it.
- One-click fixes on the health page (Monitoring → Health). "Issue certificates" runs AutoSSL for the websites without one, "Redirect to HTTPS" switches the redirect on for websites with a trusted certificate, "Publish records" adds the SPF, DKIM, DMARC or MX records mail domains are missing in the zones hosted here. Each asks first and says what it will change. New check: Mail DNS records.
- Update safety for App Store applications. Updates of the non-WordPress apps now check the website before and after and copy the files aside first. An update that breaks a working website, or stops half way and leaves it broken, is rolled back and reported to the owner and the administrators. Only files are restored, never the database.
- cPanel API compatibility for subdomains, FTP accounts and cron jobs:
SubDomain::addsubdomain,listsubdomains,delsubdomain;Ftp::list_ftp,add_ftp,passwd,delete_ftp;Cron::listcron,add_line,edit_line,remove_line.
0.3.34 - 2026-11-18
Fixed
- Post-import check: a file inside a backup folder that is listed itself was listed a second time, so the size of the leftovers was counted twice.
0.3.33 - 2026-11-18
Changed
- Migration → After the import can check every account, not only the ones with an import on record. Import records can be deleted and accounts arrive in other ways; what an old server left behind is the same either way. With no import on record the page opens on "All accounts".
0.3.32 - 2026-11-18
Added
- Blocklist monitoring for hosted domains (Email → Mail health). Every website domain and mail domain is checked each night against Spamhaus DBL, SURBL and URIBL. These lists hold domains: once a hacked website is on one, mail that merely mentions the domain is refused. A newly listed domain is an alert for the administrators and for the account that owns it, with the reason and where to ask for removal. Also a check on Monitoring → Health.
- Post-import check (Migration → After the import). For every imported account: does each website
answer on this server, does its DNS point here yet, does it have a certificate, is its mail DNS in
place, and - on Apache - does
.htaccessstill select the PHP of the old server. Runs by itself when an import completes and on demand. - Clean-up after an import. The same page lists what the old control panel left in the home directory, with sizes: its own data, error logs, configuration copies with a database password, account archives, database dumps and plugin backup folders. One click removes what is safe; archives and backups are listed and left to the owner.
- Mail health: Server name SPF. Mail that websites send through PHP and every bounce are checked against the server's own name. The panel adds the SPF record when it hosts that DNS zone and gives the record to add when it does not.
Fixed
- Blocklist checks reported every address as clean on some servers. Spamhaus refuses questions that reach it through a hosting provider's shared DNS resolver, and that answer was read as "not listed" - by the daily check and by Mail health. The panel now asks each list's own name servers, and a list that still does not answer is shown as a warning instead of a pass.
0.3.31 - 2026-11-17
Fixed
- A delayed message could turn into a bounce over IPv6. Postfix preferred IPv4 but fell back to
the server's IPv6 address after a temporary refusal (a full mailbox, a rate limit). IPv6 reverse DNS
is rarely set and the SPF records the panel publishes authorise the IPv4 address only, so Gmail
answered the retry with a permanent "550 5.7.25 no PTR record" and the message was returned to the
sender. On a server whose main address is IPv4, outgoing mail now leaves over IPv4 only. Mail is
still received over IPv6, and a value set by hand in
master.cfis kept. - Mail health: "the recipient is receiving mail too quickly" (Gmail, Yahoo) is its own cause instead of "Other", with the note that the provider slows down that one address, not the server.
0.3.30 - 2026-11-17
Added
- Server health page (Monitoring → Health). Everything
aio doctorchecks on the command line (services, ports, configuration tests, certificates, disk, reverse DNS, pending reboot), in the panel, together with what only the panel knows: websites without HTTPS, websites in an incident, malware and exposed files still in place, vulnerable WordPress components, backups, stuck tasks and whether alerts reach anyone. A service that is down has a Restart button; other problems link to the page that fixes them. Runs every night and on demand; a check that starts failing is an alert. - WordPress update safety. Every plugin, theme and core update now checks the website before and after. The folders about to change are copied aside first; when the website answers normally before the update and fails after it (server error, "There has been a critical error", a PHP fatal error, a database error, stuck maintenance mode), the previous version is put back automatically and the account owner and the administrators are told. A website that was already failing is not rolled back. Only files are restored, never the database.
- Pinned plugin and theme versions. A pinned plugin or theme is left alone by "Update all", "Update everything" and the automatic update of vulnerable components.
- Mail health page (Email → Mail health). Does mail from this server arrive? Server checks (reverse DNS including whether the name points back, the server name, Spamhaus ZEN, SpamCop, PSBL and Mailspike, outbound port 25, the mail certificate, IPv6 reverse DNS, the queue), the last 24 hours of refused mail grouped by receiving domain and cause with the receiving server's own words and what to do, and SPF, DKIM, DMARC and MX for every mail domain. A provider that starts refusing the server itself is an alert.
- cPanel API compatibility. Tools written for cPanel work against the panel with an AIO Panel API
token:
/execute/<Module>/<function>(UAPI) and/json-api/cpanel(API 2). Covers what ACME clients use for DNS validation (acme.shdns_cpanel, certbot-dns-cpanel, lego and therefore Traefik and Caddy),SSL::install_sslfor deploy hooks, and mailbox and MySQL provisioning. Token scopes, IP allowlists, package limits and the audit log apply as for the native API; account passwords are not accepted.
Changed
- Staging-certificate guard. Let's Encrypt test mode can no longer put an untrusted certificate on a live website by accident. Only a certificate an administrator requests by hand is a test certificate; renewals, AutoSSL, new and migrated websites, the Security Advisor, customer requests and the panel's own certificate always get trusted ones. Before, a renewal that ran while test mode was on replaced a trusted certificate with a test certificate. Test mode switches itself off after 24 hours, a test certificate never turns the HTTPS redirect on, AutoSSL replaces test certificates with trusted ones once test mode is off, and a website serving one fails the health check.
0.3.29 - 2026-11-17
Added
- Bot and AI crawler control (Websites → Security → Bots and crawlers). Per website: block AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Bytespider, CCBot and others), block SEO tool crawlers (AhrefsBot, SemrushBot, MJ12bot...), block custom user agents, and rate-limit crawlers to 30 requests a minute, 1 a second or 5 a second per crawler. Search engines, link previews and uptime monitors are never blocked or slowed. The card lists who crawled the website in the last seven days and how many requests were refused.
- WordPress vulnerability scanning works without an API key. The scanner used to need a Wordfence Intelligence key on every server, so most servers never scanned. Servers now download the vulnerability index from aiopanel.net once a day (a few minutes after the first start, then nightly) and scan right away. An own Wordfence key stays possible under WordPress → Vulnerability scanning. The data is Wordfence Intelligence, © Defiant Inc., redistributed with its copyright notice and licence.
Changed
- Site error watch also covers reverse proxy websites: a 502 or 504 from an application that is down opens an incident like any other server error.
0.3.28 - 2026-11-17
Fixed
- "Cannot read properties of undefined (reading 'startsWith')" on the Settings page (and on the DNS and webmail autodiscover endpoints) for a request whose connection closed while it was being answered, typically during a panel restart. Such a request has no client address; it is now treated as an unknown address instead of failing with an internal error.
0.3.27 - 2026-11-17
Added
- Site error watch. Every two minutes the panel counts server errors (5xx) and PHP fatal errors per website from the access log and the account's PHP error log. When the last 15 minutes cross the limits (20 failed requests that are at least 20% of all, or 10 fatal errors; both adjustable under Monitoring → Alerts) an incident opens: the administrators and the account owner get one alert with the failing addresses or the fatal message and another when the website has recovered, the website list shows a badge, and a new Errors card on the website's Overview tab shows the last 24 hours. It catches websites that fail behind a healthy home page, such as a shop whose checkout or REST API answers 500.
- Exposure scanner (Security Center → Exposure). Looks three folders deep into every website for site copies, database dumps, configuration copies, keys, logs and diagnostic scripts, and requests each one the way a visitor would; only files that are really served are listed. A finding can be blocked (a deny rule for that exact address, the file stays), marked as intended, or deleted. A scan of every website runs weekly and alerts the administrators about new high-risk files.
Fixed
- A toast could cover the Save button of a dialog and, while the pointer rested on it, never went away, so the next save did nothing. Toasts now appear at the top, below the header, in the panel and on aiopanel.net.
0.3.26 - 2026-11-17
Added
- Critical alerts are emailed to the administrators out of the box. Notifications only left the panel when someone had set up a channel under Monitoring; on a server without one, an account suspended for malware or a failing restore check stayed behind the bell icon for days. Errors addressed to the administrators are now emailed to every active administrator, through the SMTP relay from Settings or the server's own mail service. An alert a channel already delivered is not emailed again, the same alert is sent once an hour at most, and 20 emails an hour is the ceiling. The new Administrator email card on Monitoring → Channels lists the recipients, sends a test and switches the emails off.
- Dashboard reminder when alerts reach nobody: shown to administrators while the emails are off (or no administrator has a real address) and no channel is set up, and when the last alert email failed.
0.3.25 - 2026-11-17
Changed
- A malware finding no longer takes the whole account offline. Until now any file ClamAV flagged suspended the account, so one infected upload (a ticket attachment in private storage, say) put every website of that customer behind the suspension page until an administrator stepped in. Flagged files are now moved to quarantine automatically and the websites stay online; a false positive is restored from Security Center > Malware. Two switches under Settings > Policies control this: Quarantine malware automatically (on) and Suspend when malware is found (now off by default; servers where an administrator saved the policies keep their choice). The notification says what was actually done.
Fixed
- The panel and the website were wider than the screen on phones and tablets. 16 of the 33 panel pages (Dashboard, Monitoring, Websites, SSL, FTP, Web Disk, Visitor Stats, WordPress, Security, Services, Web Server, IP Addresses, Cluster, Settings and others) and the Download, Roadmap, FAQ and Modules pages of the website scrolled sideways, up to 1,021 px on a 375 px phone. Grid cells now shrink to the screen and their tables scroll inside the card, segmented filters scroll instead of overflowing, and hover tooltips no longer take up space while hidden.
- The weekly backup restore check always failed with "timed out". It waited for a task status that does not exist, so a successful test restore was reported as a failure after 30 minutes.
- A file marked as safe was reported again by the next scan and counted as a new infection.
- False "Unusual outbound traffic" alerts. Network throughput summed every interface, including loopback, Docker bridges and container interfaces, so a nightly database dump over 127.0.0.1 looked like data leaving the server and container traffic was counted up to three times. Only external interfaces are counted now (Dashboard, Monitoring, anomaly detection).
- Visitor statistics failed every night for a website that received very long URLs. GoAccess cannot read access-log lines over 4,096 bytes (a crawler caught in an encoding loop sends them), rejected the whole day, and the panel retried that day forever. Over-long lines are shortened when they are collected, and existing day files are repaired on the next run.
- "radicale reload exited 3" after every calendar or address book change: the Radicale unit has no reload action, so the panel now reloads when possible and restarts otherwise.
0.3.24 - 2026-11-13
Fixed
- Migrated WordPress sites were not monitored. Sites that arrived through a migration (cPanel, Plesk, DirectAdmin, HestiaCP, CyberPanel, aaPanel) or over SFTP were only tracked after someone clicked Scan on the WordPress page, so they got no update checks and no vulnerability alerts. The importer now registers them at the end of every migration, and after this update the panel searches every account once in a background task ("Finding WordPress sites").
0.3.23 - 2026-11-13
Security
- Backups, database dumps, logs and configuration copies were downloadable from websites. Nginx never
reads the
.htaccessdeny rules that backup plugins rely on, so files such aswp-content/updraft/backup_..._db.gz,dump.sql,error_logandwp-config.php.pre-migrationwere served to anyone who guessed the name. Every website (except reverse proxies) now includessnippets/aiopanel-sensitive.conf, which refuses backup plugin folders (UpdraftPlus, All-in-One WP Migration, Duplicator, WPvivid, BackWPup and others),*.sql/*.sql.gz/*.sqlite,*.loganderror_log, and copies such as*.php.bak,*.php~and*.php.orig. A new Block sensitive files switch in Websites > Settings turns it off for a website that must publish such files. Existing websites are regenerated once after the update (a background task).
Fixed
- Services that start from
/etc/init.dscripts showed as disabled (Pure-FTPd on Ubuntu, for example): systemd reports their unit file state as "generated" whether or not they start at boot. The Services page now askssystemctl is-enabled, which consultssystemd-sysv-install.
0.3.22 - 2026-11-13
Fixed
- Tasks that started while the live connection was down never appeared (and their progress bars stayed empty until a reload). The panel now also refreshes the task list every 10 seconds while the page is visible and adopts running tasks and tasks created in the last two minutes, so their progress and result show up even when no live event reached the page. Verified with the live connection switched off.
0.3.21 - 2026-11-13
Fixed
- Progress bars froze until the page was reloaded (panel updates, installs and other background tasks). Progress only arrived as live WebSocket events, and events sent while the connection was down were lost; during a panel update the connection always drops because the panel restarts. The panel now re-reads running tasks as soon as it reconnects and checks any running task that has been silent for a few seconds, so progress, logs and the final result appear without a reload.
- The Dovecot 2.4 fix from 0.3.20 was undone by the update itself: the updater re-renders
99-aiopanel.conffrom the installer template, which lacked the new include line. Both templates now include/etc/dovecot/aio-compat.conf.
0.3.20 - 2026-11-13
Fixed
- Mail delivery on Ubuntu 26.04 (Dovecot 2.4). The distribution's
20-lmtp.confstrips the domain from the address before looking up the mailbox (%{user | username | lower}), so every delivery to a mailbox would fail with "User doesn't exist". The panel now writes/etc/dovecot/aio-compat.confat start, which keeps the full address for LMTP and also closes the obsolete ManageSieve listener on 0.0.0.0:2000 that the same package opens (mail clients use 4190). Validated withdoveconf -nand rolled back if rejected. - OpenLiteSpeed setup failed with "also listens on 0.0.0.0:7080, 0.0.0.0:8088". The package starts an
instance with
lswsctrloutside systemd, whichsystemctl stopdoes not reach and which kept the stock public listeners. The setup (Services → Install / Finish setup) and the installer now stop it as well.
0.3.19 - 2026-11-13
Fixed
- OpenLiteSpeed websites answered 403 Forbidden. Its workers ran as
nobody, which cannot open website folders (owner plus thewww-datagroup only). OpenLiteSpeed now runs aswww-datalike the other web servers; servers set up on 0.3.16 to 0.3.18 are corrected the next time a website changes. Verified on a live server: PHP runs through LSAPI as the site owner and.htaccessrewrites work. - Website lists, the website header and the app installer showed "Nginx" for OpenLiteSpeed sites.
Added
- Migration → Review offers OpenLiteSpeed as the web server for imported websites when it is installed.
0.3.18 - 2026-11-13
Fixed
- Creating a website on OpenLiteSpeed failed with "Internal server error". Panels installed before 0.3.10 kept a database rule that only allowed the Nginx, Apache, proxy and static stacks. Migration 1002 widens it; because SQLite cannot change such a rule in place, the websites table is rebuilt with foreign keys held off, every row, index and the ID counter carried over, and the update rolls back if any reference would break. The update keeps its usual database backup.
0.3.17 - 2026-11-13
Fixed
- Services: enable, disable and install for services known by an alias. OpenLiteSpeed's
lsws.serviceis a link tolshttpd.service, and systemd refuses to enable or disable a unit by its alias, so the last step of the OpenLiteSpeed install and the Enable/Disable buttons failed. The panel now resolves the real unit first.
0.3.16 - 2026-11-13
Fixed
- Services: Finish OpenLiteSpeed setup. When an earlier OpenLiteSpeed install failed after apt had installed the packages, the Install button disappeared and websites still could not use OpenLiteSpeed. The card now offers Finish setup, which writes the panel configuration, restarts the service with it and switches OpenLiteSpeed on for websites.
0.3.15 - 2026-11-13
Fixed
- OpenLiteSpeed install stopped at "Command failed (exit 1): openlitespeed -t". The exit code of
openlitespeed -tsays nothing about the configuration (a stock install exits 1, a file with unbalanced braces exits 0), so the panel, the installer and every website reload now read its output for real errors instead, and the install checks that the service actually listens on its port. - OpenLiteSpeed WebAdmin listened on all addresses. Its configuration was written to
conf/admin_config.conf, but WebAdmin readsadmin/conf/admin_config.conf, so the stock listener on*:7080stayed (the panel firewall keeps port 7080 closed by default). The config now goes where OpenLiteSpeed reads it, the service is stopped and started instead of gracefully restarted (which kept the stock public listener on port 8088 open), and the install fails if any OpenLiteSpeed listener is not on the loopback address. - The OpenLiteSpeed template no longer sets
adminRoot, which OpenLiteSpeed 1.9 rejects.
0.3.14 - 2026-11-13
Fixed
- OpenLiteSpeed install (Services → Install and the installer's
--openlitespeed) asked for lsphp modules LiteSpeed does not publish for every PHP version, such aslsphp85-opcache(opcache is built into lsphp 8.5), and apt stopped with "Unable to locate package". Only packages the repository publishes are installed now, and the task log names the ones skipped. OpenLiteSpeed is restarted after the panel writes its configuration, so it never keeps running with the package's stock settings.
0.3.13 - 2026-11-13
Fixed
- Services → Install OpenLiteSpeed stopped with "Could not download the LiteSpeed signing key":
LiteSpeed publishes its repository key as a binary keyring, which the 0.3.12 install only accepted in
ASCII-armored form. Both formats are now recognised and stored the way apt expects (
.gpgor.asc).
0.3.12 - 2026-11-13
Fixed
- Services → Install OpenLiteSpeed failed with "Unable to locate package openlitespeed": the
package is not in the Ubuntu or Debian archive. The install now adds LiteSpeed's signed repository
for the server's release, installs an
lsphpbuild for every PHP version on the server (where LiteSpeed publishes one), writes the panel's OpenLiteSpeed configuration, checks it withopenlitespeed -tand switches the feature on, so websites can use the OpenLiteSpeed stack without reinstalling the panel.
Changed
- aiopanel.net blog: posts with an FAQ section publish FAQPage structured data, articles carry word count, reading time and language, and cover images have alt text and dimensions.
0.3.11 - 2026-11-13
Changed
- Panel: HTTP/2 and precompressed assets. The panel now listens with HTTP/2 (one multiplexed
connection per tab instead of six HTTP/1.1 ones; HTTP/1.1 stays available for WebSockets and old
clients,
AIO_HTTP2=0turns HTTP/2 off) and serves its JavaScript and CSS brotli- or gzip-precompressed (tools/build/precompress.mjsruns at build time): the main script goes from 715 KB to 184 KB on the wire. The theme script is inlined (allowed by a CSP hash, no extra blocking request) and the two UI fonts are preloaded. - aiopanel.net: per-page bundles. Each public page is its own chunk, loaded ahead of hydration and on demand when navigating, so a first visit downloads 190 KB of script instead of 309 KB; markdown and chart code only come with the pages that use them. Fonts are preloaded, the theme script is inlined and assets are served precompressed.
0.3.10 - 2026-11-13
Added
- Plesk and DirectAdmin imports. Migration → Other control panels takes a whole-subscription Plesk
backup (Backup Manager, Obsidian or Onyx) or a DirectAdmin user backup (
user.<creator>.<user>.tar.gz) and imports domains, subdomains and aliases with their files, databases with their users and passwords, mailboxes with messages, forwarders and catch-all, DNS zones and cron jobs through the same analyze → review → import flow as cPanel. Pasting a listing is still offered when no backup file is at hand. - Object storage. Install with
--object-storageand every hosting account gets S3-compatible buckets (<account>-<name>, optional quota, optional public downloads) and access keys scoped to its own buckets, under Object Storage. The MinIO server runs on the panel machine with the panel certificate on port 9000; any S3 client (AWS CLI, rclone, WordPress offload plugins, Laravel) works with path-style addressing. Usage is refreshed every ten minutes; suspending an account disables its keys, deleting it removes buckets and keys. - OpenLiteSpeed as a website backend. Install with
--openlitespeedand pick OpenLiteSpeed (via Nginx) as a website's stack: Nginx keeps TLS, HTTP/3, the page cache and static files and proxies the rest to OpenLiteSpeed on 127.0.0.1:8088, which runs PHP through LSAPI (lsphpbuilds per version) as the account's user, honours.htaccessand works with LiteSpeed Cache plugins. Per-sitevhconf.conffiles and the listener map are generated and validated like the Nginx and Apache configs; OpenLiteSpeed appears under Services and Logs. - Public demo.
AIO_DEMO_PUBLIC=1runs the demo image as a sandbox for anonymous visitors (demo.aiopanel.net): the password, e-mail, two-factor settings, passkeys and sessions of every seeded user, administrator accounts, every write under Settings, System, Services, PHP, web server, IPs, cluster, DNS secondaries and license, every delete of seeded data and suspending seeded accounts answer403 demo_public, uploads are capped at 5 MB and the shell shows a banner with the credentials and the reset every 30 minutes.tools/demo/holds the hardened Compose file (read-only root, tmpfs data, no capabilities, no egress), the reset timer and the nginx pieces. - Settings → About links to the public roadmap and to "Suggest a feature" on aiopanel.net.
- Settings → License shows how long the license itself lasts ("Lifetime" for licenses without an end) next to the token check-in window, which used to be the only date shown. Needs a license server that sends the new validUntil field (aiopanel.net does since 2026-11-12); older tokens show the old row.
- aiopanel.net: Modules page.
/modulesoffers the WHMCS and Blesta modules as zip downloads with install steps, linked from the Download page and the footer; the zips are built from the repository'sintegrations/folder on request (/modules/whmcs.zip,/modules/blesta.zip). - aiopanel.net: redeem codes. Admin → Redeem codes generates prepaid license codes (plan, 1 month to 5 years or lifetime, server count, batches of up to 500 with CSV export). Customers redeem them under Account → Licenses: a new license, or more time on the one they already have for that plan. Staff can also redeem a code for a customer by e-mail; unused codes can be revoked.
- aiopanel.net: comparison pages with a cost calculator (cPanel, Plesk, DirectAdmin, CyberPanel, HestiaCP, CloudPanel, aaPanel, Virtualmin), public roadmap with voting, ideas board, blog with RSS and newsletter, FAQ, security, partners, migrate-from-cPanel and demo pages, the site in 12 languages with request-time rendering, customer pages for servers (seat transfer), notifications (e-mail + Telegram) and API keys, and staff pages for idea triage, roadmap, blog, campaigns, fleet, churn, affiliates, incidents, the comparison matrix and site content.
0.3.9 - 2026-11-11
Added
- cPanel import: the "default address" (catch-all) is recreated. On cPanel the catch-all of a domain usually points at the account itself, so mail for unknown addresses went to the account's system mailbox; the importer used to skip it with "is not a valid email address", and such mail bounced after the DNS cutover. It now creates one mailbox named after the new account at the main domain, makes it the catch-all of every such domain, copies the old system mailbox (homedir/mail) into it and reindexes it. The mailbox gets a random password (set one under Email); the analysis and the report say so. Catch-alls that pointed at an address are imported as before.
- ionCube Loader. Server → PHP → Extensions lists the ionCube Loader as installable for each PHP version: the panel downloads ionCube's loaders, enables the one for the version before OPcache and validates PHP-FPM like any extension. The installer sets it up for every PHP version it installs.
Changed
- PHP versions come with the extensions a cPanel server ships. apcu, bz2, gmp, imap, ldap, memcached and tidy are installed with every PHP version (installer and Server → PHP) when the repository provides them.
- New installs default to Apache mode when Apache is installed, so websites and cPanel imports
keep their
.htaccessfiles working; the default remains adjustable under Settings → Server, and existing servers keep their setting.
0.3.8 - 2026-11-10
Changed
- Wildcard certificates while the zone is still served elsewhere. When
_acme-challenge.<domain>is delegated to this server with an NS record (the usual arrangement during a migration), the DNS-01 check now polls the delegated nameservers instead of waiting two minutes on the zone's own.
0.3.7 - 2026-11-10
Fixed
- WordPress object cache: cached objects came back broken. The drop-in unserialized cache entries with every class forbidden, so WP_Post, WP_Term, WP_User and option objects returned as incomplete objects and WordPress died with "The script tried to modify a property on an incomplete object". Entries are unserialized normally now (Redis is local). Switch the object cache off and on again on affected sites to get the new file.
0.3.6 - 2026-11-10
Fixed
- WordPress object cache broke every page. The panel's object-cache drop-in defined only wp_cache_init() and wp_cache_supports(); WordPress then skipped its own cache.php and every page died with "Call to undefined function wp_cache_get()". The drop-in now provides the whole wp_cache_* API. Sites with the object cache switched on are repaired by switching it off and on again (or by re-saving it); new activations get the complete file.
- cPanel migration: folders archived through a symbolic link. cPanel backs up both a symlinked folder (public_html/app -> /home/user/app/public) and the files behind it; tar then fails on those members ("Cannot open: Not a directory") and the whole analysis stopped. Those members are now skipped with a note - their files are restored from the link target - and only other errors stop the import.
0.3.5 - 2026-11-10
Added
- cPanel migration: certificates come along. With "SSL certificates" selected, the certificate cPanel served for each website (key, leaf and chain from the backup) is installed when it is still valid for two weeks and covers the name, so HTTPS keeps working the moment DNS moves; the others are re-issued as before.
0.3.4 - 2026-11-10
Fixed
- cPanel migration: apps deployed into public_html. Laravel-style sites whose .htaccess forwards every request into public/ are now served from public/ directly (nginx does not read .htaccess); the review and the report say so. Before, such sites answered 403 or exposed the project root.
- cPanel migration: database users. The implicit cPanel user named like the account keeps its
password and grants (it is created as
account_accounthere, and the report lists the rename).
0.3.3 - 2026-11-10
Fixed
- nginx rejected every new website after 0.3.0. The page cache's
fastcgi_cache_keynamed the per-site$aio_cache_genvariable at http level, which nginx only accepts once some server block defines it, songinx -tfailed with "unknown aio_cache_gen variable" on servers where no website had the page cache on: creating or importing a website was rolled back ("Web server rejected the configuration") and a restart would not have brought nginx back. The variable is now declared with amapdefault in the generated http configuration. Update as soon as possible.
0.3.2 - 2026-11-10
Added
- Wildcard subdomains. A website can answer for
*.example.com(Websites > Domains > Wildcard subdomains): the virtual host gets the wildcard name, the zone a*address record, and the certificate is re-issued as a wildcard through DNS-01 when the zone is hosted on the server. Subdomains created as websites of their own keep their own configuration. - Catch-all website. Administrators can make one website answer for every hostname that reaches the server without a website of its own - for apps whose customers point their own domains at the server. Bare IP addresses keep the server's default page.
- cPanel migration: wildcard subdomains.
*.example.comentries of a cPanel account are recreated as wildcard websites instead of being dropped; the review shows them, and a different cPanel document root is reported as a warning.
Fixed
- cPanel migration: cron commands.
/usr/local/bin/phpandphp-clipaths of cPanel cron jobs are rewritten to the panel's PHP; WP-CLI calls keep working because the panel installs it at the same path.
0.3.1 - 2026-11-10
Fixed
- Migration from cPanel with a password failed on servers without sshpass. The panel now installs sshpass on demand, and the installer ships it from the start.
0.3.0 - 2026-11-10
Added
- Passkeys. Sign in to the panel (and to aiopanel.net) with a fingerprint, face, device PIN or hardware security key instead of a password. Register them under Profile > Security; Settings > Security can require passkeys for administrators once they have one, and the security advisor lists administrators without one.
- WordPress vulnerability scanning. Every WordPress refresh matches installed plugins, themes and core against the Wordfence Intelligence feed (free API key). Findings lower the health score, feed the security advisor and notifications, and can be fixed from the new Vulnerabilities tab; optionally patched releases are installed and plugins without a fix deactivated automatically.
- Immutable backup vault. S3 destinations can lock every archive with Object Lock (compliance or governance) for a chosen number of days. Locked archives cannot be deleted from the panel, by retention or with stolen keys; the destination test verifies that Object Lock is on.
- Warm-standby failover. Servers > Failover replicates every account to a standby panel on a schedule; the standby watches the primary, alerts after a configurable outage and can promote the replicas automatically, repointing A records (and Cloudflare zones) to itself. Manual promotion with a dry run, failover log, promotion reset.
- Anomaly detection. Monitoring > Anomalies compares CPU, memory, load, outgoing mail and traffic with the same hour of day over the past weeks and alerts on real outliers for an account or the server, without thresholds to tune.
- Full-page cache for every site. PHP, Apache-backed and reverse-proxied websites get a page cache with per-site TTL, query-string handling, stale-while-revalidate, path and cookie exclusions, a per-site purge and a 24-hour hit-ratio chart (Websites > Optimize).
- Cloudflare integration. Store Cloudflare API tokens, link DNS zones to Cloudflare, keep records in sync with the proxy on for web hosts and off for mail, purge the Cloudflare cache, set the SSL mode and issue Origin CA certificates in one click (DNS zone > Cloudflare).
- Free trials on aiopanel.net. Pro and Business can be tried for 14 days on one server without payment details; reminders before the end, conversion on the same license key, automatic fall-back to the free plan otherwise. Panels show a Trial badge.
- Referral and reseller programs on aiopanel.net. Every customer has a referral link; referred customers get a discount on their first invoice and referrers earn credit that pays their next invoices. Administrators grant reseller discounts on top of the volume tiers; customers apply from their account.
- Open panel from aiopanel.net. The license owner can sign in to any activated server from Licenses & servers with a signed one-minute link. Off by default on the panel; a local administrator enables it under Settings > Security, where two-factor on aiopanel.net is required when the mapped administrator uses two-factor.
Fixed
- Site: JSON settings were stored double-encoded on PostgreSQL. The postgres client serialized jsonb parameters a second time, so the "last announced release" marker never matched and the release e-mail went out again every hour; 2FA recovery codes, audit details and webhook payloads were affected the same way. The driver now passes JSON through once and migration 8 repairs the stored rows.
0.2.6 - 2026-11-10
Security
- Licensing hardening. The server identity now combines the machine id, install id, primary MAC address and root file system UUID (upgraded panels keep their seat automatically). Every license call carries a build attestation: the panel hashes its compiled code and the license server compares it with the hash published for that version, refusing modified builds (switchable to flag-only). The license server records every activation, refresh, release and refusal, flags keys whose seats rotate between servers, whose server reports many IP addresses or hostnames, or that come from modified or re-keyed builds, and e-mails staff; Admin > Licenses shows flags and history. Online tokens for subscriptions now live 5 days (monthly) or 10 days (yearly).
0.2.5 - 2026-11-09
Added
- What's new after an update. The admin dashboard shows the release notes of the version the panel runs, once per admin, with a link to the full changelog under Settings > Updates.
- Six more languages: Turkish, Russian, Arabic (right-to-left), Indonesian, Vietnamese and Simplified Chinese, for the sign-in screen, shell, dashboard and profile; module pages follow.
- arm64 release archives.
tools/release/publish.sh --arch arm64cross-builds the archive on an x64 server (prebuilt better-sqlite3 for the target, verified by its ELF header), so every release shipslinux-x64andlinux-arm64; the installer andaio updatealready pick the right one. - WHMCS and Blesta modules (
integrations/, downloadable from the panel) with the billing API calls they need: change password, change package, usage, account list and single sign-on links (POST /api/billing/accounts/:username/login, valid once for 60 seconds). - Account usage reports. Accounts > (account) > Usage charts disk, bandwidth, CPU and memory per day from nightly snapshots and lists monthly transfer by source, with CSV export; the same numbers feed the billing API.
- Staging for any website. Websites > Staging creates
staging.<domain>with a copy of the files and, optionally, of the site's databases; push files and databases back to live after an automatic backup. WordPress sites keep their own staging tool, which also rewrites URLs. - Summary e-mails. Settings > Email > Summary e-mails sends administrators a daily or weekly overview of the server (accounts, sites, disk, backups, sign-ins, infected files, monitors, updates) and, optionally, every account owner a summary of their own account. Opt-out under Profile.
- Sign-in history for everyone. Profile > Sessions lists the login's own sign-in attempts with browser and IP address; failed attempts included.
- Activity log retention is now a setting (30 days to 5 years) next to the CSV/JSON export.
- Quarantine housekeeping. Security > Malware shows what sits in quarantine, deletes files automatically after a configurable number of days, empties the quarantine in one click and quarantines every detected file at once.
- aiopanel.net: discount codes (percent or fixed, once or every renewal, per plan, with limits and expiry), automatic volume licensing for resellers (10% off from 5 servers, 20% from 10, 30% from 25), a public status page fed by the panel's own monitoring, and release announcement e-mails with one-click unsubscribe.
0.2.4 - 2026-11-09
Verified with a clean one-line install (curl … install.sh | sudo bash) on a fresh Vultr Ubuntu 24.04
server: 4 minutes 40 seconds, 60 health checks passed.
Added
- The installer gets the panel a trusted Let's Encrypt certificate on its own when the hostname already points at the server, and its "Next steps" skip what is already done.
Fixed
- Outgoing mail prefers IPv4. Gmail and others refuse IPv6 senders without a reverse DNS record (5.7.25); Postfix now delivers over IPv4 first, on new installs and existing servers.
- Table empty states ("No invoices yet") rendered as bare text at the edge of the card.
- The installer reported itself as 0.2.0 regardless of the release;
tools/release/publish.shnow refuses to publish whenAIO_INSTALLER_VERSIONand the release differ. - Roundcube's expected first-run error no longer prints
[FAILED]into the installer output.
0.2.3 - 2026-11-07
Found by exercising every module on a real Ubuntu 24.04 server.
Fixed
- Calendars and contacts (CalDAV / CardDAV) refused every client with 403. Radicale trusts the
X-Remote-Userheader, but nginx never authenticated anyone. The panel now writes an nginx snippet that checks the mailbox password throughauth_request(/api/dav/public/auth) and forwards the address; the password itself never reaches Radicale. Existing servers get the snippet at the next start. - Mailing lists bounced or discarded every post. The panel created three of mlmmj's fourteen
directories, and the Postfix pipe lacked the
Rflag that gives mlmmj the envelope sender. New lists get the full layout and message templates, and the panel repairs existing lists and the pipe entry at start. - WordPress installs were missing and truncating files.
wp core downloadextracts with PHP's PharData, which cuts file names longer than 100 characters (WordPress 7 has them underwp-includes/php-ai-client). The installer now fetches the official zip for the chosen language, verifies its MD5 and extracts it with unzip;wp core verify-checksumspasses. - Uninstalling an app left its database user behind. The user the installer created is removed unless something else still grants it.
- Wildcard certificates failed with "redundant with a wildcard domain" when an alias such as
license.example.comwas also requested: names a wildcard covers are now left out. - Calendar and address book names with spaces were rejected ("Team Calendar"); the name is now
turned into the path segment Radicale needs (
team-calendar). - Deleting a DNSSEC-signed zone left BIND's
.jbkjournal backup behind.
Added
aio ssl:panelsecures the panel hostname with Let's Encrypt from the command line (the same as SSL / TLS > Panel certificate).
0.2.2 - 2026-11-07
Fixed
- Services, PHP, Web Server and Cluster pages stuck on the loading screen on servers whose timezone abbreviation JavaScript cannot parse (CET, IST, JST and most others outside the US): service start times are now read from systemd's monotonic clock, which has no timezone.
0.2.1 - 2026-11-07
Added
- Migration from HestiaCP, CyberPanel and aaPanel — upload a backup from any of the three panels and import its domains and websites, databases, mail domains, mailboxes and forwarders, DNS zones and cron jobs, with the same analyze, review and import steps as the Plesk and DirectAdmin imports. Anything a backup format cannot carry is listed as a warning in the analysis.
0.2.0 - 2026-11-07
Added
-
Licensing — AIO Panel is licensed per server. Servers start on the free plan (up to 5 hosting accounts); a license key raises the limit and unlocks resellers, multi-server and DNS cluster, migration and transfers, and the billing API. Activate it under Settings, License, with
aio license:activateor with the installer's--license-key. Licenses are signed tokens renewed a few times a day; offline licenses are supported. A lapsed license never stops hosted accounts. -
Operating systems — the installer, updater and
aio doctorsupport Debian 12 and 13 and Ubuntu 26.04 LTS, alongside Ubuntu 22.04 and 24.04. Debian and Ubuntu 26.04 get PHP from packages.sury.org. Dovecot 2.4 (Debian 13, Ubuntu 26.04) uses its own configuration templates. -
Web server — server-wide HTTP/3 (QUIC) and Brotli, enabled only when the installed Nginx supports them. Turning HTTP/3 on opens UDP 443 and rolls the configuration back if
nginx -tfails. -
Email — an outgoing relay (smarthost) with provider presets, per-domain routes and a port-25 check, and spam training from the Junk folder through Dovecot IMAPSieve into Rspamd.
-
Visitor statistics — per-site visitors, pages, referrers and status codes from the access logs (GoAccess), with optional GeoIP countries and a sandboxed HTML report.
-
API tokens — full, read-only or per-module scopes, an IP allowlist, last-used IP and expiry. Password, two-factor and impersonation actions require a browser session.
-
Languages — English, Spanish, German, French, Portuguese (Brazil) and Hindi for the shell, sign-in, dashboard and profile, with
npm run i18n:checkfor translators. -
Documentation site — guides and screenshots under
website/, published to docs.aiopanel.net.
Changed
- Node.js 22.12 or newer is required. The installer upgrades older 22.x releases.
- AIO Panel is now proprietary software under an end user license agreement (previously MIT).
- The installer and
aio updateinstall prebuilt releases from aiopanel.net/releases by default, and the update check reads from there too. Building from source needs--sourceor--branch. - Release archives no longer include source maps, and include THIRD_PARTY_NOTICES.md.
0.1.0 - 2026-10-19
First preview.
Added
- Panel core — Fastify 5 API with one plugin per module under
/api/<module>, SQLite database with per-module migrations, sessions and personal API tokens (Authorization: Bearer aio_...), two-factor authentication, IP allowlist, audit log, background tasks with live progress, notifications and a realtime WebSocket gateway. - Web UI — React 19 single-page app with dark and light themes, command palette, tasks tray and a complete design system.
- Demo mode — runs on any OS with simulated system changes and seeded demo data
(
npm install && npm run dev, loginadmin/demo1234), plus a Docker demo image. - Hosting — accounts, packages with limits, resellers, suspension and "log in as"; websites with Nginx, Apache, reverse proxy and static modes, multiple PHP versions, redirects, aliases and password-protected folders; configuration validated and rolled back automatically on errors.
- Modules — DNS, email, databases, file manager, FTP, SSL, backups, cron, app installer, WordPress toolkit, Node.js/Python apps, Git deploy, Docker, security center, monitoring, multi-server, migration, terminal and AI assistant (several modules are marked beta).
- Installer (
installer/install.sh) — one-command installation on Ubuntu 22.04/24.04 (x86_64, arm64): Nginx, optional Apache backend, PHP-FPM (ondrej/php), MariaDB, Redis, optional PostgreSQL, Postfix + Dovecot + Rspamd with DKIM maps, BIND9, Pure-FTPd, UFW, Fail2ban (including an AIO Panel jail), ClamAV, WP-CLI, Composer, rclone, optional Docker, phpMyAdmin with single sign-on and Roundcube; self-signed panel certificate, systemd service, health check and credentials summary. - Operations —
aiocommand line (status,logs,doctor,update,apply-certs...),update.shwith database backup and automatic rollback,uninstall.shthat keeps hosted data unless--purgeis given. - Project — CI (typecheck, build, demo smoke test, ShellCheck), release workflow producing
prebuilt
linux-x64andlinux-arm64archives, documentation and contribution guidelines.