3 ms·
https://community.letsencrypt.org/t/acme-v2-production-environment-wildcards/55578 https://community.letsencrypt.org/t/acme-v2-production-envir... They do supp
by jasonjayr 8y ago
https://community.letsencrypt.org/t/acme-v2-production-environment-wildcards/55578 https://community.letsencrypt.org/t/acme-v2-production-envir...
They do support wildcard certs now.
- zie 8y agoThey do, and it's fabulous, but *.example.com certs from LE do not cover the root domain (example.com) so if you do a wildcard cert, you then must also do www.example.com. unless I'm missing something :)
- pseudalopex 8y agoYou can have example.com and *.example.com on the same certificate.
- jasonjayr 8y agoI didn't find docs specific to wildcard + non-wildcard, but LE certs can use multiple subject alternate names. So whatever tool you use, use SAN to request both *.example.com and example.com into one cert. I imagine you have to setup your stuff to respond to the DNS + web based challenge/response.
- NotANaN 8y ago.
- LinuxBender 8y agoYou can have multiple names in the cert, including the apex. Here is how I do it using acme.sh: acme.sh --issue --dns --force --yes-I-know-dns-manual-mode-enough-go-ahead-please -d "${domain}" -d "*.${domain}" > /dev/shm/.le."${domain}".txt