LiteSpeed Web Server replaces Apache on cPanel servers chosen for their performance characteristics — better static throughput, native HTTP/3, drop-in EasyApache compatibility. The licence is paid, annual, and managed at the LiteSpeed portal. When the renewal date passes, the server keeps running on a grace period; if the licence file doesn’t update by the end of grace, LSWS falls back to a heavily rate-limited mode that customers feel immediately. The renewal is automatic at the portal; the propagation to the server is not always.
What’s happening
LiteSpeed’s licence ties to a serial number and a server identifier (IP plus hostname). At renewal time, the LiteSpeed portal extends the entitlement and updates the licence file at https://www.litespeedtech.com/. The lshttpd daemon polls for licence updates on a slow cadence — typically once a day — but the poll can be blocked by an egress firewall, a TLS interception proxy, or a DNS misroute. When the poll fails, the local licence file stays at the old expiry, and lshttpd enters grace, then degraded mode.
How to verify
Read the LiteSpeed licence state on the server:
/usr/local/lsws/bin/lshttpd -V
cat /usr/local/lsws/conf/serial.no
ls -la /usr/local/lsws/conf/serial.no
curl -v https://www.litespeedtech.com/check
tail -100 /usr/local/lsws/logs/error.log | grep -i licen
The -V flag shows the licence type and expiry date. The serial.no file mtime tells you when the licence last updated. The error log records licence failures explicitly.
The fix
- Confirm the portal shows the renewal applied. Log into the LiteSpeed portal, check the serial: the entitlement date should be at least a year ahead.
- Force a licence fetch from the server:
/usr/local/lsws/bin/lshttpd_licenseor/usr/local/lsws/admin/misc/lshttpd_licensedepending on version. The script downloads the current licence file from the portal using the serial. - Confirm the updated expiry:
/usr/local/lsws/bin/lshttpd -Vshould now show the new expiry. Theserial.nofile mtime should be current. - Restart LSWS to apply:
systemctl restart lshttpdor/usr/local/lsws/bin/lswsctrl restart. Existing connections drain; the restart takes about two seconds. - If the licence-fetch step fails: confirm egress to
www.litespeedtech.comover HTTPS, check for TLS interception (the licence file is delivered over HTTPS with cert pinning in some versions), and confirm the serial number on the server matches the portal record. - Set up monthly licence-expiry monitoring with a Nagios or Prometheus check that reads
lshttpd -Vand alerts at 30 days from expiry. The portal renews automatically; the server-side fetch is what needs eyes.
For shops running LSWS in production, Stack Harbor’s cPanel and WHM management practice tracks licence expiry per server and runs the renewal-propagation step as part of the monthly review so the daily poll isn’t a single point of failure.