Skip to main content

Core Foundations

This module builds the baseline mental model for OpenLiteSpeed so later configuration choices make sense.

Why this section matters

Many OpenLiteSpeed problems that appear later in SSL, PHP, or virtual host setup actually begin with weak foundations. If you understand the server model, filesystem layout, and admin workflow early, the rest of the stack becomes much easier to operate.

What you should learn here​

  • what OpenLiteSpeed is and when to choose it
  • how its event-driven model affects performance
  • how to install it safely on Linux
  • where important files live under the default install tree
  • how to access and navigate WebAdmin without exposing it carelessly

Web Server Basics​

What is OpenLiteSpeed​

OpenLiteSpeed is the open source edition of LiteSpeed Web Server. It is designed for fast static file delivery, efficient PHP execution through LSAPI, and low overhead under high concurrency.

LiteSpeed vs OpenLiteSpeed​

ProductLicensingTypical Use
LiteSpeed EnterpriseCommercialShared hosting, enterprise support, advanced enterprise-only features
OpenLiteSpeedOpen sourceSelf-managed servers, learning, cost-conscious production stacks

OpenLiteSpeed shares the same core design philosophy, but some enterprise features and compatibility conveniences are reserved for the paid edition.

Event-Driven Architecture​

OpenLiteSpeed uses an event-driven model rather than a process-per-connection design. A smaller worker pool can handle many simultaneous clients because connections spend most of their lifetime waiting on network or disk I/O.

Performance Characteristics​

  • Handles keep-alive connections efficiently
  • Reduces memory pressure compared with heavier prefork models
  • Performs well for PHP workloads when paired with lsphp
  • Supports HTTP/2 and HTTP/3 for lower latency delivery

Lessons in this group:

Installation​

Linux Installation​

OpenLiteSpeed is commonly installed on Ubuntu, Debian, AlmaLinux, Rocky Linux, and CentOS-derived systems.

Package Repository Install​

Repository-based installs are the best default because they simplify upgrades.

wget -O - https://repo.litespeed.sh | sudo bash
sudo apt update
sudo apt install openlitespeed lsphp84 lsphp84-common lsphp84-mysql

Use the equivalent dnf or yum packages on RHEL-family systems.

Source Compilation​

Source builds are mainly useful when you need a custom toolchain, patched dependencies, or a development build. Most administrators should prefer repository packages for operational simplicity.

System Requirements​

ResourcePractical Baseline
CPU1 to 2 vCPU minimum
RAM1 GB for light use, 2 GB or more for PHP sites
DiskEnough for logs, cache, app files, and backups
OSModern 64-bit Linux distribution

Lessons in this group:

Directory Structure​

/usr/local/lsws​

This is the default installation root and the main path every administrator should know.

conf​

Stores server-level and virtual host configuration, including httpd_config.conf and per-vhost config files.

logs​

Contains server logs, error logs, and often WebAdmin-related logs during troubleshooting.

Admin interface files​

WebAdmin binaries, templates, and supporting files live under the installation tree, typically alongside admin-specific configuration and SSL material.

Lessons in this group:

Admin Panel​

WebAdmin Console​

OpenLiteSpeed ships with a browser-based administration interface called WebAdmin Console.

Default Port (7080)​

You typically access it at https://server-ip:7080.

Login Credentials​

The admin username is usually admin. The password is set or reset with the helper command:

sudo /usr/local/lsws/admin/misc/admpass.sh

Basic Navigation​

The main areas to learn first are:

  • Listeners for port and SSL entry points
  • Virtual Hosts for per-site settings
  • Server Configuration for process, security, and logging controls
  • Tools and dashboard views for live status and graceful restarts

Lessons in this group:

Best Practices​

  • Prefer package installs unless you have a strong reason to compile
  • Learn the filesystem layout before editing live settings
  • Secure WebAdmin access with firewall rules or IP restrictions
  • Keep notes of any non-default paths for certificates, sockets, and vhost roots

Success checkpoint​

By the end of this module, you should be able to explain where OpenLiteSpeed runs, where it stores its major files, how to log into WebAdmin, and why its event-driven model behaves differently from older web servers.