Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
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
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix Cloudflare Error 525 on WordPress

Short answer

Cloudflare error 525 means the SSL handshake between Cloudflare and your origin server failed while your SSL/TLS mode is set to Full or Full (strict). Fix it by installing a valid SSL certificate on the origin, opening port 443, and making sure the origin supports SNI and a cipher suite Cloudflare accepts. If you cannot change the origin settings yourself, send your host the error code, the time it happened, and the affected URL.

Key takeaways

  • Error 525 means the SSL handshake between Cloudflare and your origin server failed before any page was requested.
  • The error only appears when your Cloudflare SSL/TLS mode is Full or Full (strict).
  • The four causes Cloudflare lists are no valid origin certificate, closed port 443, no SNI support, and a cipher mismatch.
  • A free Cloudflare Origin CA certificate works on every plan, including the Free plan.
  • Switching from Full (strict) to Full fixes error 526, not error 525.
  • Test the origin directly with curl against its IP address, since public SSL checkers only see Cloudflare's edge.

What does Cloudflare error 525 mean?

Error 525 means Cloudflare reached your origin server but could not complete the SSL handshake, so no page was ever requested.

Cloudflare's Error 525 documentation states that the error means the SSL handshake between Cloudflare and the origin web server failed.

That matters because the failure happens before WordPress runs at all. Your WordPress files, database, and plugins can be fine, and visitors still see the error, since Cloudflare never gets far enough to ask your server for a page.

If you are still setting Cloudflare up, our guide to setting up Cloudflare for WordPress explains the proxy and DNS steps that put Cloudflare in front of your site.

Why does error 525 happen?

Error 525 happens when the origin cannot finish a secure handshake, and Cloudflare lists four causes to rule out first.

CauseWhat goes wrongFirst check
No valid SSL certificateThe origin has nothing to present during the handshakeLook for a certificate in your hosting panel
Port 443 closedCloudflare connects on port 443 and nothing answersAsk your host to confirm the port is open
No SNI supportThe server cannot tell which site is requested on a shared IPAsk your host whether SNI is enabled
Cipher mismatchCloudflare and the origin share no cipher suiteCompare the origin ciphers with Cloudflare's list

Cloudflare lists a missing certificate first in its resolution steps, so check that before the rarer causes. Port and cipher problems are more likely after a server change, a migration, or a firewall rule change.

How is error 525 different from error 526?

Error 525 means the handshake never finished, while error 526 means the handshake finished but the certificate failed validation.

Cloudflare's Error 526 page says 526 happens when Cloudflare cannot verify the origin certificate and the mode is Full (strict). That page offers switching to Full as a quick fix, but that change only skips validation, so it cannot fix a 525.

Other 5xx codes point at different faults, such as the 500 internal server error, so match the code on the page to the right fix instead of guessing.

In short, 525 is a failed negotiation and 526 is a rejected certificate. If your error page says 525, work on the handshake itself, not on the certificate details.

How do you check your SSL/TLS encryption mode?

Open the Cloudflare dashboard, go to the SSL/TLS Overview page, and read the encryption mode shown there.

Cloudflare's encryption modes page explains that Full connects to the origin with the visitor's scheme and skips certificate validation, while Full (strict) adds validation. Both modes use HTTPS to the origin, so a broken handshake can produce a 525 in either one.

Flexible and Off cannot produce a 525, because they connect to the origin over plain HTTP. If your mode is Flexible, the error on your screen is something else, or the mode changed after the error appeared.

Cloudflare now uses Automatic SSL/TLS by default, and it can raise your mode on its own. Upgrades start with 1% of traffic and rise in 10% steps, so a site can start showing 525 errors days after the mode changed, as of November 2026.

Our guide to Cloudflare SSL settings for WordPress walks through each mode and when to use it.

How do you test the origin handshake yourself?

Send a request straight to your origin server IP address to repeat the exact handshake Cloudflare tried.

