Articles

How to Use AutoSSL

With AutoSSL, ServerPilot can automatically issue, deploy, and renew SSL certificates for your apps. We're proud to have made ServerPilot's AutoSSL the industry standard for painless deployment of free SSL certificates. ServerPilot's AutoSSL became so quickly well-known and in such demand that other control panels adopted the same feature name in their attempts to make an SSL deployment feature.

AutoSSL certificates are fully trusted by browsers just as certificates you purchase from a certificate authority (CA). There's no need for you to generate a certificate signing request (CSR), pay a CA for each certificate, or worry about renewing certificates when they expire.

There is no limit to the number of apps or domains you can have secured with AutoSSL.

AutoSSL is a feature of ServerPilot's Coach and Business plans.

Enabling AutoSSL

Before AutoSSL will be available for an app, you must first add the app's domains in ServerPilot.

Once you've added your app's domains, you'll have an AutoSSL option available in your app's SSL tab.

When you click on Enable AutoSSL, ServerPilot will enable SSL for your app using an AutoSSL certificate. This certificate will be automatically renewed by ServerPilot before it expires.

AutoSSL is only available if you have not deployed your own SSL certificate to your app. If you have already deployed your own SSL certificate, you must delete that certificate before you can enable AutoSSL.

Requirements

ServerPilot can issue AutoSSL certificates for apps that meet the following requirements of our certificate provider, Let's Encrypt:

  1. DNS for your domains must resolve to your server or, if you use a CDN like CloudFlare, the CDN must be configured to proxy requests to your server.
  2. Your domains cannot be internationalized domain names (IDNs). AutoSSL certificates can now include IDNs as Let's Encrypt began supporting IDNs in October 2016.
  3. Your domains cannot be wildcard domains.

If any of your apps' domains are not available for AutoSSL, you will see the reason why in the app's SSL tab.


Last updated: December 12, 2016