Changing CNAME from DNS-only to Proxied results in HTTP/1.1 409 Conflict

[anon9246926]

Believe this was solved via a second thread @tech39?

Changing CNAME from DNS-only to Proxied, causes several problems

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 s…