Can't renew without DNS

Help
1

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: https://cubistmediagroup.com

I ran this command: sudo certbot certonly -d $DOMAIN -d $WILDCARD --manual --preferred-challenges http-01

(DOMAIN=cubistmediagroup.com
WILDCARD=*.$DOMAIN)

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Cert is due for renewal, auto-renewing...
Renewing an existing certificate
Performing the following challenges:
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.
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): AWS Lightsail running Bitnami Wordpress with Apache

The operating system my web server runs on is (include version):
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster

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 can login to root shell

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 0.31.0

Basically I'm trying to renew, but the only option that gives me forward progress is sudo certbot certonly -d $DOMAIN -d $WILDCARD --manual which requires me to use DNS authentication.

This is work for a client that I'd rather not bother and do the authentication over HTTP by putting a file in the .well-known folder.

How can I use a plugin to renew over HTTP only?

2

If you want a wildcard certificate, you need to use DNS authentication. (Basically, just because you run a website doesn't mean you own all the subdomains of that website, whereas if you control DNS then you basically do.)

So your options are, (1) Don't get a wildcard and instead just get a certificate with the names you're actually using, or (2) Use DNS authentication.

Ideally, in either case you'd be automating it. More and more DNS providers offer an API which would allow for automated integration with certbot (or other clients), and if you don't you may be able to delegate it to some other system that does support an API.

See the challenge types documentation for more information:

3

You're using Bitnami. Please note that the Bitnami stack is very different from regular *Nix installations. I would not recommend using certbot for Bitnami stacks. Please see the following "sticky" thread from the Help section:

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.