iebojiQ: TidyCal does not generate SSL certificates
My domain is: consult.chatbizsol.com
I am setting up a custom domain for my TidyCal booking page.
My DNS record is:
CNAME
consult → members.tidycal.com
DNS propagation has completed globally (confirmed via DNSChecker), and TidyCal shows “DNS configured” in the dashboard.
However, visiting:
https://consult.chatbizsol.com
returns the error:
NET::ERR_CERT_COMMON_NAME_INVALID
The SSL certificate presented is *.tidycal.com, which does not match the custom domain.
My DNS is managed via QuicCloud DNS, and the subdomain resolves correctly to members.tidycal.com.
Does TidyCal provision SSL certificates for custom domains pointing to members.tidycal.com, or is a Cloudflare proxy required for SSL to work?
Luka_originals
Mar 23, 2026A: Thanks for reaching out, everyone!
Custom domains with SSL are now fully supported. We've rolled out automatic SSL provisioning for custom domains and published a step-by-step setup guide here: https://help.tidycal.com/article/1000-custom-domains---use-your-own-domain-for-booking-pages
If you've already set up your CNAME and are still seeing the SSL error, please reach out to our support team at [email protected] with your custom domain and we'll get the certificate provisioned for you right away!
I hope they can resolve this issue as quickly as possible. For a moment I was happy to have access to this new feature. 🙁
The issue we have is while you can create a CNAME to point to TidyCal recommended domain which is members.tidycal.com, it id for TidyCal to generate the SSL certificate to match the CNAME. That is something only they can do.
I’m having the same issue.
Verified purchaser
I’m having the same issue.
Verified purchaser
Same here. Plus I can't choose my custom domain. It's stuck on tidycal.
I am guessing they are workng in the background to fix it. But so far, they hve not acknowledge the issue is with them.
I’m having the same issue
If you can't create CNAME directly, ask your hosting company to do so for you. Most Hostly plans allow for the creation of CNAME.
SSL report:
https://www.ssllabs.com/ssltest/analyze.html?d=consult.chatbizsol.com
The scan shows TidyCal’s AWS servers responding but presenting the wildcard *.tidycal.com certificate, suggesting the custom-domain SSL has not yet been issued.
Could you please trigger SSL provisioning for consult.chatbizsol.com?
Thank you.
Did you get ANY reply? Same problem here, seems to remain unsolved. Other questions were quickly answered so I must assume Tidycal has no interest in fixing it. Will move on to Lapsula, which is GDPR compliant and responsive. So sad.
Yes, I receievd a reply from the TidyCal team in which they made the assumption that I am using Cloudfare as my DNS provider, even though I stated repeatedly I am using QuicCloud as my DNS provider. That is all beside the point. The real issue is they are still issuing SSL to their domain, hence the error. They can fix this by triggering SSL provisioning for their customers' custom domain (CNAME).
10 days passed since this post, is the (big) issue been handled?
No. Still waiting for a response since this post.
Good news. TidyCal has acknowledged the issue and have instructed their technical team to generate an SSL certificate for my custom domain on their AWS infrastructure and deploy it to the correct server within 24 hours. Let you know as soon it is finally resolved.
Thank you. I can confirm it is as you say.