Solved Let’s Encrypt error: No domains pointing to this server to generate the certificate for.

[twv]

After banging my head against this error for too long today and finding other threads where people were also struggling with it, I wanted to post the solution that worked for my situation in case it might be helpful to others.

This page pointed me in the right direction: https://docs.directadmin.com/webservices/ssl/troubleshooting-letsencrypt.html

However, both

http://domain.com/.well-known/acme-challenge/test.txt

and

/usr/local/bin/curl -I -L -k -X GET http://domain.com/.well-known/acme-challenge/test.txt

worked fine.

The problem turned out to be that letsencrypt.sh is hard-coded to use Google’s 8.8.8.8 nameserver, which had not updated to the new record for the domain (even though the TTL had passed). Editing letsencrypt.sh and changing

DNS_SERVER

to one I knew was correct fixed the problem.

 

[Active8]

Damn , that was exactly what happens to me , strange thing was that after few other attempts the certificate was issued correctly.
Now seeing your post maybe this happens because sometime the Google NS didnt response on time, anyway thank you for sharing

 

[Ohm J]

@smtalk
"DNS_SERVER" should have config , enable/disable this options.

remove this option, maybe result will false positive when server use "127.0.0.1" as dns resolve and don't have ipv6 assign. ( This happends when domains use 3rd dns like cloudflare ).

be like this
DNS_SERVER=0 or DNS_SERVER='' to disable
DNS_SERVER=1.1.1.1 to enable

 

[Spyder01]

I have the exact same problem, but changing the DNS_SERVER to something else didn`t work. Also, I did several checks and Google, OpenDNS and many others do return A and AAAA adressess as expected for the domains.

This issue affects all domains on the server. I looks like the issue is created after the last updates.

 

[Richard G]

I have the exact same problem,

Since this thread is marked solved, chance is smaller your issue will be seen by staff. It might be best is to create a new thread with your problem, and point to this thread explaining that the solution here doesn't work for you.