Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA

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. https://crt.sh/?q=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: familie-sossna.de

I ran this command: sudo certbot --authenticator standalone -v --installer nginx -d *.familie-sossna.de --pre-hook "service nginx stop" --post-hook "service nginx start"

It produced this output: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA

My web server is (include version): nginx

The operating system my web server runs on is (include version): Ubuntu on raspbery pi

My hosting provider, if applicable, is: domainfactory

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):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

2

wildcard certificates require DNS-01 challenge. what you'd actually want?

4 Likes
3

Yes, you requested a wildcard certificate which requires a DNS Challenge. Yet, you chose the standalone authenticator which only supports an HTTP Challenge.

See: Challenge Types - Let's Encrypt

If you don't need a wildcard just use specific domain names. You use multiple -d values to have more than one name in the cert.

5 Likes
4

And:

Getting certificates (and choosing plugins)

For a table of which Certbot plugin supports which challenge.

2 Likes