Integration with Let’s Encrypt
Let’s Encrypt is a free certification authority that provides free X.509 certificated for TLS encryption. An automated process enables to facilitate the creation, verification, setup, and renewal of SSL certificates for protected websites.
The official website. Working with Let's Encrypt certificates is possible immediately after installing the control panel.
Please pay attention, Let’s Encrypt has a number of limits (for more details, check additional limits):
You can order only 50 certificates per week (TLD, including its subdomains);
Let’s Encrypt certificate validity period is 3 months (every 3 months ispmanager will reissue Let’s Encrypt certificates);
All alternative names should be subdomains of the certificate domain.
In ispmanager, you can get a valid self-renewing SSL certificate for your domain.
To do this, you will need a user who has the right to use SSL, and a valid domain name available to the world DNS.
There are two buttons in SSL-certificates — Let's Encrypt and Let’s Encrypt Log. Clicking the first button will start the process of the certificate issue.
The second function will be activated if you already have the Let's Encrypt certificate in the list of SSL-certificates, and will redirect you to the Event log.
Before generating a certificate, make sure that the Let's Encrypt function is enabled:
In the Main menu choose Users.
In the form that opens, select the user and click on the Perm. button.
Choose SSL-certificates in the form that opens and click Functions.
In the form that opens, choose Let’s Encrypt and Let’s Encrypt log and click Enable.
Add a certificate
There are two ways to obtain a Let's Encrypt certificate:
Navigate to SSL-certificates. Click the Let's Encrypt button, and fill out the form.
When creating a new domain, Let's Encrypt form will be opened after you press Create. Specify the required parameters and click Issue.
Every day at 1:30 a.m server time, the system checks which certificates need to be updated.
The certificate will be reissued according to the set value of the LetsencryptStartUpdatePeriod parameter (default value is 29 days).
Recommended values are from 7 to 29. It is not recommended to specify values less than 7 and more than 29, as well as negative values and letters.
Manual certificate update
You can also start the update process manually with the letsencrypt.check.update function. Call the function via the mgrctl utility with the following parameters:
/usr/local/mgr5/sbin/mgrctl -m ispmgr letsencrypt.check.update force_update=yes cert_name=%cert name% user_name=%user name%
The number of certificates that can be issued for a domain is limited, that's why, do not update your certificates manually too often.
When updating the certificate with DNS-verification, new TXT-records will be generated. If the external DNS-server is used, the records won't be added automatically, and the certificate won't be updated.
Certificate issue procedure
First, a self-signed certificate with the specified parameters is created, then, once in a minute, an attempt is made to obtain a certificate. You can set the maximum number of certificate requests that the control panel will send simultaneously. To do this, change the LetsencryptProcessCount parameter in the ispmanager configuration file. The default value for this parameter is 1.
If errors occur, they are logged. Retrying to receive is performed every minute. Requests for new certificates take precedence over retrying old ones.
You can start the letsencrypt.periodic command via the mgrctl utility.
If the certificate cannot be obtained within 24 hours, the corresponding notification will be created for the user and administrators. No more attempts will be made.
If the certificate is issued successfully, the self-signed certificate is changed into Let's Encrypt. The user and administrators receive the notification that the certificate has been issued.
Order of requests:
Request for domain ownership (in order to verify domain ownership, a new token is added. This is a file with data that were received after authentication. The global alias .well-known/acme-challenge/ on the server leads to the directory /usr/local/mgr5/www/letsencrypt. All verification tokens will be created there.
Waiting for successful validation
Let's Encrypt supports DNS-based validation that requires specific TXT-records to be inserted into the DNS zone for a domain. Select the DNS validation checkbox when you order a new SSL-certificate.
The necessary TXT-records will be automatically added to Manage DNS records form. To view:
In the Main menu, choose Domain names (DNS).
In the form that opens, choose your domain and click Manage DNS records.
If you use an external DNS server, the process will be suspended for 30 minutes. In the left corner of the panel interface next to the global search field and in the Notifications section (in Monitoring and logs), you will see a notification saying what records you should add to the external server to receive the certificates.
The system will check the records on the Internet every 30 minutes during 24 hours after you have received the first notification. When the required records are available, the certificates will be issued.
If domain validation processes cannot be completed successfully for 24 hours since you ordered a certificate, the system will stop trying to issue the certificate.
To get a certificate for a mail domain, when creating/editing a mail domain, select Secure connection(SSL) - New Let's Encrypt certificate.
Next, enter the aliases that the selected domain uses for mail operation (pop.your_domain.com, mail.your_domain.com, smtp.your_domain.com or others).
If the web-domain with the same name is not created in the control panel, the verification procedure will be run via DNS.
Ispmanager supports Wildcard SSL certificates. To receive a Wildcard SSL-certificate, check the Wildcard box on the order form.
The domain verification procedure for wildcard-certificates is performed only via DNS.
An alias such as *.domain.name specified manually will be ignored during the order to avoid verification conflicts.
Sometimes it may happen that a web-domain is resolved to several cluster nodes. If one of the cluster nodes doesn't have a web-role, it cannot pass the HTTP verification. How to solve the issue:
Use DNS verification.
Just wait. After several failures, the ACME server will find the right address for the HTTP verification.
The log file of ispmanager and Let’s Encrypt interaction is located in /usr/local/mgr5/var/letsencrypt.log.
The default logging level is not enough for receiving all the information an administrator may need to solve possible issues. Complete the following steps:
In the Main menu, choose Monitoring and logs -Logging settings.
Select sslcert, rpc, and core modules.
Click on Maximum.