Failed to get SSL in Let's Encrypt

[itcur7]

SYSTEM INFORMATION
OS type and version	Ubuntu 18.04 64bit with Webmin/Virtualmin/LAMP
Virtualmin version	7.5

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Obtaining a new certificate
Performing the following challenges:
dns-01 challenge for itcusys.online
dns-01 challenge for itcusys.online
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. itcusys.online (dns-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.itcusys.online - check that a DNS record exists for this domain, itcusys.online (dns-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.itcusys.online - check that a DNS record exists for this domain
IMPORTANT NOTES:

The following errors were reported by the server:

Domain: itcusys.online
Type: None
Detail: DNS problem: NXDOMAIN looking up TXT for
_acme-challenge.itcusys.online - check that a DNS record exists for
this domain

Domain: itcusys.online
Type: None
Detail: DNS problem: NXDOMAIN looking up TXT for
_acme-challenge.itcusys.online - check that a DNS record exists for
this domain

My hosting provider, if applicable, is: Hostinger

[stefan1959]

For some reason its doing a DNS challenge and DNS TXT records don’t exist. I never use wildcard. Untick and see what happens.

[itcur7]

I tried and this are the outputs. I transfer to image because I cant send links. Thank you.

[itcur7]

[itcur7]

[stefan1959]

You have setup the DNS correctly and point to the correct IP.

[itcur7]

Yes.

[itcur7]

[stefan1959]

Ok I used this https://letsdebug.net/ its saying you have muliple IP addresses. I see IP6 address in the error above, maybe that the issue.

[stefan1959]

Ide drop the IP6

[itcur7]

Thank you for your help. I will try this

[stefan1959]

weird, docs say it should work as long as the address are correct.

IPv6 Support - Let's Encrypt

[itcur7]

Yeah as check my ip is still not yet propagated after i drop the IPv6

[Joe]

The errors are clear.

It’s not talking about an A record. It is talking about a TXT record that is generated in real time at the time of request. If Virtualmin is not managing your DNS, and if you haven’t properly delegated authority for DNS to the Virtualmin server and its secondary DNS server(s), then DNS validation cannot work.

Wildcards are not recommended, in general, but they can’t be validated in Virtualmin if Virtualmin is not managing your DNS, because it requires immediate creation of a TXT record with the necessary information.

A records are absolutely irrelevant here.

You posted another log for a non-wildcard request, which shows 404 errors from the web server, which is always one of three things.

1. DNS is wrong. Let’s Encrypt validation server is hitting the wrong web server when it tries to request the verification file. If you have correct A records this isn’t you.
2. You have a proxy or redirect preventing access to the .well-known path where Let’s Encrypt verification file must be accessible. Check this by putting an HTML or text file in /home/domainname/public_html/.well-known/ and see if you can browse to it. I assume you cannot. You have to fix that.
3. Misconfiguration of Apache (or nginx) Virtual Hosts causing the wrong site to be served. Browse to the domain (without https), do you see the right site? If not, fix that.

You can search for either of these problems, they’ve been discussed a ton, and it can literally only ever be one of those three things (wildcards can only be a DNS problem, because wildcards can only be validated via DNS).

[itcur7]

Okay thanks I found the solution to my problem there are some misconfiguration on my end.