Hello, I suddenly had an error to this link: https://guide.calliecares.com/discover-your-saboteur-guidebook
According to the developer, he said this: “I see that you’re using Cloudflare. Could be that they’ve made some changes at their end.
When I check the DNS for your domain I don’t find any CNAME records: https://mxtoolbox.com/SuperTool.aspx?action=a%3aguide.calliecares.com&run=tool page
My advice would be to contact Cloudflare support and ask them about any recent changes and what is the procedure now for setting up a CNAME. Let me know how you get on with Cloudflare and hopefully we can get this resolved shortly.“
But I haven’t made any changes to the DNS or CNAME records! How can I fix this? Please advise. Thank you!
That’s because proxied DNS entries are not CNAME entries but A ones. The entry itself is there and the error is something from your server which your developer needs to fix.
Also, your configuration suggests you have an insecure legacy mode on Cloudflare and no secure site.
That’s something your developer should fix as well and make sure your site is secure and on Full Strict.
Thank you, but when I set it to full strict, I have problems with my other sites (that are on this domain) as well. It says “invalid SSL certificate”. Please see attached screenshot
Also, setting it to full strict doesn’t solve my problem… I get the error message “this server could not prove that it is (the domain I used); its security certificate is from beacon(dot)by. This may be caused by a misconfiguration or an attacker intercepting your connection”
Please advise! Appreciate your kind help, thank you
Hello, I have checked and my site’s SSL is installed by my hosting service provider, Hostinger.
They have given me the following response: “If you want to use the Full Strict mode, you must install SSL from Cloudflare. But if you’d like to use our SSL, setting it to Flexible is enough. Cloudflare SSL and our web hosting SSL provide the same security but different issuer. If there is no problem with your current configuration (website is loading fine), no need to change the SSL config. Our Lifetime SSL is installed properly.”
Which brings me back to my original problem: I have a CNAME recording pointing
beacon.by
to
guide.calliecares.com
under Flexible settings and it used to work without any issues. But now, I’m getting this “NET::ERR_CERT_COMMON_NAME_INVALID” error where it states that " This server could not prove that it is guide.calliecares.com ; its security certificate is from beacon.by . This may be caused by a misconfiguration or an attacker intercepting your connection.
I’ve also made sure that instead of “proxied” DNS entry, I’ve set the CNAME entry to “DNS only”. There are no A entries for this. So I don’t know what could be the problem…
To add on, because I’m using SSL from Hostinger, I have to set the settings as Flexible instead of Full Strict, according to the support team from Hostinger.
That is incorrect information I am afraid, you do not need a Cloudflare certificate, you do need a valid certificate however, which you do not seem to have. And yes, you do need Full Strict, as you otherwise have an insecure site with no encryption. It seems most of the information provided by your host is wrong.
