Set up Let’s Encrypt with multiple domains

Oh, wow, finally it worked:

true | openssl s_client -connect www.starzen.space:443 2>/dev/null \
| openssl x509 -noout -text \
| perl -l -0777 -ne '@names=/\bDNS:([^\s,]+)/g; print join("\n", sort @names);'
starzen.space
www.starzen.space

I commented out the if statements in the letsencrypt script to force a re-issue. This is not a ‘factory’ solution, though, of course.

However, it suggests there was an issue with ‘state’ rather than the options supplied.

Looks like the current script can get tripped up depending on prior state but if you force a reissue you can fix it.

But now I have a working apex domain! :tada:

2 Likes

It is part of the standard install. See User Guide — Certbot 1.30.0 documentation and scroll down to Managing Certificates and also immediately below that, Re-creating and Updating Existing Certificates.

These commands would be run from where you ran Certbot to begin with.

1 Like

I have a standard install and certbot is not in use. Not on ”normal” server-lever, neither if I say first ./launcher enter app.

I reckon it is missing because of acme.sh.

3 Likes