Cannot generate Certificate through cerbot with Duckdns as authenticator

Help
1

My domain is:

mc-panda.duckdns.org
This domain maps to a private IP address if it makes any difference.

I ran this command:

certbot certonly --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --c ert-name "npm-28" --agree-tos --email "[email]" --domains "*.mc-panda.duckdns.org,mc-panda.duckdns.org" --authenticator dns-duckdns --dns-duckdns-credentials "/etc/letsencrypt/credentials/creden tials-28"

credentials-28 contains the DuckDNS token.

It produced this output:

The DNS response does not contain an answer to the question: mc-panda.duckdns.org. IN TXT

My web server is (include version):

Trying to setup a reverse proxy through Nging Proxy manager running through Docker.

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

I can login to a root shell on my machine (yes or no, or I don't know):

Admin on the Ubuntu server

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 2.5.0

2

A limitation of the DuckDNS API is that it only allows one TXT record at a time.

So, you can use one domain name per command. There is a trick to allow multiples which is described here. This examples uses acme.sh but the idea is the same for Certbot

The restriction is noted in the Certbot DuckDNS docs:

4 Likes
3

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