If an update is unavailable in your control panel (or you just prefer the command line) you can update LSWS from the terminal.

The lsup command is a simple way to update LiteSpeed Web Server from the command line, allowing the possibility of upgrading hordes of LSWS installations with a single command.

The lsup command is located at $SERVER_ROOT/admin/misc/lsup.sh. In most CentOS installations, the command is thus:

/usr/local/lsws/admin/misc/lsup.sh

Running the basic lsup command will automatically upgrade your installation of LiteSpeed Web Server to the latest release. There are also options for customizing the command listed below.

• -f: If you already have the version to be installed, the basic lsup command will abort. The -f option forces lsup to install even if the version you have is the same version as the LSWS to be installed. This can be useful if there has been a change in the build since you upgraded, but a new build has not yet been released.
• -v: You can control what version you install with the -v option followed by a version number. (For example: ./lsup.sh -v 4.2.2) This will allow you to downgrade to older versions if you run into a bug. Keep in mind, LiteSpeed only keeps the most recent few versions available. Much older versions are not available.
• -b: Designates a build number. All versions start from build 0. To view what build you are currently using, view /usr/local/lsws/autoupdate/build. Will automatically upgrade to the latest build of the designated version if -b is not set. (Only available for versions 5.0 and higher.)

NOTE: for -v and -b, you can get a version number here if you need one.

Force an update to version 5.2.4:

/usr/local/lsws/admin/misc/lsup.sh -f -v 5.2.4

Force an update to version 5.2.5 build 4:

/usr/local/lsws/admin/misc/lsup.sh -f -v 5.2.5 -b 4

Starting from LSWS 5.3.7 build 4, LiteSpeed web server introduces new stable tier and edge tier to meet your auto upgrade requirement through lsup.sh script. It will make your server more stable during the upgrade while still keep edge user in mind.

• Basically /usr/local/lsws/autoupdate/follow_stable marker will be set automatically as far as you upgrade to 5.3.7 build 4 or later version.
• If you want to setup cron job, please ensure lsup.sh without parameter is used instead of lsup.sh -f.
• lsup.sh without parameter will follow stable tier if follow_stable marker is set and stable tier number is controlled.
• lsup.sh -f will install the edge build, which is the latest build available. and it will stop following stable tier by removing the follow_stable marker.
• If a version is forced, such as lsup.sh -f -v <version>, “lsup.sh” will stop follow stable and “lsup.sh” will do nothing.
• You can manually create follow_stable marker by running touch /usr/local/lsws/autoupdate/follow_stable, then it will start to follow stable tier again after the reset.
• Why follow_stable is important? When you try to install a test build/debug build, or downgrade to an older version, you certainly do not want lsup.sh in daily cron job to change it to stable tier automatically during the test. In these situations, unset follow_stable will make lsup.sh do noting in cron job.
• Please be aware that the new powerful stable/edge tier lsup.sh only available for 5.3.7 build 4 and later version. If you force downgrade to earlier version/build prior than that, it does not have above feature.