On one of our domains we have cname records that point to herokudns.com DNS targets that were generated with Herokus ACM.
All the cnames are currently with Proxy Status: dns-only. This works ok, but I get complaints that http requests are not automatically redirected to https.
So I set the ‘Always Use HTTPS’ to true in Edge certificates section.
If I now set one such cname record to proxied, it no longers directs to the heroku app. It goes to a url that I found was defined in the Page Rules section,
[I ran into another issue while working on this task, I thought for clarity I would open a new topic for it, but I was kindly advised by the moderators to use this existing topic.I edited the subject, since it no longer covers the content. I will leave the changing of the category labels, if any, to the moderators]
While trying to perform the same action on a different cname record on a different domain, it resulted in a HTTP/1.1 409 Conflict (see curl output below).
So it’s not that it got redirected via Page Rules to a different url, it makes the domain unavailable, as if it is down.
I looked up the error here: 4xx Client Error · Cloudflare Support docs
“Typically happens on a PUT request …” I don’t think this applies, no put requests were made. It is simply changing the Proxy Status that results in this error.
I don’t know how to investigate this, so even just a hint in the right direction would be appreciated
I have some more information on this problem.
Most of our cname records are subdomains for our clients and have the format customer-name.our-domain.com and the http requests that access them are pointing directly to this subdomain. In these cases switching to ‘Proxied’ works fine.