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 ERR_SSL_PROTOCOL_ERROR in WordPress

Short answer

ERR_SSL_PROTOCOL_ERROR means Chrome could not finish the secure TLS handshake with your WordPress site. Check the certificate first, then your system clock, browser extensions and antivirus, then the Cloudflare SSL mode and WordPress HTTPS settings. In most cases, renewing an expired certificate or fixing a wrong SSL mode clears the error.

Key takeaways

  • ERR_SSL_PROTOCOL_ERROR means the TLS handshake failed before Chrome could load any page.
  • Let's Encrypt certificates last 90 days by default, and Let's Encrypt recommends renewing them every 60 days.
  • Cloudflare Full (strict) checks the origin certificate, while Full does not check it at all.
  • WordPress 5.7 added a Site Health HTTPS check with a one-click switch to HTTPS when the server supports it.
  • A wrong system clock can cause a certificate date error, so set the date and time correctly first.

What does ERR_SSL_PROTOCOL_ERROR mean?

ERR_SSL_PROTOCOL_ERROR means Chrome could not finish the secure TLS handshake with your site, so it stopped before any page loaded.

A TLS handshake is the short exchange where your browser and server agree on encryption before they send page data.

Chrome shows the message “This site can't provide a secure connection” with this code when the secure connection fails. Google Chrome Help says that for a secure-connection error Chrome could not understand, you should contact the website owner.

This error is not the same as a mixed-content warning. Mixed content lets a page load with some insecure parts, while this error blocks the whole page.

What causes ERR_SSL_PROTOCOL_ERROR on a WordPress site?

The most common site causes are an expired or missing certificate, a wrong Cloudflare SSL mode, and a server that offers only old TLS versions.

CauseWho sees itFirst check
Expired certificateEvery visitorCertificate expiry date in the browser
No certificate on the originEvery visitorHost SSL panel
Wrong Cloudflare modeEvery visitorSSL/TLS Overview in Cloudflare
Old TLS version or cipherVisitors on newer browsersServer TLS settings
Wrong system clockOne device onlyDevice date and time
Browser extension or antivirus scanOne device onlyIncognito test

A certificate can also fail if it names a different domain. The name on the certificate must match the domain in the address bar.

A proxy or CDN in front of WordPress adds a second connection. If that second link has no valid certificate, the handshake can fail even when the public padlock looks fine.

How do you tell if the fault is your browser or your site?

Test the site in a second place before you change any server setting.

  1. Open the site on a phone with Wi-Fi off, using mobile data.
  2. Open 2 or 3 other secure sites in the same browser.
  3. Ask a friend in another place to open your site.

If other secure sites fail too, the fault is on your device or network. If only your site fails on every device and network, the fault is on your site.

If the site fails on one computer but works on a phone, start with the browser fixes in the next section. Do not renew a certificate for a fault that follows one device.

How do you fix ERR_SSL_PROTOCOL_ERROR in Chrome first?

Fix the browser side first, because those checks take minutes and need no server change.

  1. Check the date and time on your device and set them correctly.
  2. Open the page in an Incognito window.
  3. Turn off browser extensions, then turn them back on one at a time.
  4. Clear browsing data in Chrome, then reload the page.
  5. Update your operating system, then restart Chrome.

Google Chrome Help says a wrong date and time can cause a certificate date error, and the fix is to make the time and date correct. The same page says to open the page in Incognito mode and, if it opens there, turn off the extension that blocks it.

Antivirus software can also break the handshake. Google Chrome Help says software that provides “HTTPS protection” or “HTTPS scanning” can cause the error, so turn that feature off to test it, then turn it back on when you finish.

If the site still fails in Incognito mode with extensions off, the fault is likely on the server. Move to the certificate checks below.

How do you check and renew an expired certificate?

An expired certificate is the first server fault to rule out, because it blocks every visitor.

  1. Open your site in Chrome, select the padlock or “Not secure” icon, then select “Certificate is not valid” or “Certificate” to read the expiry date.
  2. Open your host SSL panel and check the status for your exact domain, including www and non-www versions.
  3. Renew the certificate, or ask your host to renew it, then reload the site after 5 minutes.

Let's Encrypt says its default certificates are valid for 90 days, with no way to adjust the lifetime and no exceptions. The same FAQ recommends renewing 90-day certificates every 60 days and 6-day certificates every 3 days, as of November 2026.

