Installation for NGINX:

Install the required packages:

# yum update && yum install certbot python3-certbot-nginx

For versions earlier than CentOS 7, the package is python-certbot-nginx.

Installation for Apache:

Install the required packages:

# yum update && yum install certbot python3-certbot-apache

For versions earlier than CentOS 7, the package is python-certbot-apache.

Installation for LiteSpeed:

LiteSpeed does not have an official package for automatic configuration. You therefore only need to install the Certbot package:

# yum update && yum install certbot

If you do not already have snapd installed, you can run the following on GNU/Linux:

# apt update && apt install snapd && snap install core; snap refresh core

For CentOS, replace apt with yum and enable it as follows:

 # yum update && yum install snapd && systemctl enable --now snapd.socket && snap install core; snap refresh core 

Install Certbot with snap:

# snap install --classic certbot

Verify the installation of the symbolic link:

# ln -s /snap/bin/certbot /usr/bin/certbot

Automatic configuration (recommended):

Obtain a certificate and automatically modify the Apache configuration:

# certbot --apache -d example.com -d www.ejemplo.com

Confirm that automatic configuration was successful by accessing your domain over HTTPS in a browser and checking that the certificate appears.

You can also use SSL Checker or an SSL Server Test to verify the Let's Encrypt certificate.

Manual configuration:

Obtain a certificate only (without modifying the Apache configuration):

# certbot certonly --apache -d example.com -d www.ejemplo.com

Example Apache configuration file for HTTPS:

<IfModule mod_ssl.c>
  <VirtualHost *:443>
  # The ServerName directive sets the request scheme, hostname and port that
  # the server uses to identify itself. This is used when creating
  # redirection URLs. In the context of virtual hosts, the ServerName
  # specifies what hostname must appear in the request's Host: header to
  # match this virtual host. For the default virtual host (this file) this
  # value is not decisive as it is used as a last resort host regardless.
  # However, you must set it for any further virtual host explicitly.
  #ServerName www.example.com

  ServerAdmin webmaster@localhost
  DocumentRoot /var/www/html

  # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
  # error, crit, alert, emerg.
  # It is also possible to configure the loglevel for particular
  # modules, e.g.
  #LogLevel info ssl:warn

  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined

  # For most configuration files from conf-available/, which are
  # enabled or disabled at a global level, it is possible to
  # include a line for only one particular virtual host. For example the
  # following line enables the CGI configuration for this host only
  # after it has been globally disabled with "a2disconf".
  #Include conf-available/serve-cgi-bin.conf

  ServerName ejemplo.com

  SSLCertificateFile /etc/letsencrypt/live/ejemplo.com/fullchain.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/ejemplo.com/privkey.pem
  Include /etc/letsencrypt/options-ssl-apache.conf
  </VirtualHost>
</IfModule>

Example HTTP to HTTPS redirect for an Apache site configuration:

<VirtualHost *:80>
  ServerAdmin webmaster@localhost
  DocumentRoot /var/www/html

  ErrorLog ${APACHE_LOG_DIR}/error.log
  CustomLog ${APACHE_LOG_DIR}/access.log combined

  RewriteEngine on
  RewriteCond %{SERVER_NAME} =ejemplo.com
  RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

As mentioned in the installation section, Certbot does not provide an official package for automatic LiteSpeed configuration. You must configure it manually by obtaining a certificate using the webroot option for validation through an ACME file:

# certbot certonly --webroot -w /usr/local/lsws/ejemplo.com/html/ -d example.com -d www.ejemplo.com

Configuration through LiteSpeed Webadmin

Once this is done, specify the certificate locations for the domain in question in the configuration. If you have access to Webadmin, you can do this in the SSL section of the corresponding virtualhost for that domain:

Also remember to enable the Listener on port 443 if it is not already enabled, map the domain and mark the connection as secure:

In the SSL section, add a certificate to configure SSL and support the required protocols, as shown in the following screenshots:

Then configure the certificate in Virtual Hosts:

You can also enable and create a rule for redirection:

Redirection rule:

 rewriteCond %{HTTPS} !on
  rewriteCond %{HTTP:X-Forwarded-Proto} !https
  rewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [R,L]

Manual LiteSpeed configuration

If you are not using CyberPanel, edit the web service configuration file to create or modify the Listener:

# vi /usr/local/lsws/conf/httpd_config.conf

An example of adding or modifying the Listener and specifying a certificate location with vhost mapping:

 listener HTTPS {
     address           *:443
     secure            1
     keyFile           /etc/letsencrypt/live/ejemplo.com/privkey.pem
     certFile          /etc/letsencrypt/live/ejemplo.com/fullchain.pem
     certChain         1
     sslProtocol       31
     map               ejemplo ejemplo.com
     map               ejemplo2 ejemplo2.com
  }

You must then also modify the configuration of the vhost or vhosts (after creating the mapped listener):

# vi /usr/local/lsws/conf/vhosts/ejemplo.com/vhconf.conf

An example vhost configuration file with HTTP to HTTPS redirection:

docRoot $VH_ROOT/html/
rewrite {
  enable                 1
  autoLoadHtaccess       1
  rules                  <<<END_rules
  rewriteCond %{HTTPS} !on
  rewriteCond %{HTTP:X-Forwarded-Proto} !https
  rewriteRule ^(.*)$ https://%{SERVER_NAME}%{REQUEST_URI} [R,L]
  END_rules
}
vhssl {
  keyFile                 /etc/letsencrypt/live/ejemplo.com/privkey.pem
  certFile                /etc/letsencrypt/live/ejemplo.com/fullchain.pem
}