Cannot create certificate

[DoctorIGP]

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: liminalwanderings *.liminalwanderings.com

I ran this command: sudo certbot -v --apache

It prompted me to input my domain names, and the 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.
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.52

The operating system my web server runs on is (include version): Ubuntu 22.04 (LTS) x64

My hosting provider, if applicable, is: digitalocean

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 1.31.0

[Bruce5051]

Hello @DoctorIGP, welcome to the Let's Encrypt community.

@DoctorIGP

liminalwanderings.com

Here a list of issued certificates for the domain crt.sh | liminalwanderings.com, the latest being 2022-11-05.

It does not seem like the server for the domain is offering HTTPS or listening on Port 443.

Check report was removed: Check host - online website monitoring

[MikeMcQ]

@DoctorIGP

My domain is: liminalwanderings *.liminalwanderings.com

I ran this command: sudo certbot -v --apache

You have requested a wildcard but tried to use the --apache plug-in authenticator. A wildcard cert requires a DNS challenge but that plug-in only supports HTTP Challenge. See challenges doc here

DNS Challenges are often much harder to setup. If you don't need a wildcard you might try getting a cert with just explicit names. See the Certbot docs for DNS challenge options if you need a wildcard.