| docs

Appearance

LiteSpeed Dashboard ​

Where to find it: this is the Overview tab of LiteSpeed, at /admin/web-server/litespeed, in the Web Server area.

The LiteSpeed Dashboard is the control center for the LiteSpeed web server. From here you see which web server is currently active, switch between MyApache and LiteSpeed, manage your license, restart LiteSpeed, and open the native WebAdmin console.

This page is the per-view reference for the dashboard. For the full end-to-end workflow (install, license, switch, PHP migration, roll back), see Integrations > LiteSpeed.

Overview ​

URL: /admin/web-server/litespeed

The page is the LiteSpeed tab of Web Server in the sidebar. Since panel 1.9.2 the tab is in the bar only while LiteSpeed Enterprise is installed or is the web server the panel is set to; install the litespeed module from Modules, or with Install on the LiteSpeed card of the Web Server overview, to bring it in. Its settings and cache tabs are documented on LiteSpeed Settings and LiteSpeed Cache.

AdminBolt runs one web server at a time: MyApache (Apache) or LiteSpeed. The dashboard shows the current state and the actions you need to manage it. Since panel 1.9.0, OpenLiteSpeed has a card of its own on this page, so its state is never shown on the LiteSpeed Enterprise card.

Active web server ​

The Webservers card shows which server is currently serving traffic and lets you change it:

  • Switch to LiteSpeed - prepares LiteSpeed's configuration while MyApache still serves, then stops MyApache and starts LiteSpeed. The switch counts as done only once LiteSpeed serves on ports 80 and 443, and the banner then changes to LiteSpeed is Active. If LiteSpeed does not start or does not take the ports, the panel tries to start MyApache again, and the message says whether MyApache is serving again or the sites are down.
  • Switch to MyApache - returns the active server to Apache. This is blocked while any domain is still on an LSPHP version, because Apache cannot serve LSPHP; migrate those domains back to REMI first (see below). Since panel 1.9.2 the button is hidden while Apache is already the active web server, and the panel refuses the switch then, even from a page opened before Apache became active. Since panel 1.9.3, a switch refused because of LSPHP domains names them, up to five and the number of the rest, and Open PHP Migration takes you to the move.

The banner names the server that is active, for example LiteSpeed is Active or MyApache (httpd) is Active. Refresh Status reads it again. Since panel 1.9.2, when the panel cannot read which web server runs, the banner reads Web Server State Unknown, Apache's Running shows Unknown, and no switch to MyApache is offered. Use Refresh Status; if the state stays unknown, check that the server agent is running.

Switching the active server affects every site on the node and causes a brief interruption, so plan the change for a quiet moment. After switching to LiteSpeed, move your domains to the matching PHP engine on the LiteSpeed PHP Migration page. To go back to Apache, run that migration in the LSPHP → REMI direction before switching - otherwise the panel refuses the switch and lists the domains still on LSPHP.

Native mode and the Apache drop-in ​

Since panel 1.9.0, LiteSpeed Enterprise runs in one of two modes, shown as Mode on the LiteSpeed card:

ModeWhat it means
NativeLiteSpeed serves from its own configuration, with its own virtual host for each domain. Node.js, Python, and Ruby applications can be served.
Apache drop-inLiteSpeed reads the Apache configuration, as it did before 1.9.0. Applications cannot be served.

A new LiteSpeed installation, made with panel 1.9.0 or later, runs in native mode. A server where LiteSpeed was installed before keeps the Apache drop-in until you convert it. While a serving LiteSpeed still reads the Apache configuration, the Needs attention card on the dashboard and Health show a warning that links to this page.

  • Convert to native mode - shown while LiteSpeed is the active web server and runs as the Apache drop-in. The panel writes a virtual host for every domain first, then restarts LiteSpeed once. If LiteSpeed does not serve afterwards, the panel puts the Apache drop-in configuration back and says what went wrong. Existing PHP versions keep working; the conversion does not move any domain to another PHP engine.
  • Revert to Apache drop-in - shown in native mode. LiteSpeed reads the Apache configuration again and restarts once. Applications stop being served on the server until you convert it back.

In native mode, the Apache-style settings on the settings tab are stored but not applied, and Apache Includes are not read. Real visitor IP settings still apply.

License Serial ​

The License Serial card shows the current LiteSpeed license state. It reads Not Set right after installation.

  • Update License Serial - enter your paid LiteSpeed license serial, or tick Use Trial Key to start with a time-limited trial. Keep Restart LiteSpeed after applying the license key enabled so the change takes effect immediately.

Once applied, the Current Serial shows your key (masked).

The trial key is meant for evaluation only. Apply a paid serial for production use.

Restart LiteSpeed ​

Use Restart LiteSpeed to restart the server after a configuration change or to recover from a transient issue, without switching the active web server.

LiteSpeed Admin Details ​

For advanced tuning you can open the native LiteSpeed WebAdmin console:

  1. Click LiteSpeed Admin Details.
  2. The panel shows the WebAdmin URL (on port 7080) and a generated admin password. Click Open LiteSpeed Admin Panel, or copy the URL and password to sign in.

The WebAdmin console is a separate admin surface. Keep port 7080 reachable only from trusted networks, and safeguard the generated password rather than exposing the console publicly.

The WebAdmin console is LiteSpeed's own tool rather than an AdminBolt screen; see the LiteSpeed documentation for how to use it.