Use this extension with nginx about certbot_dns_duckdns HOT 3 CLOSED

I need more information which exact command and which versions of the plugin and certbot you used. Please fill out the issue template.

from certbot_dns_duckdns.

I found the right way to do it, I created the certificate with my duckdns token and then added it manually to my nginx config.
I just wonder why it is impossible to use the 2 flags --nginx and --authenticator dns-duckdns

The command I used was:

certbot certonly \
  --non-interactive \
  --agree-tos \
  --preferred-challenges dns \
  --authenticator dns-duckdns \
  --duck-dns-token $my_token
  -d "rambi.duckdns.org"

And I don't think this is specific to my version (I installed the latest version of certbot and certbot_dns_duckdns with pip)

from certbot_dns_duckdns.

If you use the argument --nginx and --authenticator dns-duckdns, then you say certbot it should create a HTTP-01 challenge with nginx and a DNS-01 challenge with duckdns at the same time. This is logically not possible, because both are mutually exclusive. You can find more information about the different challenge types on the letsencrypt page.

From the official docs:

--nginx           Use the Nginx plugin for authentication & installation

And for authenticator plugins:

-a AUTHENTICATOR, --authenticator AUTHENTICATOR
                        Authenticator plugin name.

You can not combine multiple authenticators. You can combine only installer and authenticator, this is it also described here

For more information about certbot please refer to the official documentation.
If you need support for using certbot and this is not related to this DNS plugin, then use the official certbot help channels.

I will close the ticket as this is not a feature idea, an issue or related to this specific DNS plugin and relates only to the general use of certbot.

If you find a bug in certbot_dns_duckdns or have a feature idea then feel free to open a new issue and fill out the templates.

from certbot_dns_duckdns.