Failed authorization procedure. (http-01): urn:ietf:params:acme:error:dns :: No valid IP addresses found

Having some trouble using Certbot to install an SSL certificate for your website? Getting hit with an error message that looks something like?:

Failed authorization procedure. (http-01): urn:ietf:params:acme:error:dns :: No valid IP addresses found for


The following errors were reported by the server:

Type: None
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.

Okay, so here’s what’s probably going on: You just bought your domain name, set your nameservers, uploaded a landing page to your server etc., then wham! Certbot just doesn’t want to add that little https to your URL. The issue may be that your newly registered domain name hasn’t propagated through the internet’s DNS registry yet so Certbot is having a hard time finding the corresponding IP Address for your new domain.

The solution? Just give GoDaddy or whoever else you used to register your domain a little more time update everything and try running Certbot again.

If you’d like to test this hypothesis out, try visiting your new domain through Google Chrome AND Mozilla Firefox AND/OR Apple Safari. I found that while Google Chrome could not find my new domain, Firefox found the new domain easily and displayed my placeholder landing page just fine, albeit with an “unsecure” icon indicating that the site had not yet been secured with an SSL certificate. Likewise, it appears Certbot itself can’t find the newly registered domain either, just like Google Chrome. If you happen to have multiple browsers, try visiting your domain from different browsers to see if you can duplicate what I’ve described above. If you find that your website isn’t showing up yet, give your registrar and the World Wide Web a little time to process things and try again.