Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Hosting · Info

WP Engine Cloudflare Settings Explained: What Each Option Does

WP Engine Cloudflare Settings Explained: What Each Option Does

Short answer

On WP Engine, Cloudflare can run through WP Engine's Advanced Network or Global Edge Security, or through your own account on top. Point DNS to the values in the User Portal, use Full (strict) SSL and let WP Engine handle page caching.

Key takeaways

  • WP Engine's Advanced Network and Global Edge Security already use Cloudflare.
  • Your own Cloudflare account is optional and adds a second layer.
  • Copy DNS values from the WP Engine User Portal.
  • Use Full (strict) SSL, never Flexible.
  • Let WP Engine cache pages and bypass admin, login and checkout paths.

What are the WP Engine Cloudflare settings?

WP Engine Cloudflare settings are the choices you make about how Cloudflare sits in front of a WP Engine site: through WP Engine's own network options, through your own Cloudflare account, or both.

WP Engine already uses Cloudflare inside some of its products. Its Advanced Network and Global Edge Security options route traffic through Cloudflare's network without you needing a Cloudflare account.

Many site owners also run their DNS on their own Cloudflare account. In that case, the key settings are the DNS records, the proxy status, the SSL mode and the caching rules.

This guide explains what each of those does, which values usually work and where people go wrong. It is general guidance, so always compare it with the current notes in your WP Engine User Portal.

SettingWhereUsual choice on WP Engine
Network typeWP Engine User PortalAdvanced Network or Global Edge Security
DNS recordsYour DNS provider or CloudflarePoint to the value WP Engine gives you
Proxy statusCloudflare DNSProxied or DNS only, based on your plan
SSL/TLS modeCloudflare SSL/TLSFull (strict)
Always Use HTTPSCloudflare Edge CertificatesOn, with no clashing redirects
Caching rulesCloudflare CachingLight rules; let WP Engine handle pages
Rocket LoaderCloudflare SpeedOff unless tested

What network options does WP Engine offer?

WP Engine offers a legacy network, the Cloudflare-powered Advanced Network, and the paid Global Edge Security add-on, which adds firewall and DDoS protection on top.

The WP Engine Advanced Network page explains that option. It adds a content delivery network and edge protection without extra setup in Cloudflare.

Global Edge Security, often shortened to GES, is the upgrade. It adds Cloudflare's web application firewall and more security features. Cloudflare's own WP Engine integration page describes what is included.

WP Engine's network comparison page lays out the differences. Features and pricing change, so check it before you buy.

If you are not sure what your site uses, open the domain in the User Portal. The network type is shown next to each domain.

For a plain-English overview of WP Engine's CDN options, see our guide on whether WP Engine uses a CDN.

Do you need your own Cloudflare account on WP Engine?

No, you do not need your own Cloudflare account; WP Engine's network options already use Cloudflare, but you can add your own account if you want its DNS, rules or extra features.

Common reasons to keep your own Cloudflare account include:

  • Your domain's DNS is already managed there.
  • You use Cloudflare for email routing or other subdomains.
  • You want your own firewall or redirect rules.
  • You run several sites and like one dashboard.

When both your account and WP Engine's network use Cloudflare, traffic passes through your Cloudflare zone first and then through WP Engine's. Cloudflare calls this setup orange-to-orange, and it has a WP Engine provider guide for it.

That layering is fine, but it means two sets of settings apply. Most problems on WP Engine with Cloudflare come from the two layers fighting over SSL or caching.

What DNS settings does WP Engine need in Cloudflare?

Point your domain at the target WP Engine shows in the User Portal, usually a CNAME for www and a matching record for the root domain, and remove old records for the previous host.

WP Engine lists the exact record values per domain, and they depend on your network type. Copy them from the portal rather than from old blog posts.

Cloudflare supports CNAME flattening at the root, so you can often use a CNAME on the bare domain too. That lets the record follow WP Engine if its addresses change.

Keep these points in mind:

  • Delete A records still pointing at an old host.
  • Leave mail records like MX and TXT alone.
  • Wait for DNS to update before judging results.

Our guide to WP Engine DNS settings goes through each record in detail.

Should the Cloudflare proxy be on or off?

Either can work: DNS only (grey cloud) lets WP Engine's network handle everything, while Proxied (orange cloud) adds your Cloudflare rules in front of it.

DNS only is the simplest. Cloudflare just answers DNS lookups, and visitors connect straight to WP Engine's network. There is only one layer of caching and security to think about.

Proxied is useful if you need your own Cloudflare rules, like custom redirects, page rules or firewall settings. It adds a second layer, so take care with SSL and caching.

If SSL certificates fail to issue on WP Engine, a common step is switching to DNS only while the certificate is created. WP Engine's portal states which validation it needs for each domain.

Pick one approach and document it. Switching back and forth during troubleshooting often makes problems harder to trace.

Which SSL/TLS mode should you use?

Use Full (strict) in Cloudflare's SSL/TLS settings, because WP Engine serves a valid certificate and strict mode checks it on every connection.

