| docs

Appearance

CloudLinux Installer ​

The CloudLinux Installer page is a guided installer that converts your server to CloudLinux. It walks you through activation, validates your environment, converts the operating system with a live log, and tracks the conversion through to completion.

This page is the per-view reference. For the full end-to-end workflow, including feature provisioning, the LVE Manager, and per-plan resource limits, see Integrations > CloudLinux.

Overview ​

URL: /admin/cloudlinux-installer

The installer has no sidebar entry of its own: open Modules in the sidebar and click the CloudLinux card. Converting a server to CloudLinux is a node-level, admin-only action, and it requires a reboot to take effect.

What the installer does ​

  1. License key - Enter your CloudLinux activation (API) key and validate it. A pre-check confirms the key and that the system can be converted.
  2. Conversion - Start the conversion. The panel converts the operating system in the background and streams a live deploy log.
  3. Reboot - When the conversion finishes, the server needs to reboot onto the CloudLinux kernel. Use the Reboot now action to restart it.

The installer reports the conversion state as it progresses:

StateMeaning
convertingThe OS conversion is running, with a live log.
installed-pending-rebootCloudLinux is installed; the server must reboot onto the CloudLinux kernel.
convertedThe server is running CloudLinux.

The admin API reports the installer state at GET /api/admin/cloudlinux/status. Its installed field is true once the conversion has finished and the server is running CloudLinux. Its running field is true only while a conversion is in progress, so running: false next to installed: true is the normal state of a converted server. Both fields describe the installer, not LVE or CageFS. You manage and check LVE and CageFS in Settings > CloudLinux > LVE Manager (/admin/settings/cloudlinux-lvemanager); see LVE Manager.

Warning: Converting to CloudLinux rewrites the operating system and is effectively irreversible. It interrupts active sessions and services and requires a reboot. Take a provider snapshot before you start.

When a conversion fails ​

Since panel 1.9.0 a failed precheck names the reason before the conversion starts, and a conversion that fails names its reason too. The installer lists the components a failed conversion could not install, next to the licence edition, and shows CloudLinux's own log below the conversion log. After Try again, the previous failed run stays visible with its outcome, stage, edition, running kernel, and log.

Since panel 1.9.3, the reason, such as the check that failed or the missing packages, shows on the page while you watch the run, not only after a reload. A failed run keeps one correlation ID, however often the page refreshes, so the ID you quote to support matches the panel log. See If the conversion fails.

After conversion ​

Once the server is converted, CloudLinux features become available in the panel:

  • LVE Manager - the native CloudLinux UI, embedded with single sign-on, for per-account resource usage and the language selectors.
  • Per-plan Resource Limits - a Resource Limits tab on hosting plans (CPU, memory, I/O, IOPS, processes) that pushes LVE limits to every account on the plan.
  • CageFS in Enable All mode - since panel 1.9.3, every hosting account runs inside CageFS, including accounts created later; see CageFS for every account.
  • Apache modules - on Apache, mod_lsapi and mod_hostinglimits are loaded as soon as the conversion installs them; see Apache modules on CloudLinux.
  • Isolation Report - whether every account is kept apart, the steps to get there, and the move of websites to CloudLinux alt-php. Since panel 1.9.0, the installer page links to it with Open Isolation Report once CloudLinux is installed.
  • BoltTerminal - the terminal module (listed as Terminal on the Modules page) for isolated per-account SSH access on CloudLinux.