Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: example.com
I ran this command: certbot renew --dry-run
It produced this output:Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. You may need to use an authenticator plugin that can do challenges over DNS.
My web server is (include version): Apache/2.4.38 (Debian)
The operating system my web server runs on is (include version): Debian 10
My hosting provider, if applicable, is: ME
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):certbot --version: certbot 0.31.0
I have setup and been down the rabbit hole. I maintain my own bind DNS server (using Xen VM's). I can't finds any docs that help to setup automagic cert renewel (I do comment out TXT record for letsencrypt). Maybe I've just read too much and making this harder than it needs to be.
Basic Debian stuff, create certs, configure https w/wildcard cert (example.com,*.example.com, re-direct all requests to https, no directory listing, renew when due (at the 60 day mark????) without having to monkey w/DNS, or anything for that matter.
How hard can this be with such a simple setup? 10,000ft view is fine, I've been around the block, just want out of this hole ;~)>
AUTOMATION HELP PLEASE.