AdminBolt 1.9.3 connects your servers to Acronis Cyber Protect Cloud. Administrators recover accounts and whole servers from it. Resellers and clients can recover their own data when you allow it. Hosting accounts' mail can run on remote mail servers. A hosting account backup file from a cPanel server can be imported into a new or an existing account. Malware protection gets its own page in Health > Security, with real-time scanning for ImunifyAV and one malware history for every engine. Mailbox and webmail logins get login protection. White-label branding now covers the look of the admin, reseller and client panels, from colour schemes and the font to the favicon, the login page and the footer. The panels also have a new design and new security settings. The release also brings secondary DNS checks, free certificate replacement, failing backup alerts and a Reboot server action. The addon domain count no longer includes the main domain, so review your plan limits after the upgrade. Node.js and Ruby applications run on LiteSpeed Enterprise in Apache drop-in mode. On CloudLinux, Python applications run there too. Fixes cover PHP, CloudLinux, migrations and the client panel.
Acronis Cyber Protect Cloud
- Acronis Cyber Protect Cloud (AB-2019): Backups > Acronis connects the server to your Acronis Cyber Protect Cloud account. Install the Acronis Backup module in Modules first. You also need an API client from the Acronis console. In Settings you enter the API client, verify the connection, check the server and enroll it. Create the default plan then sets up a daily protection plan that keeps databases consistent. A plan you already have can be applied instead. You set its time and retention. Encryption is chosen when the plan is created. Run a backup now shows the backup's progress. Administrators recover account files, databases, mailboxes, domains or a whole account. They can also recreate a terminated account, download an account, recover or download server files and revert the whole server to a recovery point. Self-service in Settings lets resellers restore the accounts they own and clients restore their own files, databases and mailboxes. Restoring a whole account for clients is a separate option, off by default. Clients also need the Acronis Backup feature in their hosting plan. The hosting plan and the reseller each set how many days back they can go. The Operations Log lists every recovery, download and backup. Notifications report a failed or stale backup, an offline agent and storage that is almost full. The Updates tab updates the Acronis agent and the panel's Acronis package. The admin REST API offers the same under
/api/admin/acronis and the client API under /api/client/acronis.
Remote mail servers
- Remote mail servers (AB-70): Email Servers lets hosting accounts' mail run on a separate server. Add Email Server adds a server and Deploy sets it up as a dedicated mail server. That server needs AlmaLinux 9. On a hub, Use Fleet Node turns a paired node into a mail server for this panel's accounts. Each mail server shows its status. View Logs shows its recent mail log. Administrators pick an account's Mail Server when they create the account or in Edit Account. Accounts set to Default Mail Server follow the server chosen with Set as Default. Existing accounts stay on the local mail server. When an account's mail server changes, its MX records that point at this panel's servers move to the new server. So do its mail SRV,
mail.<domain> and DKIM records and its mail autodiscovery. External MX records and records you added by hand stay as they are. While a domain uses MailChannels, SpamExperts or Remote email routing, its MX and mail.<domain> records stay as they are too. Existing mailboxes are not moved to the new server. A mail server that accounts still use cannot be deleted. A node that accounts use as their mail server cannot lose its mail role or be unpaired. Webmail on a hub signs in to mailboxes hosted on mail servers.
Backup file import and migration
- Backup file import (AB-1959): A hosting account backup file from a cPanel server can be imported into a new or an existing account, without access to the old server. Administrators start it with Import a backup file on the Migration page. Resellers use Import a backup under Hosting Management. Clients use Files > Import a backup. Imports start once Allow backup imports is turned on in Import settings. Clients also need the Backup import feature in their hosting plan. Both are off until you turn them on. An interrupted upload resumes where it stopped. Before anything is written, a preview lists the domains, databases, mailboxes, DNS zones, cron jobs, certificates and FTP accounts in the file. It checks them against the plan limits and shows the planned action for each. An import into an existing account keeps its data unless you choose otherwise. Replaced data is kept in a protection copy. The report gives the result of each item. Try again prepares a new preview for what was not restored. The admin, reseller and client REST APIs offer the same.
- Migrated accounts with failed setup (AB-1910): A migration run ends as completed with warnings when some of an account's services could not be set up. The run page lists each such account with its failed steps. The DNS cutover leaves out accounts whose system user, website or DNS zone could not be set up, unless you tick them. You tick them on the run page or through
POST /api/external-migrations/runs/{run}/gates/dns-cutover. The Activity panel replaces raw runner output with a plain message and a log reference.
- Node migration pre-check (AB-1997): For accounts with MariaDB databases, the node migration pre-check fails when MariaDB is installed but not running on the target. It tells you to start MariaDB before you retry. The hub and the target both need 1.9.3 for this check.
- Remote PostgreSQL access in migrations (AB-1831): An account moved between AdminBolt nodes keeps its remote PostgreSQL access rules when the target runs 1.9.3. A rule that cannot be set up there is named in the migration result with the reason and the next step. The migration then ends as completed with warnings.
White-label branding
- White-label branding (AB-2081, AB-2122, AB-2124, AB-2125): Branding in General Settings puts the admin, reseller and client panels under your brand. Pick one of the ready-made colour schemes or set your own colours, each with a light and a dark palette. A preview shows your colours as you adjust them. You also choose the corner style and the font for all three panels. The sidebar width is set for each panel on its own. Your logo fits without cropping. Branding also sets the favicon in the browser tab, a message above the login form, the footer text and the theme users start in. The Support tab adds your support URL, email, phone and Terms and Privacy links to the client login page and the client panel footer.
Malware protection and login security
- Malware protection (AB-1766, AB-2014): Health > Security shows which malware protection engine guards the server, whether it runs, its licence and whether uploads are scanned in real time. It compares ImunifyAV, Imunify360 and cPGuard side by side. Installing, removing or switching engines is a guided flow that runs one operation at a time. The admin REST API offers the same under
/api/admin/security. The CPGuard page shows the installed cPGuard version and whether an update is available. Update CPGuard installs it in the background and reports the result. A failed update shows the next step.
- Real-time scanning and malware history (AB-1764): With ImunifyAV, files written to a website are scanned in real time. Installing ImunifyAV sets this up. The upgrade sets it up where ImunifyAV is already installed. It follows domains and accounts as they are created, renamed, moved to another web server or removed. Health > Security shows whether real-time scanning is active and how many websites it watches. Where it is missing, Set up bolt-livescan adds it. Health > Malware lists every file a malware engine reports, once per account. Clients see their own files on Security > Malware. A file can be moved to quarantine, restored or deleted, one at a time or in bulk, whichever engine found it. The client page is a hosting plan feature, turned on for existing plans by the upgrade. Deleting a hosting account removes its quarantined files.
- Security Scan page removed (AB-1683): The Security Scan settings page is gone and its old address no longer opens. Malware protection is managed on Health > Security.
- cPGuard for clients (AB-1766): When the cPGuard client plugin is on, clients open cPGuard under Security > CPGuard. They see only their own account's data and can restore files from quarantine. Hosting accounts have a Contact email and the client panel has a notifications bell. A threat found in an account reaches the client in that bell. An email goes to the account's Contact email when one is set. Later detections arrive together in one digest. An account that cPGuard suspends is suspended in the panel.
- cPGuard scanning (AB-1765): cPGuard scans every site, also after a domain rename. A cPGuard install that cannot finish its set-up is reported as failed, for example when the licence key is missing or rejected.
- Mail login protection (AB-1951, AB-2011, AB-2066): Repeated failed mailbox logins and repeated failed webmail logins get the address blocked. This protection is added on upgrade and when Roundcube is installed. Your existing login protection settings stay as they are. The upgrade also updates Roundcube. Until Roundcube has the version webmail login protection needs, the Jails page asks for the update. The Jails page shows the reason when webmail login protection needs attention. Addresses you exempt are not blocked.
- cPGuard login protection (AB-1651, AB-1765): When cPGuard's login protection is on, it also covers panel, webmail and FTP logins. Repeated failed logins there get the address blocked. Addresses you exempt are not blocked. This protection is removed together with cPGuard. The CPGuard page and its Health row show its state and warn when cPGuard's login protection is stopped.
- ModSecurity by default (AB-1960): New installations turn ModSecurity on in the default Apache profile. The WordPress block editor saves normally with its rules. Existing servers keep their ModSecurity setting. Re-applying the default profile turns ModSecurity on.
- Imunify360 integration (AB-1674): Imunify360 installed from the panel works with the panel's web server, ModSecurity, login protection and certificates. A failed install names its cause, such as a refused licence or an unreachable repository. A failed first install is rolled back. WebShield serves each site the certificate of its own account. It follows a changed certificate, domain or hostname, also on demand with
bolt-cli imunify360-webshield-sync. Existing installs are repaired on upgrade.
- JetBackup firewall access (AB-1853): When JetBackup is installed, Firewall Rules has a JetBackup access dialog. It keeps the JetBackup port open, limits it to networks you choose or closes it. Fix System Ports,
bolt-cli setup-firewall and the JetBackup installer keep this choice. The upgrade carries over a source or block you set by hand on the JetBackup rule. The admin REST API offers the same setting under /api/admin/firewall/jetbackup.
Panel design and settings
- New panel design (AB-2081, AB-1817): The admin, reseller and client panels share a calmer, consistent look with a neutral dark theme. The client Home page fits a phone screen. Logs is one menu entry, with Activity Log as one of its tabs. DNS, Redis instances and Plan limits moved out of General Settings. Networking is now Hostname & SSL. Old links to the moved tabs lead to their new place. Health has a MySQL page on servers with a MariaDB profile in Database Settings. With the PostgreSQL module installed, it also has a PostgreSQL page. The Hostname & SSL tab opens with one status card for DNS, the certificate and reverse DNS.
- Panel preferences (AB-2121, AB-2122, AB-2123, AB-2124, AB-2125): The General tab of General Settings sets the default language for users who have not picked their own. It also sets the timezone that dates are shown in.
- Panel security settings (AB-2121, AB-2122, AB-2123, AB-2124, AB-2125): The new Security tab in General Settings sets the session lifetime. It can require two-factor authentication for administrators, resellers or clients. It can also limit the admin panel to a list of IP addresses. A list that would lock you out is refused. The list can be cleared from the server's command line.
bolt-cli admin-two-factor-reset <username> resets an administrator's two-factor sign-in.
Multi-server management and DNS
- Secondary DNS checks (AB-1922): The panel checks what each secondary DNS server serves for every zone. Global DNS Zones and Secondary DNS Servers show the result and the time of the last check. A secondary that stops answering is marked Not answering. A zone that keeps failing raises a Health issue naming the zone, the secondary and the reason.
- Zones for new secondaries (AB-1833, AB-1868): A server that becomes a secondary DNS server receives every existing zone, however it joins. Resync DNS and Resync All Zones send the zones to every active secondary in the background. The new Send zones action on the node and Secondary DNS Servers rows sends them on demand, also through the admin REST API. After each send the panel confirms that the secondary serves every zone in its current version. The result names each zone that did not arrive and why. Connect Node to the address of an unpaired node reconnects it with its roles and zones. When a secondary registers under a new address, the hub keeps only its current address.
- Per-zone DNS sync status (AB-1807): For each node zone, Global DNS Zones shows the result and time of the hub's last sync attempt. It also shows whether the hub holds that version. A Zone sync window for each node lists all of the node's zones page by page, including zones the hub has not stored.
- Zone removal on secondary nodes (AB-1804): A zone deleted on the hub is also removed from the nodes with the Secondary DNS role. The upgrade registers each of those nodes again and names any node that is not converted yet. Register again names what to upgrade on that node.
- DNS cluster protection (AB-1806): The DNS cluster protects the zones that the hub and each node with the Secondary DNS role exchange. Existing clusters get this protection on upgrade. A warning names each node that is not protected yet, with the reason.
- SOA nameserver rule (AB-1805): The primary nameserver in the SOA record of a new domain zone follows a rule you set in DNS Templates > SOA settings. It is either the first NS record the template produces or a fixed nameserver name. Apply Template and
bolt-cli dns-rewrite-soa-mname --all apply the rule to existing zones. Use --domain for a single domain. The admin API offers the same under /api/dns/soa-settings and /api/dns/soa-mname/rewrite. The rule does not apply while the DNS cluster is enabled.
- Secondary DNS turn-off (AB-1860): On a node that runs 1.9.3, turning off the Secondary DNS role reports success once the node has finished. When the node could not finish, the hub names the failed step and lists any zones left on the node. The next save of the node tries the turn-off again.
- Settings after hub mode change (AB-1840): Every Settings page opens right after hub mode is turned on or off. Secondary DNS Servers moves between Settings and DNS Cluster to match.
- Source node DNS after migration (AB-1832): After a node migration's DNS cutover, the source node's copy of each moved zone points its A and AAAA records for the source server to the new server. A record that cannot be moved this way leaves the migration completed with warnings. This applies to node migrations run on 1.9.3. When the target account or node is removed, the source node answers with its previous records again.
- Node health (AB-2003, AB-1999): When a node answers the hub's health check without its services list, Health and Check node health show its services state as unknown. They show when the list last arrived and the next step. The health of a web node reflects the web server it runs: Apache, LiteSpeed Enterprise or OpenLiteSpeed. The recovery notification is sent once the node is healthy again.
Certificates and hostname
- Free certificate replacement (AB-1911): Some certificates are not renewed automatically. Examples are certificates from other authorities copied by a migration and free certificates on accounts with AutoSSL switched off. They get expiry reminders before they expire and on the day they expire. Administrators get them through System Notifications. The account owner sees them in the client panel bell. Replace with a free certificate swaps a certificate from another issuer for a free one. That includes imported, private and self-signed certificates. It works for one certificate or in bulk. It is on the admin and client SSL lists, the certificate page and the admin and client APIs. The installed certificate stays in place until the new one is issued. AutoSSL leaves another issuer's certificate in place unless you replace it. The expiry email and webhook templates get a
{{renewal_note}} variable that notes when a certificate is not renewed automatically.
- Hostname DNS and certificate (AB-1923): The panel checks that the server hostname resolves to this server. When it does not, Health warns with the resolved addresses and the next step. Saving a hostname runs the same check without blocking the save. The hostname certificate run replaces a self-signed certificate. A failed issuance appears in Health with its cause. The Certificate card on the Hostname & SSL tab shows the certificate in use, with a note when a new one is waiting to be applied.
- Hostname certificate history (AB-1849): Installing a purchased hostname certificate and switching back to automatic SSL are recorded in the hostname certificate history with their actual result. That includes a warning when the certificate is in place but a service did not reload. When the certificate authority cannot be reached or its certificate cannot be verified, the message says so. The Executions list shows the cause of a failed row.
- Hostname DNS zone (AB-1950): Changing the server hostname writes the hostname DNS zone for the new hostname. The upgrade repairs servers whose hostname already changed and keeps records added by hand. When no nameservers are set, it asks you to set them first. The previous hostname's zone is kept. Unless it was the default myboltip.com hostname,
bolt-cli dns-orphan-zones lists it. When a domain, a node or another DNS source already serves the hostname's zone, that zone is left as it is. The panel names the next step. A domain named like the server hostname is refused on create and rename. It is skipped with a warning on import. An account whose main domain is the server hostname is not imported.
- Previous hostname system mail (AB-1948): After a hostname change, the panel's
system@ and admin@ mail accounts of the previous hostname are switched off once mail works on the new one. Their stored mail is kept. The upgrade does the same for earlier hostname changes. bolt-cli manage-system-email-account --action=remove --hostname=<previous hostname> moves that mail to a dated folder and removes the two accounts. POST /api/system-mailboxes/previous-hostnames/remove does the same.
- Certificates after a domain rename (AB-1915): On an account with AutoSSL on, a renamed domain's free certificate is reissued under the new name in the next AutoSSL run. The mail settings of the previous name are removed.
mail.<new name> is offered as the mail host once a certificate covers it. The upgrade to 1.9.3 cleans up after earlier renames.
- External MX records (AB-1904): Issuing or disabling a domain certificate updates only the domain's MX records that point at the server. External MX records and MX records added by hand stay as they are.
Backups
- Failing backup alerts (AB-1924): When an account's backups to a destination start failing, the first failure sends a critical notification by email, webhooks and the admin bell. It names the account, the destination and the error. No alert is sent for a suspended account or while the alert's notification template is switched off. You set when the first reminder comes in the Settings dialog of System Notifications or through
/api/system-notifications/backup-failure-streak. Further reminders follow while the backups keep failing. Health lists each account whose backups to a destination keep failing, until a backup succeeds. The Backups page shows the last successful backup and the failures since.
- Set up backups guide (AB-1735): Until the first account backup has run, the Backups overview shows a Set up backups checklist. The steps are adding a destination, creating a policy and waiting for the first backup. When no server-wide policy exists, the policy step preselects one. The first two steps link to their forms. The guide notes that a local path destination does not keep backups off-site.
- Backup repository folders (AB-1986): Each server keeps the account backup repositories it creates from now on in a folder of its own. Existing repositories keep their path. When this server cannot open a repository, the message asks you to create a new destination for this server.
- Backup file browser and search (AB-1913): The backup folder browser in the client panel reaches every file in a large folder through Load more. The backup file search shows the first 200 matches and says when there are more.
- Account export with deleted domains (AB-1964): An account export, such as a transfer between nodes, completes when some records belong to a deleted domain. Examples are mailboxes, FTP accounts, redirects and certificates. Logs > Panel Error lists them. When such an export is imported, FTP accounts and Git repositories come back without a domain. The other records are skipped and listed in the import's provision log.
Server management
- Reboot server (AB-1302): System Updates > OS packages has a Reboot server action. It is highlighted when the package check reports that a reboot is due. The confirmation says what stops and asks you to type
reboot. A reboot is refused while a package install or update is running. The page follows the reboot and reloads once the server is back. Every reboot request goes to the audit log. The admin REST API offers it at POST /api/system-updates/reboot.
- Update that did not start (AB-1838): System Updates recognises an update that did not start or found another update running. It shows a notice and returns to the version screen. Clear the update status,
bolt-cli clear-update-status and POST /api/system-updates/clear-status reset the stored update state while no update runs.
- Upgrade warnings (AB-1804): Upgrade steps that end with a warning appear on System Updates with Dismiss. They are also listed under
/api/system-updates/upgrade-step-warnings.
- Unreadable stored data (AB-1921): Health lists stored values the panel cannot decrypt, grouped by feature. Each group shows the number of records, the fix and a link. The same list is available under
/api/admin/health/encrypted-storage. A backup repository the panel cannot unlock gets Start a new repository, which keeps the old repository and its password.
- Settings saved once applied (AB-1864): Several settings pages save a change once the server runs it. They are Database Settings, the FTP server settings, MyApache Settings, ModSecurity and LiteSpeed Settings. The login protection settings and jails work the same way. A refused change saves nothing. It shows the cause and keeps your edits for a retry.
- Service install status (AB-1759): An install or removal whose progress the panel lost, for example after a restart, is closed on Health > Manage services. The service's actions are offered again, with a note that the last result is unknown.
- Module install errors (AB-1858, AB-1808): A failed install of LiteSpeed, OpenLiteSpeed, LSPHP, mod_proxy_lsapi or Passenger gives its cause in the notification and the Provision Log. Other failed
bolt-cli manage-* jobs give it in the execution log. A package that cannot be found is named, with the repository to enable. bolt-cli manage-my-apache-mod-proxy-lsapi --action=install follows the same rules as Module Manager. After an install it reports whether Apache loads the module and gives the next step.
- Firewall rules (AB-2008, AB-2004, AB-1798): The source and destination ports of a firewall rule are checked when you create or edit it. A stored rule whose port cannot be read is left out of the firewall. Firewall Rules and System Updates list it with the reason until it is fixed. A rule that applies to all traffic has its own confirmation message. When another firewall service on the server blocks ports the page lists as open, Firewall Rules warns and gives the command that stops it. The upgrade applies the firewall rule for DHCPv6 replies on IPv6. It then removes the manual workaround rule described for 1.9.0.
- Existing home folders (AB-2018): Creating a hosting account whose home folder already exists is refused before anything is stored. The message names the folder. Health warns about home folders that belong to no hosting account and no system user.
GET /api/admin/health/orphaned-homes lists them too.
- Stats refresh interval (AB-1789): The stats refresh interval on the Scheduler tab can be set to Automatic. An interval chosen earlier carries over. The old default becomes Automatic.
Websites and applications
- Web server reloads and status (AB-1689, AB-1973): The Served column on the client Domains page shows whether each domain is served, pending or not served, with the reason and the next step. The client and admin domain APIs return the same status. When the server cannot reload the web server, the account or domain is still created. A warning names the cause and the next step.
- Applications on LiteSpeed Enterprise drop-in (AB-1559): Node.js and Ruby applications run on LiteSpeed Enterprise in Apache drop-in mode. Applications carry over through a web server switch, a domain rename and an account restore. Logs shows an application's start-up errors. On any web server, an application whose last change the server did not confirm shows Needs attention with Apply again.
- Python applications and LiteSpeed runners (AB-1559, CloudLinux Only): Python applications also run on LiteSpeed Enterprise in Apache drop-in mode. Set up LiteSpeed runners in the Runtime Manager installs what Python and Ruby applications need there.
- Node.js version over SSH (AB-1842, CloudLinux Only): An application's Node.js version can be used from SSH and the SSH Terminal. Edit Application shows a command to copy that opens the application root with that version's
node, npm and npx. The application root holds an activate file to load with source ./activate. The client API returns the same under application.ssh.
- LiteSpeed and alt-php capacity (AB-1977, AB-1978): LiteSpeed Enterprise, OpenLiteSpeed and alt-php can keep more files open at once. This also applies when LiteSpeed was installed later. The running web server gets it on upgrade. The upgrade names any configuration file that sets a lower limit.
- Managed .htaccess changes (AB-2001): Redirects, Error Pages, Indexes, IP Blocker, Hotlink Protection, AI bot blocking and site notices check the account's folders before they change files there. A refused change leaves everything as it was and gives the reason and the next step. IP Blocker and AI bot blocking report a rule they could not write as a partial change with a warning. When an account is suspended, a site whose folder links outside the account's home also shows the suspension page. Suspend and unsuspend name any domain that needs attention. A suspended account's own API key is read-only.
- Private Directories scope (AB-1998): Private Directories protects folders inside the account's own home. That includes document roots that point to another folder in that home. On OpenLiteSpeed, a folder name the panel cannot protect is refused with the reason and the next step.
- WordPress uninstall (AB-1905): Uninstall removes the WordPress core files, its folders and
wp-config.php. It keeps every other file in the folder, including .htaccess. The database is deleted unless another WordPress installation on the account may use it. The confirmation names the folder and the database.
- Softaculous install check (AB-1700): A Softaculous install that does not complete fails with the installer's explanation. Install also repairs an incomplete Softaculous installation.
PHP
- PHP change verification (AB-1861): When the panel finds that a site still runs another PHP build after its domain's PHP version changes, the change is rolled back. The panels and the REST API name the build the site still uses and the build that was requested.
- LSPHP extensions and PHP configuration (AB-1874): Configure PHP Version switches the LSPHP extensions installed for a version on and off on the server. Switching OPcache or an extension off keeps its settings for when it is switched back on. On LiteSpeed Enterprise and OpenLiteSpeed, an applied LSPHP configuration takes effect at once. On LiteSpeed Enterprise, so does an applied alt-php configuration. Switch to MyApache names the domains still on LSPHP.
- PHP error display upgrade step (AB-1865): The upgrade step that switches PHP error display off saves the new value for a PHP version once the server runs it. Configure PHP Version then matches what visitors get. A version the server cannot apply keeps its setting. The step runs again on the next upgrade or with
bolt-cli run-upgrade-steps --retry-failed.
- PHP version over the API (AB-1863): Creating a domain through the admin or client REST API with
php_version_id sets the domain up on that PHP version. The response returns it.
CloudLinux
- PHP Selector for websites (AB-1957, CloudLinux Only): A PHP version a customer picks in the client PHP Selector also applies to the account's websites. They move to the matching alt-php version.
native leaves them as they are. The most recent change wins, from PHP Selector or a main domain PHP change. Upgrading the panel switches no site.
- PHP Selector save confirmation (AB-2020, CloudLinux Only): When a version saved in the client PHP Selector does not take effect at once, the panel applies it in the background. The customer is told. A failed apply shows on the page and notifies the administrators and the account. Customers can pick only the versions offered to them.
- alt-php build for Softaculous (AB-1958, CloudLinux Only): Softaculous installs and upgrades on a domain with an alt-php version use that domain's alt-php build.
- Apache modules after conversion (AB-1803, CloudLinux Only): On servers with Apache, PHP runs inside each account's LVE as soon as a conversion finishes. Applying a MyApache profile keeps it that way. Servers converted earlier get this on upgrade. Install mod_hostinglimits in the Isolation Report takes effect in the same click.
- CageFS Enable All (AB-1809, CloudLinux Only): Converting a server keeps CageFS in Enable All, so every hosting account runs inside CageFS. That includes accounts created later. The panel's own system users and the administrators' login users keep their access, also on servers converted earlier. The Isolation Report lists other users in CageFS. It offers Retry the CageFS set-up for a set-up that did not finish.
- Conversion errors (AB-1736, CloudLinux Only): A failed conversion shows its reason live on the installer page, such as the check that failed or the missing packages. Each failed run has one correlation ID.
- LVE Manager frame height (AB-2016, CloudLinux Only): The admin LVE Manager and the client CloudLinux pages fit their frame to the window and scroll inside it. Wide tables in the admin LVE Manager scroll sideways.
- MySQL Governor (AB-2000, AB-2017, AB-2065, CloudLinux Only): On a server that already runs Governor, the MySQL Governor page says that MySQL Governor is installed and offers no install. A panel install that failed partway keeps Retry install. An install that waits for another package operation shows as queued and names that operation. A failed install gives its cause and the next step, says whether the database server is running and offers a retry. Remove MySQL Governor shows each step of the removal. The databases are offline for a short time while the database packages are replaced. A failed removal shows what it left behind and whether the data files were touched. It offers Retry the removal and names a missing package that keeps the database server from starting.
- Reseller LVE limits (AB-1906, CloudLinux Only): A reseller LVE limit below the sum of its accounts' plan values is refused per resource, with the current sum and the limit. A reseller already over a limit can still be saved with other changes. Its accounts can move to plans that raise no limit. After the upgrade, administrators get one notification for each reseller already over its LVE limit.
Mail, databases and accounts
- System mailboxes in Roundcube (AB-1946): Email > Mailboxes lists the panel's own
system@ and admin@ mailboxes for the hostname. Each has Open in Roundcube, which signs the administrator in with a single-use link. The admin REST API offers the same sign-in under /api/system-mailboxes/{mailbox}/webmail-sso.
- Mailbox API and sending suspensions (AB-1739, AB-1971): A mailbox password set through the client or admin REST API follows the panel form's rules and is applied to the mail server. The mailbox create and update APIs accept the documented fields. They refuse any other field and name all of them in one error. A sending suspension records who applied it: the sending limit, an administrator or the client. A client can lift only a suspension it set itself. The client panel says who suspended the mailbox and when sending returns.
- Database name ownership (AB-1982): A new MariaDB database is refused when its name is already in use on the server. The panel and both APIs refuse it. The APIs answer
409. Health lists a database name shared by more than one account as a critical Databases issue.
- Reseller hosting plan selection (AB-1937, AB-1908): Create Hosting Account and Edit Account in the reseller panel offer and accept the reseller's own hosting plans. Edit Account also offers the account's current plan.
- Extra open_basedir paths (AB-1936): Extra open_basedir Paths in Edit Account is set by administrators.
- Addon domain count (AB-1930): The Addon Domains count of a hosting account no longer includes its main domain. An account with only its main domain shows 0 addon domains. A plan with Addon Domains set to N lets the client add N domains besides the main one. Adding a domain, changing a plan and the displayed counter all use this count. An account migrated from another control panel with all its addon domains in use stays within its limit. Existing plan values are not changed, so every plan with a limit now allows one more domain than before. Unlimited plans stay unlimited. To keep the previous limit of a plan set above 1, lower its Addon Domains value by one. Do not lower a plan set to 1 to 0, because 0 means unlimited. A limit of the main domain only can no longer be set. An account shows the new count after its next Refresh Data or scheduled stats refresh.
- Domain plan limits (AB-1862): When the hosting plan stops a new addon domain, subdomain or parked domain, the client panel and the REST APIs name the limit that was reached.
- Last known disk usage (AB-1791): When a home folder cannot be measured, the account pages, the hosting accounts list and the client dashboard show its last known size. It is marked as stale and the limits use that size. Usage details opens at once on the last figures and says when they were taken. A home folder that stays unmeasurable notifies every administrator.
- Usage details at zero usage (AB-1931): In Usage details, a resource with nothing used shows 0%. N/A marks a value that has not been measured.
- Disk Used and Quota sorting (AB-1912): The hosting accounts list sorts by Disk Used and Quota, with accounts without a figure last.
- Client panel record access (AB-1970, AB-1981): Client panel lists, searches and row and bulk actions show and act on the signed-in account's own records. Git Version Control, its pull and history and the SSL status on Domains and the client dashboard answer for the account's own repositories and domains.
- Git SSH Keys menu entry (AB-1969, AB-1226): For plans that include Git Version Control, Git SSH Keys appears under Security in the client menu and in the menu search. The list shows the hosting account each key belongs to. Search matches the key name or that domain.
Fixes and smaller changes
- Nameserver Selection and cron (AB-1683): Nameserver Selection reports whether the DNS server started or stopped. When it did not, it gives the reason, the next step and a correlation ID. A DNS server that fails to start is switched back to Disabled. One nameserver change runs at a time. Admin Cron Jobs refuses a job for a system user that does not exist and says why.
- Reserved names (AB-1689, AB-1973, AB-1809, AB-2081, AB-1817): A few more account names are reserved for the system. A new administrator cannot take a username that already exists on the server.
- Health in your language (AB-2010): Health issues, the dashboard attention card and the mail and web server dashboards follow each administrator's interface language.
- OS package list after updates (AB-2015): After Install system updates or Install security updates, the OS packages tab refreshes on its own when the new package counts arrive.
- Table actions in pop-up windows (AB-1984): Row actions of tables inside a pop-up window work every time it opens. Examples are Restore, Delete and Edit Privileges in the client Databases edit window.
- Logs, Metrics and language list (AB-1230, AB-1232, AB-1238, AB-1239, AB-1242, AB-1496): The Logs tabs other than Executions have a Refresh action. The Module filter narrows the rows. Logs Center applies the open tab's text filters. Without its module, Metrics says that the module is not installed. The client mailbox form selects the first domain by default. The language list fits the window.
Install
curl -sSL https://get.adminbolt.com/install.sh | bash
Upgrade from 1.9.2
- Log in to the Admin Panel.
- Open Settings, then System Updates under System.
- Click Check for updates and review the release notes.
- Click Install update if a newer version is available.