Cloudflare explains each option in its SSL/TLS encryption modes documentation. In short, Flexible sends traffic to WP Engine over plain HTTP, which can cause redirect loops.

Full encrypts the connection but does not check the certificate. Full (strict) encrypts and checks, which is the safest choice when the origin has a real certificate.

Before switching to strict, make sure WP Engine shows an active SSL certificate for the domain. If it does not, strict mode will produce connection errors until the certificate is in place.

Our guide on Cloudflare SSL settings for WordPress covers each mode with examples.

How should you handle HTTPS redirects?

Redirect to HTTPS in one place only, either Cloudflare's Always Use HTTPS or WP Engine's HTTPS redirect setting, not with conflicting rules in several layers.

Duplicate redirects rarely break a site on their own, but combined with Flexible SSL they cause the classic too-many-redirects error.

Also check WordPress itself. Under Settings > General (see the General Settings documentation), both the WordPress Address and Site Address should start with https once SSL is working.

If you already see a loop, our guide on how to fix a Cloudflare redirect loop walks through the checks in order.

How should caching be set up?

Let WP Engine handle page caching and keep Cloudflare caching light, using it mainly for static files like images, CSS and JavaScript.

WP Engine runs its own page cache and knows when to clear it after you publish. A Cloudflare rule that caches all HTML can serve stale pages and even show logged-in content to the wrong visitors.

If you do add Cloudflare cache rules, always bypass these paths:

  • /wp-admin/ and /wp-login.php
  • Cart, checkout and account pages for stores
  • Requests with WordPress login or WooCommerce session cookies

Our guide to Cloudflare cache rules for WordPress has examples. When something looks out of date, purge both WP Engine's cache and Cloudflare's cache.

Cloudflare's APO product is built to cache WordPress pages at the edge. On WP Engine it usually adds little, since the network layer already caches. See whether Cloudflare APO is worth it before paying for it.

What speed settings are safe to turn on?

Compression and HTTP/2 or HTTP/3 are safe, but test Rocket Loader carefully because it changes how scripts load and can break sliders, forms and page builders.

Older guides mention Cloudflare's Auto Minify. Cloudflare has retired that feature, so if you need minified files, use a WordPress plugin or your build process instead.

Image optimization in Cloudflare, such as Polish on paid plans, works fine with WP Engine. Just avoid running two image optimizers on the same files.

Change one speed setting at a time and test key pages after each change. That makes it easy to see what caused a problem.

Which security settings should you watch?

Firewall rules, bot settings and high security levels can block legitimate tools, so allow WP Engine, your payment gateways and any services that call your site.

Strict bot settings sometimes block uptime monitors, webhooks and payment callbacks. If orders stop updating or webhooks fail after enabling a rule, check Cloudflare's security events first.

If you use Global Edge Security, WP Engine's own WAF already protects the site. Adding strict rules in your account on top can double-block real visitors.

What errors are common with WP Engine and Cloudflare?

The most common issues are redirect loops from Flexible SSL, 52x errors from certificate or connection problems, stale pages from over-caching and SSL certificates that will not issue.

SymptomLikely causeFirst fix
Too many redirectsFlexible SSL or clashing redirectsUse Full (strict)
Error 525 or 526Certificate problem at WP EngineCheck SSL in the User Portal
Old content showingCloudflare caching HTMLPurge cache, relax rules
Admin logged outCached admin or login pagesBypass wp-admin and login
SSL will not issueProxy blocking validationUse DNS only while issuing

For error 525 specifically, our guide on how to fix Cloudflare error 525 covers the full set of checks.

If you have not set Cloudflare up yet, start with our guide on how to set up Cloudflare for WordPress, then apply the WP Engine settings above.

Frequently asked questions

Does WP Engine work with Cloudflare?

Yes. WP Engine's Advanced Network and Global Edge Security run on Cloudflare's network, and you can also use your own Cloudflare account for DNS or proxying in front of a WP Engine site, as long as SSL and caching are set up carefully.

What SSL mode should I use with WP Engine?

Use Full (strict). WP Engine serves a valid certificate, so strict mode encrypts and checks the connection. Flexible mode sends traffic over plain HTTP to the origin and often causes redirect loops.

Should I turn on the orange cloud for a WP Engine site?

It depends on your needs. DNS only is simpler and lets WP Engine's network do the work. Proxied lets you add your own Cloudflare rules but creates a second layer, so test SSL, caching and redirects after switching.

Do I need Cloudflare APO on WP Engine?

Usually not. WP Engine already caches pages and its network options include a CDN, so APO tends to add cost with little extra gain. Measure your speed first and only add it if tests show a clear benefit.

Why will my SSL certificate not issue on WP Engine with Cloudflare?

The Cloudflare proxy can block the check WP Engine uses to validate the domain. Follow the validation steps shown in the User Portal, which may mean switching the record to DNS only until the certificate is active.

Sources

  1. WP Engine's Advanced Network WP Engine
  2. Comparing Network Options WP Engine
  3. WP Engine provider guide Cloudflare Docs
  4. Encryption modes Cloudflare Docs
  5. Global Edge Security for WP Engine Cloudflare

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.