No valid IP adresses found when trying to get ssl certficate

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. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain

I ran this command:certbot --nginx --redirect -d -d -m --agree-tos --no-eff-email
It produced this output:Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for and

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Type: dns
Detail: No valid IP addresses found for

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): vultr ?

The operating system my web server runs on is (include version):Ubuntu 20.04 x64
My hosting provider, if applicable, is: vultr

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

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

1 Like

Welcome to the Let's Encrypt Community, Christian :slightly_smiling_face:

When using an HTTP-01 challenge to prove control of a domain name, it's necessary to be able to reach a webserver on port 80 at some public IP address (AAAA or A record in DNS) for that domain name.

For example, using dig we can see that has an A record:


while does not:

;AUTHORITY 300 IN SOA 5 21600 3600 259200 300

Neither has an AAAA record, which is fine.

Just add an A record for in the DNS pointing to and you should be fine.



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