Signed certificate for a Cisco Router with a UBUNTU machine

Help
1

Hi,
I've been trying to sign a certificate from let's encrypt for a Cisco Router, i'm test with two domain but show me the same result, Down are the info that i hope that be useful

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:
networkconsulting.cloudns.nz

I ran this command:
sudo certbot certonly --manual -d networkconsulting.cloudns.nz --agree-tos --manual-public-ip-logging-ok --preferred-challenges dns-01 --server https://acme-v02.api.letsencrypt.org/directory --register-unsafely-without-email --rsa-key-size 2048

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for networkconsulting.cloudns.nz

Please deploy a DNS TXT record under the name:

_acme-challenge.networkconsulting.cloudns.nz.

with the following value:

jj5PK5hJrI80PxRzBS1torSb9XHHD2iVZ5KE4gViRRc

Before continuing, verify the TXT record has been deployed. Depending on the DNS
provider, this may take some time, from a few seconds to multiple minutes. You can
check if it has finished deploying with aid of online tools, such as the Google
Admin Toolbox: Dig (DNS lookup).
Look for one or more bolded line(s) below the line ';ANSWER'. It should show the
value(s) you've just added.

Press Enter to Continue

Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems:
Domain: networkconsulting.cloudns.nz
Type: dns
Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.networkconsulting.cloudns.nz - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to verify the manually created DNS TXT records. Ensure that you created these in the correct location, or try waiting longer for DNS propagation on the next attempt.

Some challenges have failed.
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):
Router Cisco ISR 4000

The operating system my web server runs on is (include version):
UBUNTU 22 /

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):
yes, through
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
$ certbot --version
certbot 1.32.0

Thanks in advanced.

1 Like
2

Hello @darksuite, welcome to the Let's Encrypt community. :slightly_smiling_face:

Using https://letsdebug.net/ with DNS-01 Challenge the result: Let's Debug

image
image978×178 3.81 KB

Testing and debugging are best done using the Staging Environment as the Rate Limits are much higher. Rate Limits are per week (rolling).

Doesn't seem to have happened

> set q=txt
> networkconsulting.cloudns.nz
Server:         ns44.cloudns.net.
Address:        185.206.180.140#53

networkconsulting.cloudns.nz    text = "ns41.cloudns.net"
> _acme-challenge.networkconsulting.cloudns.nz
Server:         ns44.cloudns.net.
Address:        185.206.180.140#53

** server can't find _acme-challenge.networkconsulting.cloudns.nz: NXDOMAIN
>
1 Like
3

You may want to review the results from DNSViz. The Error may be causing at least some of these problems.
https://dnsviz.net/d/networkconsulting.cloudns.nz/dnssec/

3 Likes
4

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