Let's Encrypt Error: Conflicting TXT records were found

[OB6KXB]

Website URL

https://newton.space

Error Message

Let’s Encrypt error: Please set up the following CNAME record on your domain. [blabla] Current Destination: (no CNAME found) Conflicting TXT records were found
Record Name: _acme-challenge
Domain: newton.space
Destination: 3c5f4a81-f45d-44ab-ab36-f6b255c35bf8.acmedns.infinityfree.net

This error is not correct… the correct CNAME record is in DNS for quite a while. there is no duplicate entries and replication has taken place.

Other Information

Any tips to get Let’s encrypt going?

[KangJL]

@OB6KXB

This error is not correct… the correct CNAME record is in DNS for quite a while

Are you sure?

This is what I see

DNS Checker - DNS Check Propagation Tool

@OB6KXB

there is no duplicate entries and replication has taken place.

Please provide proof

This may be better for you

How to setup Full SSL with Cloudflare

By default, Cloudflare uses a system called “Flexible SSL”. In this system, Cloudflare secures the connection between your visitors and Cloudflare, but not the connection between Cloudflare and your website. Not only is this less secure, some websites (notably WordPress) have trouble detecting whether HTTPS is in use, causing all sorts of issues. The best way to resolve this is by using Full SSL in Cloudflare. This way, the connection between Cloudflare and your website is encrypted, and your w…

[OB6KXB]

Sorry had just deleted the record to see if that remediates it. Put back now but not fixed yet.

No dupes:

[Admin]

@OB6KXB

Conflicting TXT records were found

The interface can use a lot of polishing for this, but this is the key point: you may have the CNAME records setup, but there are TXT records returned by your nameservers that are preventing the CNAME record from taking effect.

Specifically, this is caused by Cloudflare injecting hidden DNS records in their domain, so they can validate your domain against certificate providers to obtain the certificates they use to secure the connection between your visitors and their infrastructure.

As far as I know, there is not much you can do about that, except wait for Cloudflare to finish doing it’s thing.

However, since you are using Cloudflare, you don’t really need the Let’s Encrypt certificate in the first place. You can just use Cloudflare’s Full SSL mode right now, and it will use our default self-signed certificate to secure the connection, which is functionally identical, and almost as secure.