Letsencrypt - Could not verify domain

ISPConfig excluded the domains as they are unreachable, you then told ISPConfig to not check domains but run let#s encrypt and Let#s encrypt was also not able to reach the domains due to missing or wrong DNS records. So ISPConfig was correct to exclude the domains from the LE cert, therefore you should enable the skip letsencrypt check again, as it worked correctly.

Next step is to fix your DNS records, the reason can also be AAAA Records and not just A records, when your system uses IPv6. Or you did not wait long enough, it may sometimes take up to 24 hours until DNS changes are propagated to all mirrors, especially when you switched to a different DNS server with that zone. You can check DNS e.g. at intodns.com

 

Sure, but this will be a self-signed SSL cert then or you have to buy an SSL cert at an SSL certification authority. Self-signed SSL certificates and also SSL certificate requests to buy a SSL cert can be created on the SSL tab of the website, enter the details in the fields at the top of the page, then select create certificate as action in the action field at the bottom and press save, you will then get a self-signed SSL cert after about 60 seconds. This also creates a certificate signing request that you can use to buy an SSL cert.

 

But just to mention it, you can't use the site live anyway before you get the DNS issue fixed as many users will fail to reach your site, in the same way, Let's encrypt failed to reach it. And when DNS is ok, then you can get a Let's encrypt cert too.

 

You know why it fails. You explained it even to me in post #3. You won't get a LE cert until you have a valid and working DNS setup, meaning that ALL DNS servers must be valid and responding, not just some servers. Look up your domain at intodns.com and fix the errors mentioned there before you try to get a LE cert.

 

Post the debug output for activating LE now (see let's encrypt FAQ post).

 

Here is the error:

The IPv4 and IPv6 records for liafi1964.in and www.liafi1964.in is incorrect or missing. And Let#s encrypt is right about this, just queried for the domains and they do not have valid DNS records.

Code:

root@server1:~# dig liafi1964.in

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> liafi1964.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50726
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;liafi1964.in.                  IN      A

;; Query time: 121 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Mar 29 10:55:55 CEST 2023
;; MSG SIZE  rcvd: 41

root@server1:~# dig www.liafi1964.in

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> www.liafi1964.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15373
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.liafi1964.in.              IN      A

;; Query time: 248 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Mar 29 10:56:01 CEST 2023
;; MSG SIZE  rcvd: 45

So the original problem that you do not have valid DNS records still persists. Fix your DNS and you will get a LE cert.

 

Your problem is not an ISPConfig issue. Contact the support of your DNS provider and ask them.