Cloudflare's curl troubleshooting guide gives this command, with your own hostname and origin IP in place of the examples:

curl -svo /dev/null https://www.example.com --connect-to ::203.0.113.34

The output shows whether the TLS handshake succeeds and which certificate the origin serves. Add --tlsv1.2 or --tlsv1.3 to test one TLS version at a time, which pins down a version mismatch fast.

curl is a free command line tool for sending HTTP and HTTPS requests, and Cloudflare's guide uses it for exactly this kind of test. Run the test from a computer outside your own network when you can, so a local firewall rule cannot hide the result.

How do you fix Cloudflare error 525 step by step?

Work through the fixes in order, starting with the certificate, because that is where Cloudflare's own resolution steps begin.

  1. Confirm a certificate is installed on the origin. Check your hosting panel under SSL or Security, or ask your host to confirm one is active for your domain.
  2. Confirm port 443 is open. Cloudflare connects on port 443 by default, or on the custom secure port you set, so ask your host or check the server firewall.
  3. Install a free certificate if the origin has none. A Cloudflare Origin CA certificate or a Let's Encrypt certificate both work, so see our comparison of Let's Encrypt vs paid SSL before you pay for one.
  4. Check SNI support with your host. SNI lets the server pick the right certificate when several sites share one IP address, and older setups may lack it.
  5. Check the cipher suites. Your origin must offer at least one cipher from Cloudflare's published list, and TLS 1.2 or TLS 1.3 should be enabled.
  6. Read the origin error logs at the times the 525 errors happened. Cloudflare's Error 525 page says the logs can show a connection being reset during the handshake.

Cloudflare publishes the exact cipher suites it offers origins. Its cipher suites page lists three TLS 1.3 ciphers, TLS_AES_128_GCM_SHA256, TLS_AES_256_GCM_SHA384, and TLS_CHACHA20_POLY1305_SHA256, and your origin must share at least one cipher with that list.

Do not change WordPress settings to fix a 525. The handshake fails before WordPress runs, so a plugin, theme, or wp-config.php change cannot reach the problem.

How do you install a free Cloudflare Origin CA certificate?

Create the certificate in the Cloudflare dashboard, install it on your origin, then set your mode to Full (strict).

Cloudflare's Origin CA page says these certificates are free on every plan, including the Free plan, and work with Full (strict) mode. Create one under SSL/TLS, Origin Server, on the Origin Certificates tab, by selecting Create Certificate.

  1. Choose Generate private key and CSR with Cloudflare, and pick RSA or ECC as the key type.
  2. List the hostnames the certificate should cover. The zone apex and first level wildcard are included by default, and one certificate can carry up to 200 names.
  3. Pick a validity period, select Create, then copy the certificate and private key into separate files. You cannot see the private key again after you leave the screen, so save it at once.
  4. Upload the certificate to your origin server, enable SSL and port 443, and set the SSL/TLS mode to Full (strict).

If a paid certificate fits better, our guide to how much an SSL certificate costs lists current prices before you buy.

How do you check that the fix worked?

Reload your site over HTTPS, confirm the page loads, then repeat the curl test against the origin to confirm the handshake now succeeds.

Cloudflare's Error 525 page points to Origin Analytics for this check. The Origin status codes chart shows when Cloudflare got no HTTP response from your origin, marked as an originResponseStatus of 0, which can point to TLS negotiation failures.

Also check the site in a private browser window and open wp-admin. A clean load on both, with no 525 page, means visitors are reaching WordPress again.

Public checkers such as the Qualys SSL Server Test grade the server visitors reach, which is Cloudflare's edge when the proxy is on. That grade cannot prove the origin handshake works, so keep using curl against the origin IP for that check.

Error Analytics in the dashboard samples 1% of traffic, according to Cloudflare's 5xx troubleshooting page, so a small site may show few or no 525 entries even while the error is live. Trust the live page load and the curl result first.

