Troubleshooting
Really Simple SSL Not Working: Causes and How to Fix It

Short answer
Really Simple SSL usually fails because there is no valid SSL certificate for your domain, a CDN such as Cloudflare in Flexible mode causes a redirect loop, mixed content remains on pages, or older redirect rules clash with the plugin. Confirm the certificate works before you activate HTTPS.
Key takeaways
- The plugin needs a valid certificate on your server or CDN first.
- Cloudflare Flexible mode often causes redirect loops; use Full or Full (strict).
- Rename the plugin folder over FTP if you get locked out.
- Turn on the mixed content fixer and remove hard-coded http links.
- Keep only one HTTP to HTTPS redirect across server, CDN and plugins.
Why is Really Simple SSL not working?
Really Simple SSL usually fails because no valid SSL certificate is installed, a CDN or proxy causes a redirect loop, mixed content remains, or old redirect rules clash with the plugin's own.
The plugin, now called Really Simple Security on WordPress.org, switches a WordPress site to HTTPS. It changes your site URLs, adds a redirect from HTTP to HTTPS and fixes insecure links in your pages.
What it cannot do on its own is make an invalid certificate valid. It relies on a working certificate on your server or CDN.
Common symptoms:
- The plugin says no SSL certificate was detected
- The site shows too many redirects after activation
- The padlock is missing or shows a warning
- You are locked out of the admin after enabling HTTPS
- Some pages load on HTTP and others on HTTPS
If you have not set the plugin up yet, start with our guide on how to install Really Simple SSL.
Do you have a valid SSL certificate?
The plugin needs a working certificate for your exact domain, so open your site with https in a browser and confirm the padlock appears before you activate HTTPS.
A certificate must cover the address visitors use. A certificate for example.com may not cover www.example.com unless both are included.
Check:
- Visit your site with https in front
- Click the padlock and view the certificate
- Confirm the domain names and expiry date
Most hosts offer free certificates from Let's Encrypt in their control panel. Turn it on there and wait for it to issue. Some hosts take a few minutes, others longer.
Do not activate HTTPS in the plugin until the certificate shows as valid in your browser. Enabling it too early is the most common way people lock themselves out.
Our guide on how to install an SSL certificate on WordPress covers the host side in detail.
Why do you get a redirect loop after activating?
A loop usually happens when a CDN or proxy talks to your server over HTTP while the plugin forces HTTPS, so each side keeps redirecting the other.
The classic case is Cloudflare's Flexible SSL mode. Visitors reach Cloudflare over HTTPS, but Cloudflare connects to your server over HTTP.
The plugin sees an HTTP request and redirects to HTTPS. Cloudflare passes it back as HTTP. The loop never ends.
Fix it by setting Cloudflare to Full or Full (strict) with a valid certificate on your server. Cloudflare explains each option in its SSL/TLS encryption modes documentation.
Other causes include load balancers, reverse proxies and some managed hosts that end HTTPS before WordPress. The plugin's own guide to fixing a redirect loop lists the settings to check.
Our guide on Cloudflare SSL settings for WordPress explains each mode in plain terms.
For loops caused by something other than SSL, see our guide on fixing too many redirects.
How do you get back in if you are locked out?
Deactivate the plugin without the dashboard by renaming its folder over FTP or your host's file manager, then fix the cause before reactivating.
Steps:
- Connect with FTP or open your host's file manager
- Go to wp-content/plugins
- Rename the really-simple-ssl folder, for example by adding -off
- Load your admin over http
Renaming the folder stops WordPress loading the plugin. Some changes, such as redirect rules in .htaccess or URLs saved in settings, may stay in place. Check both.
Then clear your browser cache before you test again. Browsers remember HTTPS redirects, so an old redirect can keep sending you to the broken address even after you fix it.
The plugin's documentation also describes its own deactivation method for lockouts. Our guide on deactivating plugins without admin access covers the general method.
Why does the padlock still show a warning?
A missing or broken padlock usually means mixed content: the page loads over HTTPS but some images, scripts or styles still load over HTTP.
Browsers block or flag insecure resources on secure pages. MDN's article on mixed content explains what is blocked and why.
Really Simple SSL has a mixed content fixer. Make sure it is turned on in the plugin settings.
If warnings remain:
- Check theme options and page builder settings for hard-coded http URLs
- Look in custom CSS for background images using http
- Check widgets and custom HTML blocks
- Update external embeds to their https versions
Use your browser's developer tools Console tab to see exactly which files are insecure. Our guide on fixing mixed content warnings covers a database search-and-replace for stubborn cases.
Could old redirect rules conflict with the plugin?
Yes, older HTTPS redirects in .htaccess, your host panel or another plugin can clash with Really Simple SSL and cause loops or double redirects.
Keep one HTTP to HTTPS redirect. Check:
| Place | What to look for |
|---|---|
| .htaccess | RewriteRule lines forcing https |
| Host panel | A force HTTPS toggle |
| CDN | Always Use HTTPS or redirect rules |
| Other plugins | Security or SEO plugins with HTTPS options |
The plugin can write its own redirect to .htaccess on Apache servers. If you already have one, remove the duplicate. Back up the file before editing it.
Are your WordPress URLs set to https?
Your WordPress Address and Site Address must both use https, otherwise links, logins and redirects can switch back to HTTP.
The plugin normally updates these for you. Check Settings > General to confirm. If the fields are greyed out, they are set in wp-config.php, and you need to edit them there.
WordPress documents these settings on its General Settings page.
Also check any hard-coded URLs in wp-config.php. Old WP_HOME or WP_SITEURL lines with http override the dashboard.
Could caching show the old HTTP version?
Yes, page caches and CDNs can keep serving pages built before the switch, so clear every cache after enabling HTTPS.
Clear your caching plugin, your host's cache and your CDN. Then test in a private window.
If you use a minification or optimization plugin, regenerate its files. Combined CSS and JavaScript files may still reference http URLs.
Some hosts also run their own cache in front of WordPress. Look for a purge button in your hosting panel, or ask support to clear it for you.
What other errors can stop HTTPS working?
Certificate mismatches, expired certificates and old TLS settings can cause browser errors that no WordPress plugin can fix.
If you see ERR_SSL_PROTOCOL_ERROR or a certificate name warning, the problem is on the server or CDN. Our guide on fixing ERR_SSL_PROTOCOL_ERROR covers the server side.
Contact your host if the certificate will not issue or renew. They can see validation errors that are hidden from you.
How do you confirm the fix worked?
Load several pages in a private window over HTTP and HTTPS, confirm each ends on HTTPS with a padlock, and check the browser console for warnings.
Test the home page, a post, a page with images and the login page. Each HTTP address should redirect once to its HTTPS version.
Online checkers can scan pages for insecure files. Re-test after theme or plugin updates, since new content can bring http links back.
Finally, update your site address in Google Search Console and any analytics tools. Add the HTTPS version as a property if you use a URL-prefix property, so reports keep working after the switch.
Frequently asked questions
Does Really Simple SSL install an SSL certificate?
Its main job is moving WordPress to HTTPS once a certificate exists. Most hosts provide free certificates in their control panel. Install and confirm the certificate first, then let the plugin handle the switch.
Why does my site show too many redirects after enabling SSL?
A proxy or CDN is usually sending HTTP requests to your server while the plugin forces HTTPS. Set Cloudflare to Full or Full strict, and remove duplicate HTTPS redirects elsewhere.
How do I disable Really Simple SSL without the dashboard?
Use FTP or your host's file manager to rename the plugin's folder in wp-content/plugins. WordPress then stops loading it. Check .htaccess and your site URLs, since some changes may remain.
Why is the padlock still missing after the switch?
Some files still load over HTTP. Turn on the plugin's mixed content fixer, then check theme options, custom CSS and embeds for http links. The browser console lists the exact files.
Is Really Simple SSL the same as Really Simple Security?
Yes. The plugin was renamed Really Simple Security and added more security features, but it still handles the SSL and HTTPS tasks it was known for.
Sources
- Really Simple Security plugin WordPress.org Plugins
- My website is in a redirect loop Really Simple Plugins
- SSL/TLS encryption modes Cloudflare Docs
- Mixed content MDN Web Docs
- Let's Encrypt documentation Let's Encrypt
- General Settings screen WordPress.org Documentation
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.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


