Certbot "no valid ip addresses found"

  • Posted March 27, 2021
  • LEMP

I’ve been following the tutorial for SSL certification (

overall I am trying to set up a WordPress site on a virtualbox following this tutorial:

and I’ve run into a roadblock.

For reference, my domain is

When running the command:

sudo certbot --nginx -d -d

I get the error:

Obtaining a new certificate
Performing the following challenges:
http-01 challenge for
http-01 challenge for
Waiting for verification...
Challenge failed for domain
Challenge failed for domain
http-01 challenge for
http-01 challenge for
Cleaning up challenges
Some challenges have failed.

 - The following errors were reported by the server:

   Type:   dns
   Detail: No valid IP addresses found for

   Type:   dns
   Detail: No valid IP addresses found for
 - Your account credentials have been saved in your Certbot
   configuration directory at /etc/letsencrypt. You should make a
   secure backup of this folder now. This configuration directory will
   also contain certificates and private keys obtained by Certbot so
   making regular backups of this folder is ideal.

My domain is registered on NameCheap with A Records for and

The records can be confirmed at which shows that the a records for both can be found.

I’m quite new to this and not sure how to progress, any info would be appreciated.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi there,

In order for Certbot to be able to issue a certificate for your domain name, you need to set your domain name’s A record to the public IP address of the Droplet.

At the moment your A record for the domain name is pointing to t private IP ( so Let’s encrypt is not able to verify the domain name.

Once you point your domain name to the public IP, you need to run the command again and it should work as expected.

Regards, Bobby