Problem Verifing TXT records


#1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:gofitnessmind.com

I ran this command:https://www.sslforfree.com/create?dns_txt_verify=_acme-challenge.gofitnessmind.com

It produced this output:No TXT Record Found. Make to set the TTL to 1 second or if you cannot set the TTL then you must wait the TTL (in seconds) so it updates before verifying the domain. Contact your DNS provider if unsure.

My web server is (include version):Apache 2.4.37

The operating system my web server runs on is (include version): linux 2.6.32-896.16.1.lve1.4.49.el6.x86_64

My hosting provider, if applicable, is:namecheap

I can login to a root shell on my machine (yes or no, or I don’t know):no

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):Yes cPanel 70.0 (build 61)

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):no


#2

You’ve been creating the records in your DNS user interface in a way which causes them to get saved wrong - https://letsdebug.net/gofitnessmind.com/23144

Try removing the .gofitnessmind.com portion next time you try (so just _acme-challenge into the input field).


#3

Ok thank you, I’m going to try that now… :smiley:


#4

@_az I changed host records as you suggested _acme-challenge WITHOUT the .gofitnessmind.com waited a few minutes and then re-tried to verify and it still fails with error:No TXT Record Found. Make to set the TTL to 1 second or if you cannot set the TTL then you must wait the TTL (in seconds) so it updates before verifying the domain. Contact your DNS provider if unsure.

Note: however, it now passes as All OK! in https://letsdebug.net/gofitnessmind.com/23145 BUT I still cannot Verify TXT records


#5

It definitely looks like you did it right.

What subdomains are you including, if any?


#6

no specific subdomains, but I used a wildcard *.gofitnessmind.com as directed on sslforfree.com to include future subdomains


#7

I think it should be working.

I note that the error message you got doesn’t come from Let’s Encrypt. It seems to come from sslforfree.com (maybe it does a pre-flight check on your domain).

If you’re having continued trouble, you might have a go at doing the same thing with ZeroSSL, which works in a pretty similar way, and maybe wait a couple of minutes extra after you set the DNS records.

Edit: Oh man, I just realized that sslforfree.com is complaining about your TTL, not about the value of the TXT record. Are you sure you can’t just ignore that warning and just continue? Alternatively change your TTL to 1 second in cPanel (even though it’s really not necessary).


#8

Ok thank you for your time. :smiley: I’ll go look into that…


#9

namecheap DNS only allows TTL to be set at 1minute minimum. I cant change this…


#10

Yeah, it’s not a real requirement anyway. Either ignore the warning in sslforfree if you can, or try the other website.


#11

OK thanks for your time again, I just installed the certificate anyway and ignored sslforfree error message!

ALL WORK GREAT now thanks! :smiley:


closed #12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.