Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I would like to offer custom domains features for customers of my SaaS tool.
Here’s my initial configuration:
It looks like the easiest way to achieve this feature is to use Cloudflare’s SSL for SaaS (documentation).
What I have done:
Create a proxied CNAME for the subdomain domain.mysaas.com and connect it to the DigitalOcean’s app. Now I can use this subdomain to access the app. Easy.
From the SSL/TLS > Custom Hostnames add domain.mysaas.com as a Fallback Origin. Also, add custom.clientdomain.com in the hostname section. Custom Hostname
Go to clientdomain.com DNS settings and add: custom.clientdomain.com CNAME domain.mysaas.com. Also add a TXT record to verify the ownership.
I thought that this is enough but it doesn’t work. If I open custom.clientdomain.com I get browser’s 404 status page. I’ve checked the SSL certificate and it looks like it’s the correct one (issued by Cloudflare today).
At the same time, domain.mysaas.com works perfectly.
Is there something I’m missing? Do I need to add an A record for domain.mysaas.com (but DigitalOcean doesn’t provide it)? Could it be related to CORS settings or something?
Any help would be much appreciated! It’s been 3 days I’m trying to resolve this.
Probably there’s a better (not Cloudflare’s) solution?
EDIT: I really think I have to do something on the DigitalOcean side. Add a wildcard accepting any domain somehow…?
a6309a057c3f4cb38fb2e7feb67236
KFSys
ef1ed44cc2154be3bcbb2d727878f8
Devs Neonetworks
1e6b823ea20d4cb189a34a922f5588
Telmo Valverde
erik-jan martens
Henry Mui
anthonycarreon
garantieheld
Marin