Question

Tutorial for let's encrypt wildcard?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Afaik the certbot-client doesn’t yet support automatic challenges with the dns-digitalocean authenticator. However, the certbot docker container does.

sudo docker run -it --rm --name certbot \
    -v "/etc/letsencrypt:/etc/letsencrypt" \
    "/var/lib/letsencrypt:/var/lib/letsencrypt" -v "<path-to-output-directory>:/keys" \
    certbot/dns-digitalocean certonly --server https://acme-v02.api.letsencrypt.org/directory \
    --dns-digitalocean --dns-digitalocean-credentials <path-to-DO-conf.ini> "*.yourdomain.tld"

This worked for me: https://blogs.msdn.microsoft.com/mihansen/2018/03/15/creating-wildcard-ssl-certificates-with-lets-encrypt/

Pretty simple actually.

sudo certbot certonly --server https://acme-v02.api.letsencrypt.org/directory --manual --preferred-challenges dns -d *.<your.domain>

We’ll definitely be covering that topic! Quite a few of us here at DO were very excited to see this release. We’re looking into it now, but we’ll likely not provide a new tutorial until the new certbot version is available in the official PPA. See this convo on the Let’s Encrypt forum for more details: