Deploying LiteSpeed cPanel through the Linode Marketplace
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
The LiteSpeed cPanel App automatically installs WHM/cPanel, performance LiteSpeed Web Server, and WHM LiteSpeed Plugin.
LiteSpeed Web Server Features: HTTP/2, QUIC, HTTP/3, event driven architecture, Apache drop-in replacement, LSCache Engine with ESI, server-level reCAPTCHA, one-click cache acceleration
WHM LiteSpeed Plugin Features: Version management, one-click switch between Apache and LiteSpeed Web Server, build PHP with LSAPI, quick PHP suExec and LiteSpeed cache setups, license management
Auto configuration: Enable PHP_SUEXEC, enable EasyApache integration, switch to LiteSpeed Web Server, cache root setup, disable Apache mod_ruid2, Apache port offset 0
Deploying the LiteSpeed cPanel Marketplace App
The Linode Marketplace allows you to easily deploy software on a Linode using the Linode Cloud Manager.
Log in to the Cloud Manager and select the Marketplace link from the left navigation menu. This displays the Linode Compute Create page with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy.
Fill out all required Options for the selected app as well as any desired Advanced Options (which are optional). See the Configuration Options section for details.
Complete the rest of the form as discussed within the Getting Started > Create a Linode.
Click the Create Linode button. Once the Linode has provisioned and has fully powered on, wait for the software installation to complete. If the Linode is powered off or restarted before this time, the software installation will likely fail. To determine if the installation has completed, open the Linode’s Lish console and wait for the system login prompt to appear.
Follow the instructions within the Getting Started After Deployment section.
Software installation should complete within 10-15 minutes after the Linode has finished provisioning.
For advice on filling out the remaining options on the Create a Linode form, see Getting Started > Create a Linode. That said, some options may be limited or recommended based on this Marketplace App:
- Supported distributions: CentOS 7, CentOS 8, AlmaLinux 8
- Recommended plan: All plan types and sizes can be used.
Getting Started after Deployment
Accessing the LiteSpeed cPanel App
Open a browser and navigate to port
2087on your IP address. This should look like
192.0.2.0with your Compute Instance’s IP address.
The WHM login page appears. Enter
rootas the username and the root password you created when deploying your app. Click the Log In button.
You are presented with cPanel and WHM’s terms. Read through the terms and click on Agree to All if you agree and would like to continue.
In the next screen, enter in an email address to receive status and error notifications.
You are also prompted to provide nameserver’s for your cPanel instance. By default, cPanel will fill in the values for you. Update the values with the nameservers you would like to use. If you are managing your own nameservers, enter them into the form or, if you will be using Linode’s DNS manager, enter in Linode’s nameservers into the form. Click Finish to complete the initial login process.
Linode’s nameservers are the following:
ns1.linode.com. ns2.linode.com. ns3.linode.com. ns4.linode.com. ns5.linode.com.
See our How do I set up DNS on cPanel? community question and answer for details related to cPanel and Linode nameservers.
You are then brought to your WHM’s home page where you can continue to configure your cPanel instance.
Now that you’ve accessed your LiteSpeed instance, check out the official LiteSpeed documentation to learn how to further utilize your LiteSpeed instance.
NoteCurrently, Linode does not manage software and systems updates for Marketplace Apps. It is up to the user to perform routine maintenance on software deployed in this fashion.
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on