Let's Encrypt offers Domain Validation (DV) certificates only, and it does not offer OV or EV certificates. Its certificates are free, so a renewal fault is usually a failed auto-renewal, not a payment fault.

If your host uses another certificate type, check its expiry date in the same way. A paid certificate lasts longer, but it still expires, so note the date in your calendar. For help choosing a certificate type, read Let's Encrypt vs paid SSL.

How do you fix the WordPress address and admin SSL settings?

Tell WordPress to use HTTPS after the certificate works, or WordPress will keep building HTTP links.

  1. Back up the site, then log in to wp-admin over HTTPS.
  2. Go to “Settings → General” and change both “WordPress Address (URL)” and “Site Address (URL)” from http:// to https://.
  3. Select “Save Changes”, then log back in at the HTTPS address.
  4. Go to “Tools → Site Health” and open the HTTPS status section.

WordPress 5.7 added HTTPS detection and a one-click switch in Site Health. Make WordPress Core says WordPress checks whether both the Site Address and WordPress Address use HTTPS, and it shows a button to switch both URLs with one click when the server already supports HTTPS.

For the admin area, add one line to wp-config.php above the line that says “That's all, stop editing!”:

define( 'FORCE_SSL_ADMIN', true );

WordPress Developer Resources says this constant forces all logins and all admin sessions to happen over SSL. The same page says it must be defined in wp-config.php, not in a plugin file, and SSL must already be set up on the server first.

If WordPress sits behind a proxy that provides SSL while WordPress itself has no SSL, the same handbook warns that these settings can send requests into an infinite redirect loop. In that case, configure WordPress to recognise the HTTP_X_FORWARDED_PROTO header, and read how to fix a Cloudflare redirect loop.

How do you fix the Cloudflare SSL mode?

A wrong Cloudflare mode is a common cause on WordPress sites behind Cloudflare, so check it after the origin certificate.

  1. Log in to Cloudflare and open your domain.
  2. Go to “SSL/TLS → Overview” and read the current encryption mode.
  3. If the origin has a valid certificate, set the mode to “Full (strict)”.
  4. Save the change, wait 5 minutes, then reload the site in a fresh Incognito window.

Cloudflare says the SSL/TLS Encryption Mode controls 2 connections: one between visitors and Cloudflare, and one between Cloudflare and your origin server. Cloudflare strongly recommends using Full or Full (strict) modes.

Flexible mode encrypts the visitor link but leaves the Cloudflare-to-origin link unencrypted, and Cloudflare says it is common for origins that do not support TLS. Full mode uses HTTPS to the origin without checking the origin certificate, while Full (strict) adds checks on that certificate.

Cloudflare says a Full (strict) origin certificate can be issued by a public CA like Let's Encrypt or by Cloudflare Origin CA. If your origin has no certificate at all, install one first, then move to Full (strict). For the full set of settings, read Cloudflare SSL settings for WordPress.

Cloudflare now uses Automatic SSL/TLS as the default for many zones. The same Cloudflare page says scans run about once per month, upgrades start at 1% of traffic, then move in 10% steps to 100%, and Cloudflare rolls traffic back if origin connectivity fails.

How do you fix old TLS versions and ciphers on the server?

Old TLS settings can break the handshake in newer browsers, even when the certificate is valid.

Ask your host to set the server to TLS 1.3, and to keep TLS 1.2 for older clients. Google Chrome Help gives this exact advice for ERR_SSL_VERSION_OR_CIPHER_MISMATCH, and names TLS_AES_128_GCM_SHA256 as the cipher to use with TLS 1.3.

The same Google page says Chrome blocks sites with an outdated security code to protect your privacy. That means you cannot fix this fault from the browser side alone.

  1. Ask your host which TLS versions the server offers.
  2. Ask the host to turn off TLS 1.0 and TLS 1.1.
  3. Ask the host to turn on TLS 1.2 and TLS 1.3.
  4. Reload the site and check the padlock again.

If the host cannot change the TLS version, move the site to a host or plan that can. A certificate alone does not fix a server that speaks only old TLS.

How do you confirm the fix worked?

Confirm the fix on more than one device, or you may miss a fault that only some visitors see.

  1. Reload the site in a normal window and in an Incognito window.
  2. Open the home page, a post, and wp-admin.
  3. Open the site on a phone with Wi-Fi off.
  4. Check the certificate expiry date again in the browser.

