[Bug]: no DuckDNS token

[thestoreisinsured]

OS info

Windows 10, latest

Docker image

• I am using the docker image.

certbot_dns_duckdns version

v1.8.0

certbot version

5.5.0

Bug description

Every time I attempted to apply an SSL certificate, it told me that no DuckDNS token was found despite multiple attempts at supplying the token.

Expected behaviour description

it should give the SSL certificate

Relevant log output

Command

--dns-duckdns-token <your-duckdns-token>

--dns-duckdns-credentials </path/to/your/duckdns.ini>

certbot certonly \
  --non-interactive \
  --agree-tos \
  --email <your-email> \
  --preferred-challenges dns \
  --authenticator dns-duckdns \
  --dns-duckdns-token <your-duckdns-token> \
  --dns-duckdns-propagation-seconds 60 \
  -d "example.duckdns.org"

certbot certonly \
  --non-interactive \
  --agree-tos \
  --email <your-email> \
  --preferred-challenges dns \
  --authenticator dns-duckdns \
  --dns-duckdns-token <your-duckdns-token> \
  --dns-duckdns-propagation-seconds 60 \
  -d "*.example.duckdns.org"

DNS records

Steps to reproduce

dont have the plugin get the token

Additional context

No response

Checklist

• I have checked for existing Github issues for the same bug.
• I have checked to see if there is a newer version that already fixes this error.

[infinityofspace]

Thanks for the bug report. Unfortunately, I can’t reproduce your issue.
Could you try providing the token not as a CLI argument, but via an environment variable or a credentials file? You can find the docs here.

To investigate the issue more closely, could you please provide the exact command and the order of the arguments? Of course, replace the token and domain with dummy values. Your current information about the commands only shows the use of the token as an argument, if I understood correctly.