Duckdns Unable to determine zone identifier for {0} using zone names: {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: thibleroy.duckdns.org

I ran this command: sudo docker run -it --rm --name certbot -v "/Users/thibleroy/dev/certbot/etc-letsencrypt:/etc/letsencrypt" -v "/Users/thibleroy/dev/certbot/ovh:/secrets" -v "/Users/thibleroy/dev/certbot/var-letsencrypt:/var/lib/letsencrypt" -v "/Users/thibleroy/dev/certbot/logs:/var/log/letsencrypt" certbot/dns-ovh certonly --dns-ovh --dns-ovh-credentials /secrets/ovh.ini --dns-ovh-propagation-seconds 60 -d thibleroy.duckdns.org -v

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator dns-ovh, Installer None
Requesting a certificate for thibleroy.duckdns.org
Performing the following challenges:
dns-01 challenge for thibleroy.duckdns.org
Cleaning up challenges
Unable to determine zone identifier for thibleroy.duckdns.org using zone names: ['thibleroy.duckdns.org', 'duckdns.org', 'org']
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): nginx proxy manager v2.11.3

The operating system my web server runs on is (include version): raspbian

My hosting provider, if applicable, is:

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): certbot/dns-ovh v3.0.0

1 Like

Why are you using certbot-dns-ovh for a DuckDNS domain? That doesn't make much sense..

3 Likes

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