The padlock should show in the address bar, and no error page should appear on any of those loads. If wp-admin loads over HTTPS but the front page still shows HTTP links, repeat the “Settings → General” step above.

If the error returns after a short time, check the certificate renewal log at your host. A renewal that fails once will fail again at the next expiry date. For a related Cloudflare handshake fault, read how to fix Cloudflare Error 525.

When should you contact your host?

Contact your host when the fault is on the server side and you cannot change the setting yourself.

  • The certificate is expired and the host panel has no renew button.
  • Auto-renewal keeps failing, or the host shows a certificate error.
  • The server offers only old TLS versions.
  • The site works without Cloudflare but fails with Cloudflare on.
  • The error affects every visitor on every device and network.

Give the host the exact error code, the domain, the time you first saw it, and the steps you already tried. That list helps support check the certificate, the TLS settings, and the server logs in one pass.

If the host says the certificate is valid, ask the host to check the origin server directly, without Cloudflare in front of it. That test shows whether the fault is at the origin or at the CDN layer. To set up Cloudflare cleanly after the fix, read how to set up Cloudflare for WordPress.

What mistakes should you avoid?

Avoid the shortcuts that hide the error instead of fixing the certificate or the TLS settings.

  • Do not tell visitors to click past a security warning on a public site.
  • Do not set Cloudflare to Flexible to hide a missing origin certificate.
  • Do not add FORCE_SSL_ADMIN before the server has a working certificate.
  • Do not change the WordPress address to HTTPS before the certificate is live.
  • Do not turn off antivirus protection for good; turn it back on after your test.
  • Do not keep using TLS 1.0 or TLS 1.1 because an old device still needs them.

Each of these steps can make the site load for a short time while leaving the real fault in place. Fix the certificate, the TLS version, and the SSL mode, then confirm the fix on 2 devices.

Frequently asked questions

Is ERR_SSL_PROTOCOL_ERROR the same as ERR_SSL_VERSION_OR_CIPHER_MISMATCH?

No. ERR_SSL_PROTOCOL_ERROR means the secure handshake failed in a general way, while ERR_SSL_VERSION_OR_CIPHER_MISMATCH points to an outdated TLS version or cipher on the server. The second error is more specific, so ask your host to turn on TLS 1.2 and TLS 1.3. Both errors block the page, and both need a server-side fix in most cases.

Can a wrong system clock cause ERR_SSL_PROTOCOL_ERROR?

Yes, on one device. A wrong date or time can make a valid certificate look expired or not yet valid, so Chrome rejects the connection. Set the date and time correctly, restart the browser, and reload the site. If the error still appears on other devices too, the fault is on the site, not the clock.

How long does a Let's Encrypt certificate last?

A default Let's Encrypt certificate lasts 90 days, and Let's Encrypt recommends renewing it every 60 days. Short-lived certificates last 6 days and should be renewed every 3 days. Most hosts renew them automatically, so check the auto-renewal log if a certificate expires without warning.

Should I use Cloudflare Flexible or Full (strict)?

Use Full (strict) when your origin server has a valid certificate. Flexible leaves the link from Cloudflare to your origin unencrypted, so it should only be a short-term step for an origin that cannot yet serve TLS. Full encrypts that link but does not check the certificate, while Full (strict) checks it.

Why does the error appear only in Chrome and not in another browser?

Browsers differ in which TLS versions, ciphers and certificate checks they accept, and in how they handle extensions and antivirus scans. Test the site in an Incognito window, turn off extensions, and test on another device. If the site fails in every browser, the certificate or server TLS settings are the likely cause.

What should I send my host when I ask for help?

Send the exact error code, the full domain, the time you first saw the error, and the steps you already tried. Add whether the error affects every visitor or only one device, and whether the site works without Cloudflare. Those details help support check the certificate, TLS settings and server logs without asking for the same facts twice.

Sources

  1. Get help with common error messages in Chrome Google Chrome Help
  2. Encryption modes Cloudflare SSL/TLS docs
  3. FAQ Let's Encrypt
  4. HTTPS WordPress Developer Resources
  5. Improved HTTPS detection and migration in WordPress 5.7 Make WordPress Core

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