I received email asking me to add CNAME records with Hostinger so that certificate renewal process can be completed. I did add the records as instructed, waited for more than 12 hours but I am still not able to complete the certificate renewal process.I keep getting the error and asking me to contact support. But there is no way to contact the support. This is for website for a non profile organization. So, I don’t have any type of support plan.
The validation page displays the message “An error occurred while attempting to validate your domain. Please try again later or contact support for assistance.”.
-
What domain?
-
Can you share a list, perhaps a screenshot, of the record(s) you have issues with, so we can see how they appear in your Cloudflare Dashboard?
When adding a validation CNAME in Cloudflare, it is important that it is set to 
DNS Only. When a CNAME is 
proxied, it is published as A and AAAA records, not as a CNAME record. That means that any validation attempt that needs to see a CNAME will fail.
meant to say - website for a non profit organization.
domain is kalaikoodamorlando.com
Screenshot of CNAME values I have in Hostinger.
_ca3-7308b824558b4d5a9b8ddac9aea71bc3.kalaikoodamorlando.com - dcv.digicert.com
_ca3-5ece80d626c34c6a94612e292f945c9d.www.kalaikoodamorlando.com - dcv.digicert.com
I tried to add as A or AAAA records but it is asking me to provide valid IP address for a point to value. The email that I received from Cloudflare says to add as CNAME value and no IP addresses were provided.
I was not suggesting that you should create any A or AAAA records. I was explaining that when you set a CNAME to it will not be found as a CNAME.
Make sure that when you need a CNAME for validation purposes that you set it to DNS Only.
All of this is purely academic since your domain does not currently use Cloudflare.
See this analysis for more details:
https://cf.sjr.org.uk/tools/check?d66e0b288e034645b04279e6b30ca551#whois
The relevant details:
Name Server: NS1.DNS-PARKING.COM
Name Server: NS2.DNS-PARKING.COM
You seem to have stopped before step 2 in this guide. If you plan on using Cloudflare your site still needs to be activated.
1 Like
Thanks for the responses. But I am really confused with all these. I am not very technical in this area. Out site has been up and running for few years. I have DNS registered with Hostinger and I think Cloudflare is for the edge locations (probably not stating this correctly). It seems too complicated steps to go through just for the SSL certificate renewal process. Attaching one of the email received from Cloudflare.
These two CNAME’s do exist in your DNS, and if it doesn’t work, it isn’t a problem on your side, as well as it isn’t on Cloudflare’s side either.
It looks like that domain name may have partially used Cloudflare in the past.
For example in 2021, as well as up to (and including) the first few days of December 2022, it seems like your domain was pointing to Cloudflare.
In addition, it seems like the pointing towards Cloudflare may have been through a provider such as Hostinger, but via the Cloudflare for SaaS product, or alternatively through something like Cloudflare Pages.
However, steadily from December 2022, your domain has been pointing directly towards Hostinger.
→
Are you aware of any huge changes to your website around the first half of December 2022?
If NOT:
Hostinger may have changed certain things around that time, in regards to how they ran their stuff, such as previously running their customers via Cloudflare for SaaS, but then decided to drop the use of the Cloudflare for SaaS product, but where they also haven’t properly cleaned up after them, which could be one plausible reason to why you see these certificate warnings.
It may not be Hostinger, but could be another provider. However, if you haven’t done any kind of huge change to your website around December 2022 from your own side, the plausible example with Hostinger would sound most accurate.
1 Like
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.