maybe you have configured a page rule which triggers the page rule. Check in the “Rules” tab if a entry for the subdomain exists.
This is likely because this subdomain previously pointed to an “SSL for SaaS” zone (another Cloudflare zone) that took over your subdomains’ settings. Please contact whoever this domain was pointed to before or create a support ticket with us and post the ticket ID here, mentioning that this is a “Churned Custom Hostname”.
We can then forcefully remove the connection and you should be good to go again!
Maybe I certainly don’t understand anything.
A subdomain without protection (without proxy) leads exactly to the IP that is needed (example: 188.8.131.52), but with protection it does not lead to where I need it
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.