I ran this command: docker run -t --rm certbot/certbot certonly --manual --manual-auth-hook /etc/letsencrypt/acme-dns-auth.py --preferred-challenges dns --debug-challenges -d \*.ssl-test.lukavalabs.com -d ssl-test.lukavalabs.com
*note: I left out volume bindings
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for *.ssl-test.lukavalabs.com and ssl-test.lukavalabs.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Challenges loaded. Press continue to submit to CA. Pass "-v" for more info about
challenges.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press Enter to Continue
My web server is (include version): NA
The operating system my web server runs on is (include version): Amazon Linux 2
My hosting provider, if applicable, is: AWS
I can login to a root shell on my machine (yes or no, or I don't know): Yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 1.22.0
So I can request renewal certificates and that's fine, they'll renew. However when I try to issue/request new certificates like one listed in the command above, I see the above report output and after pressing Enter nothing happens, it just sits there. I'm completely stumped. I've requested certs on this server before, but it's been a while and now that I need a new one I'm a bit stuck.
@rg305 I'm not sure I follow your question about new wildcard certs. As far as I know they were introduced while back and haven't changed. Anyhow, I'm requesting a certificate that covers the domain ssl-test.lukavalabs.com and all of it's subdomains. Thus the -d ssl-test.lukavalabs.com and -d *.ssl-test.lukavalabs.com
I'm not sure how it worked previously, but it works now. I needed to change the docker argument from -t to -it. The i means interactive, which in this case I'm assuming means it can respond when I press Enter. Duh. I'm still baffled that worked previously though, maybe there wasn't the interactive prompt in old version? Anyhow, the full working command is below if others need the solution.
docker run -it --rm certbot/certbot certonly --manual --manual-auth-hook /etc/letsencrypt/acme-dns-auth.py --preferred-challenges dns --debug-challenges -d \*.ssl-test.lukavalabs.com -d ssl-test.lukavalabs.com