The plugin is distributed in RPM form as part of a yum repository for CentOS 6 and 7. If you previously used a .tar.gz to install, please just upgrade using the below instructions.
- Root SSH access to WHM
- i386 or x86_64 CentOS 6 or 7 (5 is not supported)
- WHM 11.56 or higher (CloudLinux and LSWS compatible)
- Remote access key has been generated (
/root/.accesshash). If it is not present, simply visit the “Remote Access Key” page in WHM.
- Please note that after cPanel version 66 this step is not required, the plugin will generate it’s own API Token instead.
- Please note: cPanel DNSONLY servers are currently NOT supported, please use our FleetSSL DNSONLY package instead.
Install the licence file
Save your issued licence file as
/etc/letsencrypt-cpanel.licence and chmod to 0400. If you received a file ending in
.json just rename the file to
Trial users may ignore this step, as a trial licence will be downloaded automatically for you.
If you are upgrading from a trial licence to a paid licence, save/overwrite the issued licence file as above. After installing a new licence file, you will need to restart the background service with the following command,
service letsencrypt-cpanel restart
Add the letsencrypt package repository:
wget https://cpanel.fleetssl.com/static/letsencrypt.repo -O /etc/yum.repos.d/letsencrypt.repo
Next, install the plugin through yum via
yum -y install letsencrypt-cpanel
The repository will install the plugin to the system - this might take a minute.
If there are no problems, you should be able to run a successful self-test immediately afterwards:
[root@~]$ le-cp self-test [SELF-TEST] Can read config ............ SUCCESS. [SELF-TEST] Can connect to daemon and check licence ............ SUCCESS. [SELF-TEST] Can connect to Lets Encrypt ............ SUCCESS. [SELF-TEST] Can talk to WHM API ............ SUCCESS. [SELF-TEST] Can talk to plugin RPC ............ SUCCESS.
Testing the installation
Now that the installation is complete, you should be able to login to any cPanel server on that server, and see the “Let’s Encrypt™ SSL” icon on the home screen.
You should be able to immediately issue certificates, provided that the domain actually points to the server.