WP Engine
Cloudflare partners with WP Engine to provide WP Engine customers’ websites with Cloudflare’s performance and security benefits.
If you use WP Engine and also have a Cloudflare Enterprise plan, you can use your own Cloudflare accounts to proxy web traffic. This setup option is called orange-to-orange (O2O).
O2O applies both your and WP Engine’s security settings.
Benefits
O2O benefits include your own version of Cloudflare’s WAF, Bot Management, and Waiting Room.
Additionally, O2O routing also enables you to take advantage of Cloudflare zones specifically customized for WP Engine traffic.
How it works
For more details about how O2O is different than other Cloudflare setups, refer to How O2O works.
Enable
You can only enable O2O on the Cloudflare Enterprise plan.
To enable O2O on your account, create a CNAME DNS record.
| Type | Name | Target | Proxy status |
|---|---|---|---|
CNAME |
<YOUR_HOSTNAME> |
xx.wpewaf.com (Global Edge Security)OR xx.wpenginepowered.com (Advanced Network) |
Proxied |
Product compatibility
When your zone uses O2O, certain Cloudflare features can interrupt the flow of traffic to your site or display incorrect data to your visitors, including:
For a full list of compatible products and potential limitations, refer to Product compatibility.
Additional support
If you are a WP Engine customer setting up your own Cloudflare account, contact your Cloudflare account team or Cloudflare Support for help in resolving issues.
Cloudflare will turn to WP Engine if there are technical issues that Cloudflare cannot resolve.
Resolving SSL errors
If you encounter SSL errors, check if you have a CAA record.
If you do have a CAA record, check that it permits SSL certificates to be issued by digicert.com and letsencrypt.org.
For more details, refer to CAA records.