You will see that Let’s Encrypt API is set on staging* (test) by default, set it to production.

• Get your admin* username, password & hostname
• Select your panel type in the list

• Fill-in the required information

Host must be in the form:

• Plesk: https://mydomain.com:8443/
• cPanel: https://mydomain.com:2083/
• VestaCP: https://mydomain.com:8083/
• DirectAdmin: ssl://mydomain.com:2222/

Note: For VestaCP there are two options, VestaCP web API and VestaCP exec API.

For VestaCP exec API you have to enter only the username and web space (usually your Siberian domain name):

• If your webspace name created on your hosting panel, doesn’t match your domain name, then specify it in the field “Web space“. For example, you created a webspace called “siberian”, but your domain name is myapps.domain.com, then you will have to enter “siberian” in the field “Web space“.
• Then 
• Wait for the page to reload, and click on 

Note: Do NOT refresh or quit the page until it’s done.

• If the request is successful you should now see your certificate in the “Issued certificates” below

• It’s done ! Siberian pushed your certificate to your hosting panel and will check periodically with the cron scheduler if your certificates need to be renewed.
  • For the Platform Edition, every-time a new White Label domain is setup, the certificate will be updated to match with the new domain.

*note: the admin account is generally required in order to use the API.

For cPanel users it happens sometimes that the certificate is renewed but not uploaded in the panel. You have to perform a manual action:

• download your renewed certificates by clicking on them:
  
• Open them in a text editor (not Word, preferably)
• Then, enter in your cPanel
• Search for SSL and enter in this SSL section
  
• Click on “Manage SSL sites”
• Select your domain
• Copy and paste your certificates in the appropriate sections:
  • The cert.pem in the “Certificate” field
  • The privkey.pem in the “Private Key” field
  • The fullchain.pem in the “Certificate Authority Bundle” field
• Click on “Install certificate” and you’re done.

• First select “Unknown – Self-managed”

• Then 
• Wait for the page to reload, and click on 
• If the request is successful you should now see your certificate in the “Issued certificates” below. Click on  to check the paths:

• Setup your web-server with your new certificates, some examples below:
  • Nginx: In your virtual host add the following lines

    [...]
    listen 443;
    
    ssl on;
    ssl_certificate /path/to/your/certificate/cert.pem;
    ssl_certificate_key /path/to/your/certificate/private.pem;
    [...]

    Apache: In your virtual host add the following lines

    [...]
    <VirtualHost *:443>
    
    SSLEngine on
    SSLCertificateFile /path/to/your/certificate/cert.pem
    SSLCertificateKeyFile /path/to/your/certificate/private.pem
    SSLCertificateChainFile /path/to/your/certificate/chain.pem
    [...]

• [Recommended] Next you will have to setup a root incron job , which will watch the certificate file “/path/to/your/certificate/cert.pem” changes to call your server to reload.
  1. For Debian, Ubuntu, etc…
     1. apt-get install incron
  2. For Fedora, Red Hat, CentOS, etc…
     1. yum install incron
  3. Setup your job “incrontab -u root -e” add the following line /path/to/your/certificate/cert.pem IN_MODIFY /usr/bin/reload-web-server.sh
     1. Example script for /usr/bin/reload-web-server.sh

        • #!/bin/bash
          service httpd reload

     2. Don’t forget to chmod +x /usr/bin/reload-web-server.sh the script
  4. Start the service “service incrond start” or “/etc/init.d/incrond start”
     
  5. Now each time your certificate is renewed or modified (cf: new domains registered) your web-server will be reloaded to serve the new file.

Thus it’s not a recommended way to setup your Siberian SSL, you can setup your existing certificates by giving Siberian their path or by uploading them.

• For the Platform Edition, every-time a new White Label domain is setup, you will have to renew your certificate by adding the new domains to the Subject Alternative Names of your certificate, otherwise your whitelabels won’t work with HTTPS.

1. First you need to expand the upload section by clicking on the title or “+”
   • 
2. You’ll then have access to this new form.
   • 
     We highly recommend to provide existing paths to your certificates rather than uploading them manually, if you want to upload certificates jump to the next section #upload-my-certificates.You will have to fill in the main domain name in “hostname” and provide your certificates path.The certificates path must be the same already setup in your server virtual host, this way Siberian always have the latest certificate.
3. Now click on upload and you’re done.

Upload my certificates

1. Below you can see the upload form
   • 
     In this form you also have to fill in the main domain name in “hostname”, but this time you have to upload your existing certificates files.
2. You can now click on upload and you’re done.

Note: when uploading certificates rather than giving Siberian the path, you will have to upload them again each time they are renewed