Ask the domain owner to remove the domain from their Kinsta account, or have Kinsta support remove it for you.
Cloudflare for SaaS integrations take precedence over your own configuration, and they can be tricky to identify and remove. The best way is as above, to have the SaaS provider remove the integration on their side.
OK, we have been in contact with the domain owner for whom we will be creating a new website and apparently they have never heard of Kinsta, Cloudflare or Wordpress. The owner did tell our Support team the name company that built their existing website for them and when our team looked at the website it referred to Kinsta and Wordpress.
The question is, if the domain owner cannot get the company that built their existing website to remove their domain from the Kinsta account, are there any options to enable Cloudflare to override things?
One thing thing our support team were able to confirm is that if we turn off proxying in Cloudflare, the connection does come through to our server, but then without the proxy, they also do not benefit from Cloudflare’s free SSL certificates.
If the original company refuse to help, then create a ticket in Cloudflare, and post the ticket reference here.
<Rant> Please don’t do this. The Origin server should have a valid certificate, and nobody should just rely solely on the Cloudflare edge certificate. If you claim to be a professional services company then you should act like one.
Thanks for the additional comments. Unfortunately we are actually on a free Cloudflare account (as we don’t need any of the extra features paid accounts provide). Whilst in the past Cloudflare would permitted free accounts to create tickets, that is no longer possible. Currently when you go through the process to create a ticket it just ultimately directs people to these community forums for assistance.
Our support team have now spoken directly to Bass Media, and they took some persuading to remove the domain from their Kinsta account. Apparently they said that since the domain owner had left them and DNS was now in our Cloudflare account, they did not think it mattered that the domain name was still listed in their account. Anyway, they have now removed the domain, and proxying is working correctly in Cloudflare.
Please note, that we use proxying for the caching that Cloudflare provides not as a means of obtaining SSL, but we have all domains configured to require that Cloudflare serve content only via https. In cases where a customer wants to manage dns themselves and don’t want to use Cloudflare, ssl certificates on our server will protect visitors.