Kinsta
import { Render } from "~/components";
<Render file="provider-guide-intro" params={{ providerName: "Kinsta", providerAssets: "websites" }} product="cloudflare-for-platforms" />
Benefits
<Render file="provider-guide-benefits" params={{ providerName: "Kinsta", providerAssets: "environment" }} product="cloudflare-for-platforms" />
How it works
For additional detail about how traffic routes when O2O is enabled, refer to How O2O works.
Enable
Kinsta customers can enable O2O on any Cloudflare zone plan.
To enable O2O for a specific hostname within a Cloudflare zone, create a Proxied CNAME DNS record with your Kinsta site name as the target. Kinsta’s domain addition setup will walk you through other validation steps.
| Type | Name | Target | Proxy status |
|---|---|---|---|
CNAME |
<YOUR_HOSTNAME> |
sitename.hosting.kinsta.cloud |
Proxied |
Product compatibility
Zone hold
<Render file="provider-guide-zone-hold" params={{ providerName: "Kinsta" }} product="cloudflare-for-platforms" />
Additional support
<Render file="provider-guide-help" params={{ providerName: "Kinsta" }} product="cloudflare-for-platforms" />
Resolving SSL errors using Cloudflare Managed Certificates
If you encounter SSL errors when attempting to activate a Cloudflare Managed Certificate, verify if you have a CAA record on your domain name with command dig +short example.com CAA.
If you do have a CAA record, verify that it permits SSL certificates to be issued by the certificate authorities supported by Cloudflare.
谢谢你的反馈!