SSL request failed due to conflicting TXT records

[Girofle]

Hi,

Would someone know how to fill the CNAME data on Dynadot, as am not familiar with it ?

And just while asking for a SSL certificate, the infamous red message about conflicting TXT records were found, just showed up, even before tryng to access to Dynadot.

Website URL

mobilchips.com

Error Message

Thanks

[Girofle]

Hi, am just facing the same issue, with this error
Current Destination (no CNAME found) Conflicting TXT were found.

Would somebody know what to do to sort this out ?

On Dynadot DNS settings it seems not very handy to fit all those lines.
But the error appeared way before i accessed to the DNS.

Thanks

[Frank419]

You can just fill out the DNS records at dynadot. The DNS control panel should be available inside your dynadot account > my domains > your current domain.

The terms should match the panel, so please fill them out accordingly.

@Girofle

the infamous red message about conflicting TXT records were found

Error messages are not showing up to disgust you, they show up because there really is an issue.

Please go to your dynadot DNS panel to see if there’re already a TXT record for _acme-challenge.mobilchips.com.

[Girofle]

Hi Frank thanks for replying

I tried over and over to fill the dns boxes and didnt succeed, maybe during two hours.

Also at the first place its asking me to forward with a 301 to my own url, the error on dynadot says its impossible to forward to my own domain.

And no there is no TXT from infinity on my dynadot at all.

Thanks

[Frank419]

From what I remembered, DynaDot uses Cloudflare for its DNS, so it’s possible that the same mechanism that caused this issue on Cloudflare domains also applied to you.

Please give it serveral hours and see if it helps.

[Admin]

I checked it, and this is just a bug in the client area. DynaDot’s nameservers are not the same as Cloudflare’s, but they respond differently than any nameservers I’ve seen before, causing the client area to behave unexpectedly. That’s being fixed now.

That said, the CNAME record you need to configure is really missing. The bug in the client area doesn’t prevent you from getting an SSL certificate, but not setting up the required DNS records will.

[Girofle]

Actually its left blank, as it doesnt accept to leave the redirection to the domain name.

Will try to ask dynadots support by the way.

Thanks

[Girofle]

Thankfully, the Dynadot support assisted me, and shown how to properly fill the CNAME data Infinityfree asks to fill.

I will post a next comment with the screenshot attached, and the litterature Dynadot sent me, in case someone else gets stuck on this.

Now all seems to work, except on softaculos, that a message states that there is no trusted SSL certificate, but let’s wait a day for it to propagate.

Thanks

[EdwardHamHam]

@Girofle

Now all seems to work, except on softaculos, that a message states that there is no trusted SSL certificate, but let’s wait a day for it to propagate.

Because of the way InfinityFree’s Softaculous instance is set up, it’ll always there’s no SSL certificate, even if there is. Instead you can just ignore that warning, or set to install the script for HTTP instead. You can generally configure scripts to exclusively use HTTPS after they’re installed.