| docs

Appearance

OpenLiteSpeed Dashboard ​

The OpenLiteSpeed Dashboard is the control center for the OpenLiteSpeed web server. From here you see whether OpenLiteSpeed is installed and serving traffic, switch between MyApache and OpenLiteSpeed, restart the server, open the WebAdmin console, and choose how .htaccess files are applied.

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

Overview ​

URL: /admin/openlitespeed

AdminBolt runs one web server at a time: MyApache (Apache), LiteSpeed Enterprise, or OpenLiteSpeed. The dashboard appears once the openlitespeed module is installed from the Module Manager.

Note: OpenLiteSpeed cannot be installed alongside LiteSpeed Enterprise, because both use /usr/local/lsws. A server runs one of the two.

OpenLiteSpeed dashboard with the server active

Web Server card ​

The Web Server card reports three separate facts, each as its own badge:

RowMeaning
OpenLiteSpeed installedThe packages are present on the server.
Active webserverWhich server the panel currently configures and serves with.
Service runningWhether the OpenLiteSpeed service is up right now.

The actions below the badges change with that state:

  • WebAdmin Console - opens the console details (see below). Available whenever OpenLiteSpeed is installed.
  • Switch to OpenLiteSpeed - stops MyApache (httpd), generates the native OpenLiteSpeed configuration for every domain, and starts OpenLiteSpeed. Shown while another server is active.
  • Restart OpenLiteSpeed - rebuilds the server configuration and restarts gracefully. Shown while OpenLiteSpeed is active.
  • Switch to MyApache - stops OpenLiteSpeed and starts MyApache. Shown while OpenLiteSpeed is active.
  • Refresh Status - re-reads the state without changing anything.

Switching the active server affects every site on the node, so plan the change for a quiet moment. The switch is reported as successful only once OpenLiteSpeed has started. If the configuration cannot be generated or the service does not start, the panel reports the failure and puts the previous web server back on the ports. That recovery is best effort: if the previous server also refuses to start, the failure is logged and the node is left without a running web server, so check the service state after any failed switch. When individual domains fail to generate their virtual host, the switch still completes and the notification names how many domains to review in the logs.

Warning: Going back to MyApache is blocked while any domain still uses an LSPHP version, because Apache cannot serve LSPHP. Move those domains back to REMI on the PHP Engine Migration page first.

Warning: On a CloudLinux server, switching to OpenLiteSpeed is blocked while any domain is assigned to an Alt-PHP version, which OpenLiteSpeed cannot serve. The refusal names the domains; re-assign them to an LSPHP or PHP-FPM version first.

WebAdmin Console ​

WebAdmin Console opens a dialog with everything needed to sign in to the native OpenLiteSpeed console:

  • Console URL - the console address, on port 7080, with an action that opens it in a new tab.
  • Username - admin.
  • Password - the current console password, hidden until revealed. A fresh install shows a placeholder until a password is generated.

Reset WebAdmin Password generates a new console password and applies it immediately. Open the dialog again afterwards to reveal the new value.

WebAdmin Console details with the password hidden

The WebAdmin console is OpenLiteSpeed's own tool rather than an AdminBolt screen. Keep its port reachable only from trusted networks and safeguard the generated password. See the OpenLiteSpeed documentation for what the console offers.

.htaccess handling ​

OpenLiteSpeed reads .htaccess rewrite rules when it starts, not per request. The .htaccess handling card decides how AdminBolt bridges that difference. Pick a Mode and click Save:

ModeBehavior
Restart on change (recommended)A watcher detects a changed .htaccess and restarts the server gracefully, so rules take effect the way they do on Apache.
Per-request module (experimental).htaccess is interpreted per request, with no restarts at all.
Off.htaccess files are not applied.

Panel-managed protections (IP blockers, private directories, error pages, and index settings) are enforced natively in the OpenLiteSpeed virtual host in every mode. Directives written into .htaccess by hand that are not rewrite rules, for example Deny from or AuthUserFile, are not interpreted.

Module mode requires the bolt-ols-htaccess package. When it is missing, the option stays disabled and the card says so; the package installs automatically when it is available in the package repository.

Sites in watcher fallback ​

A site whose .htaccess uses a directive that module mode does not cover is flipped back to restart on change on its own, so it keeps serving. Those sites are listed on the dashboard with the directive that caused the fallback, and each has its own Retry button: clean up the .htaccess, then retry to put that site back on per-request handling.

The list stays visible in every mode, because a fallback flag remains until it is retried.

Watcher status ​

While the watcher is in use, the card reports whether it is active, how many document roots it watches, how many restarts happened in the current window against the allowed maximum, how many restarts were suppressed, and when the last restart happened. The last error, if any, is shown in full.

Use these counters when rule changes seem slow to apply: a high suppressed count means changes are arriving faster than the restart budget allows.