AdminBolt 1.9.0: Enforced Plan Limits, Whole Account Restore and Maintenance Mode

AdminBolt 1.9.0 is out. Hosting plans now enforce their disk space, inode and bandwidth allowances. A backup can bring back a whole account with its mailboxes, databases and database users. Clients can put a single domain into maintenance mode.

Plan limits that are enforced

A hosting plan lists disk space and bandwidth. In 1.9.0 the panel enforces them. Plans gain an Inodes limit as well.

The switches live under Settings > General Settings > Plan limits. Disk and inode enforcement comes with a headroom above the plan (10% by default) and a grace period (7 days by default). Two more switches act on accounts whose databases spend the disk allowance and on accounts over their monthly bandwidth. You choose the usage level to act at. An account over its limit can show its visitors a notice page that names the limit.

On a fresh installation that supports it, plan limits apply from the first account. If the server cannot enforce them, the installer says so. Upgraded servers start with enforcement off. You prepare the server with one command, then turn enforcement on in the panel. The command tells you when the server needs a reboot first.

bolt-cli manage-disk-quota --action=install

Plan changes follow real usage now. An account that fits a larger plan can move to it. Mailing Lists limits are enforced too. Clients see one Disk Usage bar for files and databases together, with the databases as a labelled part. The Disk Usage page also shows how many files the account holds against its inode limit.

Whole account restore

Account backups now carry the account's mailboxes, databases, database users and grants. The new Whole account restore mode uses them. It puts the home directory back and recreates whatever is missing with its original passwords. It imports the databases it recreated. Mailboxes and databases that still exist are left as they are.

Restore Jobs shows a report with the outcome for every item: recreated, left as it was, failed or not restored. Restore to new account uses the same mode when the original username is kept. Whole account restore works with backups taken after the upgrade to 1.9.0. PostgreSQL databases are outside its scope.

Clients whose plan includes Backups now always see the Backups page. When nothing runs, the page explains why: there is no policy, the policy is off or the account opted out. In the admin panel, Backup Policies and the plan form warn about plans that no policy covers.

Maintenance mode for a domain

Clients have a Maintenance mode action on their domain list. Turned on, the domain shows visitors a maintenance page. The page is the client's own HTML or a default one. Maintenance can end on its own after a number of hours the client sets. The domain list shows whether a domain is off, on or on until a set time. Certificates are issued as usual while it is on. It works on Apache, LiteSpeed Enterprise and OpenLiteSpeed.

Operation hooks

Settings > System > Operation Hooks connects your own scripts to what happens in the panel. A hook runs before or after a hosting account or a domain is created or deleted. It can also run after a DNS record changes or a mailbox is created or deleted.

A hook that runs before an operation can stop it. When the script fails, nothing is created and the user sees the first line of its output. Each hook shows its last run with the result, exit code and duration. Run test sends a sample payload, so you can try a script before it matters.

Secondary DNS servers

Settings > DNS > Secondary DNS Servers sends your zones to your own secondary nameservers. The page gives ready-to-paste setup instructions for the secondary. New and deleted domains reach it on their own. Nameservers are a list now as well. Change Nameservers and General Settings hold an ordered list of at least two, with more added as you need. DNS templates can write one record per nameserver.

LiteSpeed Enterprise in native mode

LiteSpeed Enterprise can now run with a configuration of its own. In that mode it serves Node.js, Python and Ruby applications. New installations start in native mode. Existing LiteSpeed servers keep their current mode until you convert them from the LiteSpeed page.

The panel also checks which web server is really serving your sites. When it is not the configured one, the Attention Center raises a critical fault. The Web Server dashboard then offers to restore the configured server or adopt the running one.

ImunifyAV and CPGuard for clients

ImunifyAV, the free malware scanning edition, installs from Modules without an activation key. The admin page shows the last scan and the files it found across accounts. Clients see only their own files, behind a plan feature. When you want more, Upgrade to Imunify360 replaces it in one run.

Where CPGuard is installed and the plan grants it, clients get a CPGuard page of their own. It lists their scans and what each one found in their account. They can start a scan of their files themselves.

CloudLinux

CloudLinux conversion and converted servers get a set of fixes (CloudLinux Only). A failed conversion lists what is missing and explains known causes in plain words. The conversion stops before it changes anything when a check fails. Afterwards Apache is ready for AdminBolt hosting accounts. New accounts get a PHP version that runs. On a converted server WordPress tools work on alt-php. Clients find PHP Selector under Advanced when LVE Manager is installed and the plan includes it.

Smaller things you may notice

Settings > Security > Domain Security has a Blocked domains list. It ships with a default list of major mail and social providers. Adding or renaming a domain that matches it is refused for everyone, administrators included. Imports and migrations flag matching domains for review.

The new Integrations page lists the official billing integrations for WHMCS, Blesta and Upmind. On a trial, the License page shows the days left. Buy a license opens billing already signed in. The panel picks up the payment on its own.

Repeated failed panel sign-ins now block an address on the panel only. SSH, websites and mail stay reachable for it. Git Version Control has a History action with the last 20 commits. bolt-cli health-check checks the web server and MariaDB and starts a stopped service. A mailbox's Outgoing mail field and Suspend Sending are one control now.

Upgrading

Upgrades run from the panel. Open System, then System Updates, check for updates and start 1.9.0 from there. New installs are one command:

curl -sSL https://get.adminbolt.com/install.sh | bash

Tell us how it goes

Tell us how 1.9.0 works for you on Discord or the community forum.