When should you contact your hosting provider?

Contact your host when the fix needs a change on the origin server that your panel does not let you make.

Cloudflare's 5xx troubleshooting page says to share the exact error code and message, the time and timezone it happened, and the URL that failed. Add the output of your curl test against the origin IP.

Ask the host to check the origin error logs, plus the logs of any load balancer, cache, proxy, or firewall between Cloudflare and the origin. Cloudflare notes that the cause is not always in the origin server's own logs.

If the host says everything looks fine on their side, ask them to confirm the four items on Cloudflare's list one by one: certificate, port 443, SNI, and cipher suites. A vague all-clear answer is not a check.

What mistakes should you avoid?

The most common mistakes trade a real fix for a setting change that hides the error or moves it elsewhere.

  • Switching to Flexible SSL to make the error vanish. Flexible sends traffic to the origin over plain HTTP, and Cloudflare recommends Full or Full (strict) instead.
  • Dropping from Full (strict) to Full and expecting the 525 to clear. That switch is the quick fix for error 526, not for 525.
  • Installing a certificate and forgetting to open port 443. The handshake still has nowhere to connect.
  • Losing the Origin CA private key. Cloudflare shows it once, and a lost key means creating a new certificate.
  • Testing only the public site and calling the job done. Public SSL checkers see Cloudflare's edge, not your origin, so test the origin directly.
  • Editing WordPress to fix a Cloudflare error. WordPress is fully compatible with HTTPS once a certificate is installed on the server, according to the WordPress HTTPS handbook, but WordPress cannot fix a handshake that fails before it runs.

Frequently asked questions

Can I fix Cloudflare error 525 from the WordPress dashboard?

No. The handshake between Cloudflare and your origin server fails before WordPress runs, so no plugin, theme, or dashboard setting can reach the problem. The fix happens at the origin server or in the Cloudflare dashboard: install a certificate, open port 443, and check SNI and cipher support. WordPress only comes back into play once the handshake succeeds and pages load again.

Does error 525 mean my WordPress site was hacked?

No. Error 525 is a connection problem, not a security breach. It means Cloudflare could not finish a secure handshake with your origin server, usually because a certificate is missing, port 443 is closed, or the cipher suites do not match. A hacked site shows different signs, such as strange content, new admin users, or redirects to other sites.

Will switching to Flexible SSL fix error 525?

It makes the error page go away, but it is not a fix. Flexible SSL sends traffic between Cloudflare and your origin over plain HTTP, so the connection is no longer encrypted on that leg. Cloudflare recommends Full or Full (strict) instead. Install a valid certificate on the origin and keep the encrypted connection, rather than dropping the encryption to hide the symptom.

How long does it take to fix error 525?

A missing certificate can be fixed in minutes if your host offers one-click SSL or a free Cloudflare Origin CA certificate. Port, SNI, and cipher problems take longer, since they usually need your host to change a server setting, and that can take a few hours. If the host has to rebuild a server setup, allow a day and keep checking the site with curl against the origin IP.

Why does error 525 come and go instead of staying all the time?

A 525 that appears and disappears often points to connections being reset during the handshake, rather than a setting that is wrong all the time. Cloudflare's Error 525 page advises checking the origin error logs at the exact times the errors happened. Note those times and timezones, then ask your host to match them against the server logs to find what resets the connection.

Sources

  1. Error 525: SSL handshake failed Cloudflare Support docs
  2. Encryption modes Cloudflare SSL/TLS docs
  3. Cloudflare origin CA Cloudflare SSL/TLS docs
  4. Cipher suites - Origin Cloudflare SSL/TLS docs
  5. Gathering information for troubleshooting sites Cloudflare Support docs
  6. Error 526: invalid SSL certificate Cloudflare Support docs
  7. HTTPS - Advanced Administration Handbook WordPress Developer Resources
  8. SSL Server Test Qualys SSL Labs

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

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test