Uninstalling LiteSpeed Web Server can interrupt every website served by that instance. This guide is for the authorized server administrator. Removing a WordPress cache plugin is a different operation and does not uninstall the web server.
Identify the installation and replacement
Confirm whether the server runs LiteSpeed Web Server, how it was installed, its actual installation directory and any control-panel integration. The command below applies to LiteSpeed Web Server’s own installer. Do not assume it also applies to OpenLiteSpeed, a container image or a package-managed installation.
Before proceeding, save the web-server configuration and logs, verify recoverable site backups, and arrange console access independent of the web service. Record the installed version and the information needed to reinstall it. Agree on a maintenance window and on who can approve a rollback.
Test the replacement web service
If the plan is to return to Apache, use the supported switch procedure for that control panel first. Verify that the intended replacement serves representative sites with the correct PHP handlers, certificates, redirects and access rules. Test dynamic functions as well as static pages.
Keep LiteSpeed available until those checks pass. If the replacement cannot serve the sites correctly, resolve the problem before uninstalling. A successful package or script transaction is not proof that customer sites work.
Run the applicable uninstaller
The LiteSpeed installation manual locates the uninstaller beneath the installation directory. For the default /usr/local/lsws location, an authorized administrator can run:
/usr/local/lsws/admin/misc/uninstall.shConfirm the real path before using this example. The installer asks whether to retain logs and configuration. Preserve them for the agreed recovery and investigation period; do not remove useful evidence to complete the cleanup.
Validate the outcome
Repeat the same site checks after removal and examine the replacement service’s logs. Confirm monitoring targets and scheduled maintenance still match the active web server. Record failures separately from successful tests.
If there is an unexpected outage, use the prepared recovery plan and involve the responsible administrator. Reinstallation and restoration depend on the original integration; there is no safe universal command sequence for every server. Licence cancellation is also a separate action from uninstalling software.
For a Nuagerie-managed server, coordinate the change with support rather than starting from an individual hosting account.