Last active
August 10, 2018 13:33
-
-
Save scardine/825c5ea4e11b01f868a07e22b3b759b6 to your computer and use it in GitHub Desktop.
Lets Encrypt Wildcard Certificate with DigitalOcean
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| $ echo dns_digitalocean_token = 89de1bae81accf27ebd8045136c09a2f > do-api.ini | |
| $ git clone https://github.com/certbot/certbot.git | |
| $ cd certbot | |
| $ ./certbot-auto --os-packages-only | |
| $ ./tools/venv.sh | |
| $ source venv/bin/activate | |
| $ certbot certonly --dns-digitalocean \ | |
| --dns-digitalocean-credentials do-api.ini \ | |
| --dns-digitalocean-propagation-seconds 60 \ | |
| -d '*.mywebsite.com' -d mywebsite.com \ | |
| --server https://acme-v02.api.letsencrypt.org/directory |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks, this code works, but I got the following message
Is there any risk of using this method compared to the manual method of adding txt to the challenges?
This method automatically renews the certificate and replaces it in the /etc/letsencrypt/live/mydomain.com/fullchain.pem project folder?