adminbolt 1.2.0: CloudLinux and LiteSpeed, Natively Integrated

·adminbolt team·6 min read

If 1.1.0 was about running many servers as one system, 1.2.0 is about making each of those servers a lot more powerful. This release brings two of the most requested platforms in the hosting world, CloudLinux and LiteSpeed, straight into the panel as first-class integrations, and rebuilds the PHP version manager underneath them so every engine can run side by side.

The short version: you can now convert a server to CloudLinux from a guided page, switch between Apache and LiteSpeed whenever you want, and manage regular, CloudLinux and LiteSpeed PHP builds from a single screen without them stepping on each other. Here's what that looks like day to day.

CloudLinux, from install to per-account limits

CloudLinux used to be the thing you set up before adminbolt. Now it's a page inside it.

A new guided installer walks you through the whole activation: enter your license key, run a pre-check that validates the key and the system, then convert the server with a live log so you can watch each step. The page tracks the full lifecycle and surfaces a Reboot now action at the exact moment the server is waiting to switch kernels, so you're never guessing whether it's safe to restart. If a conversion stalls, the installer detects it and recovers instead of leaving you stuck.

Once the server is converted, you pick which CloudLinux runtimes to turn on, PHP and mod_lsapi, each with its own version picker and progress log. The integrated LVE Manager installs on demand straight from the panel, with single sign-on, so managing per-account resource limits doesn't mean a second login.

The part operators will feel most is resource limits tied to hosting plans. Plans gain a Resource Limits tab, CPU speed, memory, IO, IOPS, processes and entry processes, and adminbolt pushes those limits to the matching CloudLinux package automatically when a plan is created, updated, or an account is provisioned. Existing plans are not left behind: a backfill brings plans you built before the upgrade in line too, so this works on servers that were running long before 1.2.0 shipped.

Apache or LiteSpeed, switch on demand

1.2.0 adds full LiteSpeed support, and it treats the web server as something you can change your mind about.

You can switch between Apache and LiteSpeed from the panel. The license is checked first, the incoming server's saved settings are applied before the cutover, and both servers are stopped and started in a safe order so live requests aren't dropped mid-switch. Around that sit the things that make LiteSpeed worth running:

  • LSCache per domain: turn caching on or off, tune TTLs, cap object size, exclude paths, and clear a domain's cache, all from a dedicated page.
  • Settings and profiles: a LiteSpeed settings page for server, security, performance and modules, backed by sensible defaults applied on install.
  • Logs and admin: built-in access and error log viewers, a one-click restart, and direct access to the LiteSpeed WebAdmin console.

One PHP manager, three engines

Underneath both integrations is a rebuilt PHP version manager, and it's a genuine upgrade for anyone who has fought PHP versions on a shared box.

It's now a single page to install, remove, configure and set default profiles for every engine: regular (REMI), CloudLinux Alt-PHP, and LiteSpeed LSPHP, with vendor logos and clear per-version labels. The important change is that domains and plans now reference a specific PHP version, so the regular, CloudLinux and LiteSpeed builds of, say, PHP 8.3 no longer collide. Alt-PHP covers 5.x through 8.x and LSPHP covers 7.4 through 8.5, and a version that's still assigned to any plan or domain can no longer be uninstalled by accident.

Two smaller touches matter more than they sound. Install or remove a PHP version over SSH and the panel notices on its own and wires up a matching default profile, no manual refresh. And the default disabled-functions list for PHP profiles has been tightened, so shared-hosting environments start from a safer baseline.

When you switch web servers, a dedicated migration page moves your domains and plans between matching REMI and LSPHP versions, with a dry-run preview first. Switching back to Apache is blocked, with a direct link to the migration page, while any domain still uses LSPHP, so a server switch can't quietly break sites.

The operational details

A few changes exist purely to make running the panel calmer. Background operations are now written to a durable execution log with a title, status, timing, and the operator and IP that started them, plus a richer, colour-coded log viewer, so you can see what ran and who ran it. Resellers can now open the full account detail view for their own accounts. And there are small conveniences throughout: copy actions on hosting plans and feature lists, and a new Resolver Configuration page.

CloudLinux and LVE Manager interactions are also noticeably faster in this release, so the parts of the panel you touch most when managing limits feel snappier.

Fixes worth calling out

1.2.0 also clears a batch of bugs, and a few are worth naming because you'd have felt them: the Safari sign-on issue on the LVE Manager page is resolved, Apache is now fully restarted after enabling modules that require it, the PHP-FPM toggle shows up correctly, Alt-PHP versions no longer shadow usable PHP binaries on the command line, the WordPress one-click installer is fixed, and system notification email fallbacks are corrected so alerts actually get delivered. The in-panel changelog has the complete list.

Upgrading is one click

If you're on 1.1.0, upgrading is done entirely from the panel. Open the Updates screen in the admin UI and apply 1.2.0, the one-click updater shows live progress, runs the version-specific upgrade steps for you, including the resource-limit backfill mentioned above, and reports when it's done. Take a backup first (the built-in backup or JetBackup both work), and expect only a brief interruption on a typical VPS.

None of this is forced on you. CloudLinux and LiteSpeed are opt-in, and a plain Apache server with regular PHP keeps working exactly as it did.

Where this goes next

1.2.0 turns adminbolt into a panel that speaks CloudLinux and LiteSpeed natively, on top of the multi-server foundation from 1.1.0. The public roadmap is the place to see what builds on it next.

Running CloudLinux or LiteSpeed, or thinking about it? This is the release that brings them into one place. Tell us how it goes on Discord, the community forum, or via the contact form.

← Back to Blog