I am getting no valid A records in DNS

Help
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: ipwoodshop.com

I ran this command: docker compose run --rm certbot certonly --webroot --webroot-path /var/www/certbot/ --dry-run -d ipwoodshop.com

It produced this output: aving debug log to /var/log/letsencrypt/letsencrypt.log
Simulating a certificate request for ipwoodshop.com

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
Domain: ipwoodshop.com
Type: dns
Detail: no valid A records found for ipwoodshop.com; no valid AAAA records found for ipwoodshop.com

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

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): id now have a site. I am trying to create certifcates for my home network

The operating system my web server runs on is (include version): running ubuntu 25.04

My hosting provider, if applicable, is: registrar: namecheap.com, dns records: digitalocean.com

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): NA

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): automatic

2

Welcome to the Let's Encrypt Community.

Your domain name resolves to an RFC 1918 private IP. Those cannot be reached directly over the internet. You may want to look into using the DNS-01 challenge instead.

6 Likes
3

Agreed. And Digital Ocean's DNS has a pretty widely-supported API, so that shouldn't be much of a problem.

5 Likes
4

Well, that's assuming that the goal is for a domain that only works internally.

If instead, the plan is to have the site work globally, that should be done first. And then, the certificate acquisition will then work after that.

5 Likes
5

That seems to be what OP is saying:

6 Likes
6

Hi all,
I will use it for local lan addresses. I as able to get it running with the DSN 01 challenge. I now get the certificate, but I am having trouble to get nginx to see the certs, It is sill showing the old certs
I think it is because I am running nginx in a docker with an image that already has some stuff pointing to lets encrypt. I am using this image: jc21/nginx-proxy-manager
I am trying to get the nginx docker to see the generated certs, but I guess the docker doesn't see the main file system.

Thanks

Haakon

7

Nginx caches certs in memory, so you need to reload nginx to get it to use the new certs.

3 Likes