SSL Let's Encrypt — conflicting TXT records — longrichstock.com

Hosting Support
1

Error Message

Hello,

I am having an SSL/ACME validation problem with my domain longrichstock.com.

I have configured the following CNAME in Cloudflare as DNS only:

_acme-challenge
CNAME
761353de-90ad-4af3-bf3e-4457480645d0.acmedns.infinityfree.net

However, the InfinityFree SSL validation still shows:

“Current Destination: (no CNAME found)”

The desired CNAME shown by InfinityFree is exactly the same as the CNAME configured in Cloudflare.

Could you please check why the InfinityFree SSL validation system is not detecting this CNAME and re-check/restart the ACME validation for my domain?

Thank you.

2

If you’re using Cloudflare, you might be better off using their SSL tools. I’ve found that its often the easiest option

3

Yes, using Cloudflare changes everything.

First of all, you don’t even need an SSL certificate on our hosting. Just configure Cloudflare to use “Full” SSL mode and not “Full (strict)” mode, and your website will work right away, using fully encrypted connections, without any further configuration required.

If you do insist on using strict SSL mode, you can get an Origin Certificate from Cloudflare and upload that to your account.

Using a “real” SSL certificate on your hosting account should work. However, Cloudflare also sets up records on the _acme-challenge subdomain to they can obtain SSL certificates for your domain. Those (hidden!) records from Cloudflare take precedence over the CNAME record you have configured. Our DNS check sees those records, which are the “conflicting records” warning you get.