How To Create Let's Encrypt Wildcard Certificates with Certbot
A wildcard certificate is an SSL certificate that can secure any number of subdomains with a single certificate. You may want a wildcard certificate in cases where you need to support multiple subdomains but don’t want to configure them all individually.
Let’s Encrypt is an SSL certificate authority that grants free certificates using an automated API. In this tutorial you will create a Let’s Encrypt wildcard certificate by following these steps:
- Making sure you have your DNS set up correctly
- Installing the Certbot plugins needed to complete DNS-based challenges
- Authorizing Certbot to access to your DNS provider
- Fetching your certificates
This information is intended to be useful for any Linux distribution and any server software, but you may have to fill in some gaps with further documentation, which we will link to as we go.
This tutorial assumes you already have the following:
- The Certbot utility installed, version
0.22.0or later. If you need help installing Certbot, please visit our
Let's Encrypttag page, where you can find installation guides for a variety of Linux distributions and servers. Some common setups are listed below:
- A domain name, and a DNS provider that is supported by Certbot. See Certbot’s DNS plugin list for a list of supported providers
Let’s begin by setting up and testing our DNS records.
Step 1 — Setting up Wildcard DNS
Before we fetch our wildcard SSL certificate, we should make sure our server is responding to requests on multiple subdomains. This will typically be accomplished by setting up a wildcard DNS record, which looks similar to this:
*.example.com. 3600 IN A 203.0.113.1
* wildcard character is treated as a stand-in for any hostname. This example DNS record would match
two.example.com. It would not match the bare
example.com nor would it match
one.two.example.com because the
* wildcard will only expand to one hostname, not to multiple levels of names.
Additionally a wildcard DNS record can only have one wildcard character, so
*.*.example.com is not allowed.
Please refer to your DNS provider’s documentation to set up the correct DNS entries. You will want to add either an
CNAME wildcard record before proceeding.
Note: If you are using DigitalOcean to manage your DNS, please see How to Create, Edit, and Delete DNS Records in our product documentation for more information.
To test that your wildcard DNS is working as intended, use the
host command to query a few hostnames:
- host one.example.com
Be sure to substitute your own domain and hostname above. Also, remember that it sometimes takes a few minutes for DNS records to propagate through the system. If you just added your DNS record and are getting errors, wait a few minutes and try again.
When the hostname you entered resolves properly, you’ll output similar to the following:
Outputone.example.com has address 203.0.113.1
Otherwise, you’ll see an
OutputHost one.example.com not found: 3(NXDOMAIN)
Once you’ve verified that multiple subdomains are resolving to your server, you can continue on to the next step, where you’ll configure Certbot to connect to your DNS provider.
Step 2 — Installing the Correct Certbot DNS Plugin
Before issuing certificates, Let’s Encrypt performs a challenge to verify that you control the hosts you’re requesting certificates for. In the case of a wildcard certificate, we need to prove that we control the entire domain. We do this by responding to a DNS-based challenge, where Certbot answers the challenge by creating a special DNS record in the target domain. Let’s Encrypt’s servers then verify this record before issuing the certificate.
In order to connect to your DNS provider, Certbot needs a plugin. Please see Certbot’s DNS plugin list to get the name of the appropriate plugin for your DNS provider.
For instance, the DigitalOcean provider is called
certbot-dns-digitalocean. We can install the
certbot-dns-digitalocean plugin on Ubuntu and Debian by installing the following package:
- sudo apt install python3-certbot-dns-digitalocean
Other plugins should follow the same naming format. Swap your provider’s name into the command above if you’re using a different service.
On CentOS and other RPM-based distributions the installation command may be
- dnf install python3-certbot-dns-digitalocean
- yum install python3-certbot-dns-digitalocean
You also may need to install additional package repositories on these distributions to get access to the Certbot plugin packages.
To verify that the plugin was installed correctly, you can ask Certbot to list its current plugins:
- certbot plugins
Output- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - * dns-digitalocean Description: Obtain certs using a DNS TXT record (if you are using DigitalOcean for DNS). Interfaces: IAuthenticator, IPlugin Entry point: dns-digitalocean = certbot_dns_digitalocean.dns_digitalocean:Authenticator * standalone Description: Spin up a temporary webserver Interfaces: IAuthenticator, IPlugin Entry point: standalone = certbot.plugins.standalone:Authenticator * webroot Description: Place files in webroot directory Interfaces: IAuthenticator, IPlugin Entry point: webroot = certbot.plugins.webroot:Authenticator - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
In the above output, the
dns-digitalocean plugin is listed first, along with the default
When you have verified that the correct plugin is installed, continue on to the next step to configure it.
Step 3 — Configuring the Certbot Plugin
Because Certbot needs to connect to your DNS provider and create DNS records on your behalf, you’ll need to give it permission to do so. This involves getting an API token or other authentication information from your DNS provider, and putting it in a secure credentials file that Certbot will later read from.
Because each provider has a different authentication process, please refer to the documentation for your particular Certbot DNS plugin for more information on what tokens or keys you’ll need to obtain.
For this example, we will continue using the
dns-digitalocean plugin, and will store our credentials in the file
We will create this file using the
nano text editor:
- nano ~/certbot-creds.ini
This will open up a new blank text file. You’ll want to add your information based on the instructions for your particular DNS provider. DigitalOcean requires a single API token, so it will look like this:
dns_digitalocean_token = 235dea9d8856f5b0df87af5edc7b4491a92745ef617073f3ed8820b5a10c80d2
Be sure to replace the example token above with your own information.
Save and close the file. If you’re using
CTRL+O (for “write out”), hit
CTRL+X to exit.
After creating the file, you will need to restrict its permissions so that your secret is not leaked to other users. The following
chmod command will give read and write access to only your user:
- chmod 600 ~/certbot-creds.ini
Once you’ve set up your credentials file, you’re ready to actually request the certificate.
Step 4 — Retrieving the Certificate
At this point, retrieving your Let’s Encrypt wildcard certificate is similar to “normal” non-wildcard certificates. The main changes to the process are to specify the DNS-based challenge, and point to our DNS credentials file. Additionally we’ll use a wildcard domain with the
- sudo certbot certonly \
- --dns-digitalocean \
- --dns-digitalocean-credentials ~/certbot-creds.ini \
- -d '*.example.com'
Note that you cannot use the
--apache plugins to automatically configure those servers with a wildcard certificate. We use the
certonly command instead, to only download the certificate.
When running the above command, you may be presented with a few questions to answer if this is your first time running Certbot. After answering them, Cerbot will perform the challenge, the Let’s Encrypt servers will verify it, and your new certificate will be downloaded and saved to
/etc/letsencrypt/. You should see output similar to the following:
OutputIMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/example.com/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/example.com/privkey.pem Your cert will expire on 2021-09-27. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le
You have successfully generated a wildcard SSL certificate! Your next step is to configure your server application to use it. We’ll link to some resources that can help with this in the next section.
In this tutorial you configured Certbot and downloaded a wildcard SSL certificate from the Let’s Encrypt certificate authority. You are now ready to configure your server software to use this certificate to secure its connections.
For more information on what certificate files were downloaded, and how to handle gracefully restarting your applications when Certbot automatically updates your certificates, take a look at Steps 3 and 4 of our tutorial How To Use Certbot Standalone Mode to Retrieve Let’s Encrypt SSL Certificates on Ubuntu 18.04.