Migrating custom Hostnames from Heroku to Cloudflare for SaaS

Hi, We have the same issue as @relevantcompute, could somebody help us out please?

(from the unanswered and unresolved Issues migrating to Custom Hostnames for SaaS)


We’re having some trouble figuring out the best way to migrate from our current non-Cloudflare custom domain implementation, to Custom Hostnames (SSL for SaaS).

Our users currently C NAME their domain to our server via a subdomain e.g. they have a C NAME record on their domain pointing subdomain.theirdomain.com to cname.ourdomain.com (where the latter has the proxy turned off in Cloudflare and goes directly to our server).

Is this any way to migrate our current implementation to Custom Hostnames without downtime, or better without them updating their DNS?

Since our customers currently C NAME to an unproxied (grey cloud, bypasses Cloudflare), we can’t use that as our fallback origin in Custom Hostnames.

When I’ve tried to test out migrating a domain over (using a new proxied zone as the fallback origin, adding the hostname in Custom Hostnames, adding the txt record to DNS, and cnaming to the new fallback origin) there is downtime with a SSL_ERROR_NO_CYPHER_OVERLAP error.

Any suggestions?

Thank you.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.