Find answers to your questions

Documentation

Check HTTPS and the LiteSpeed WebAdmin certificate

The LiteSpeed WebAdmin certificate protects the connection to the web server’s administration interface. Its configuration is separate from your website, cPanel and WHM. A website can therefore work over HTTPS while the console displays a warning, and installing a website certificate does not automatically correct the WebAdmin certificate.

This guide is for authorized server administrators. If Nuagerie manages your hosting, report the issue to our team before changing system configuration.

Confirm that WebAdmin access is intended

Use the address, port and access method provided by the administrator. A refused connection, timeout, HTTP 403 response and certificate error indicate different problems. Filtering, a required VPN or an intentionally inactive console may explain an unavailable interface.

The LiteSpeed changelog announces that WebAdmin is disabled by default in version 6.3.7, build 5, and version 6.4 RC2, build 3. Check the installed version and access policy before intervening. This information does not describe the configuration of any particular Nuagerie server. Do not reactivate the console or open its port simply to follow an older tutorial. Our LiteSpeed update guide explains the checks to plan after a version change.

Check certificate identity and trust

At the approved address, inspect the certificate details in your browser without bypassing the warning or entering credentials. Record the name you used, covered names, issuer and validity dates.

  • Covered name: the DNS name you use must match an identity in the certificate’s subjectAltName extension. Using an IP address instead may cause an error; that IP address must itself be covered for validation to succeed.
  • Validity: check for expiration, a future start date or an incorrect clock on the computer you are using.
  • Trust: the browser must be able to validate the chain to a trusted authority. A self-signed certificate is not automatically trusted. An internal authority requires controlled trust distribution to administrators’ devices.

A warning calls for investigation, not a permanent browser exception. Encryption alone does not confirm the server’s identity.

Prepare a change limited to administration

Keep a protected backup of the relevant configuration and an independent recovery access method. Identify who manages the certificate and arrange a maintenance window. The administrator can then follow the admin SSL listener reference for the installed version:

  1. Select the administration listener, often named adminListener, without accidentally changing a website listener.
  2. Check its secure mode, the certificate and private key pairing, and the required intermediate chain. The Private Key File, Certificate File and Chained Certificate fields must match the files and format actually supplied.
  3. Check paths, ownership and the service’s required permissions. Keep the private key outside the public directory and never attach it to an ordinary support ticket.
  4. Apply the change using the vendor’s procedure, with a recovery plan if access fails. Restoring service should not broaden authorized access.

Afterward, check the certificate actually served through the usual administration access method, authentication and website operation. The LiteSpeed console security reference also describes its access controls.

Plan renewal and deployment

A renewed certificate on disk only helps if WebAdmin subsequently uses it. Check the renewal mechanism, destination, retained permissions and required reload. A manually copied certificate may remain outdated. If you use Certbot, its renewal documentation distinguishes certificate issuance from deployment actions. Then confirm the new expiry date on the actual connection and arrange failure alerts.

Have Nuagerie review the situation

Through your client area, provide the affected service, administration address, exact message, time and recent changes. Remove passwords, private keys and sensitive information from screenshots. We can identify the affected component and clarify the intervention appropriate for your service. For an administration or security project, describe your needs through our contact form.

Related Articles

An LC.8 Error Appeared If you see an LC.8 error appear while using LiteSpeed, then the IP you have been assigned has been placed on the blacklist due to having a nulled version of LiteSpeed installed. Nulled software is illegal and unsafe and will show up on most search engines. When an IP is found to have a nulled version of LiteSpeed,... How to Change the License Key LiteSpeed makes it very easy to change your license key. Simply type the following into the command terminal: cd /usr/local/lsws/conf mv serial.no serial.no.old mv license.key license.key.old echo "" > serial.no cd ../bin ./lshttpd -r ./lswsctrl restart For help with a Nuagerie service, open or follow up on a... How to Check Your License If you want to check your LiteSpeed license, simply log into the LiteSpeed Web console then go to Actions -> Version Management You should see a section with the following information: Type Serial Expiration Date Software Update UltraVPS serial-key Jun 08, 2018 Jun 08, 2018 For help with a Nuagerie service, open or... Prepare a LiteSpeed installation or migration Replacing a web server affects the sites that depend on it. The procedure must suit your control panel, operating system and selected LiteSpeed edition. Check the environmentIdentify the current web server, panel and supported versions.Confirm the license and integration method available for that... How to swap LiteSpeed to Apache If for whatever reason, you want to change your Web server, simply type in the following command into your terminal. Please make sure to have Apache installed beforehand. LiteSpeed --> Apache service lsws stop service httpd start Apache --> LiteSpeed service httpd stop service lsws start For help with a Nuagerie...