BugWP logo BugWP
Back to Community
Home / Community / Plugin → Really simple security

Troubleshooting Common Issues After a Really Simple SSL Update

26 threads Sep 16, 2025 Plugin → Really simple security

Content

Updates to the Really Simple SSL plugin are designed to improve security and functionality. However, like any software update, they can sometimes introduce unexpected behavior or conflicts on certain WordPress configurations. Based on community reports, this guide covers the most common post-update issues and their solutions.

Common Post-Update Issues & Solutions

1. Website Slowness or Performance Issues

The Problem: After an update, your site's front-end, back-end, or both may become noticeably slower.

Why It Happens: Performance hits can be caused by several factors. A new feature might be consuming more resources, a specific server configuration might conflict with a new process, or there could be a temporary issue with an external server the plugin communicates with.

How to Fix It:

  • Check for Debug Mode: Ensure that WP_DEBUG or SCRIPT_DEBUG is not enabled in your wp-config.php file, as this can significantly impact performance.
  • Review Enabled Features: New hardening or security features enabled by default in an update might be resource-intensive. Try disabling non-essential features one by one in the plugin's settings to identify the culprit.
  • Server Load: In rare cases, a traffic spike to the plugin's own server after a major update can cause temporary slowdowns. This typically resolves itself quickly.

2. Redirect Loops or 'Too Many Redirects' Errors

The Problem: Your site becomes inaccessible, showing a "Too Many Redirects" error in the browser.

Why It Happens: This is often related to how SSL redirection is handled. An update might change the redirection method or conflict with existing redirect rules in your .htaccess file or a caching service like Cloudflare.

How to Fix It:

  • Check Cloudflare Settings: If you use Cloudflare, ensure your SSL/TLS encryption mode is set to "Full (strict)" and that you are not creating conflicting redirect rules within Cloudflare itself.
  • Revert to .htaccess Redirection: In the Really Simple SSL settings, navigate to SSL → Settings and enable the ".htaccess redirect" option if available. This method is more efficient and less prone to loops than a PHP redirect.
  • Manually Deactivate: If you cannot access your admin area, deactivate the plugin by renaming its folder (from really-simple-ssl to something like really-simple-ssl_OFF) via FTP or your hosting file manager.

3. Conflicts with Other Plugins or Themes (e.g., Elementor, Checkout Plugins)

The Problem: After an update, another plugin (like a page builder or e-commerce tool) or your site's menus stop working correctly.

Why It Happens: New security hardening features can sometimes be overly broad, blocking scripts or processes that other plugins legitimately need to run.

How to Fix It:

  • Disable Hardening Features: Go to SSL → Hardening in your WordPress admin. Try disabling features like "Prevent PHP execution" or "Disable plugin and theme editing" to see if it resolves the conflict.
  • Conflict Test: The most reliable way to confirm a conflict is to temporarily disable all other plugins and switch to a default WordPress theme (like Twenty Twenty-Four). If the issue stops, reactivate your plugins and theme one by one to find the incompatible software.

4. Plugin Cannot Be Deleted or Reappears

The Problem: You try to delete the plugin, but it reappears after a page refresh, or you receive constant update failure emails.

Why It Happens: This is a sign of a corrupted plugin installation or file permission issues that prevent WordPress from completing the deletion process.

How to Fix It:

  • Manual Deletion via FTP: Bypass the WordPress admin entirely. Connect to your site via FTP/SFTP, navigate to the /wp-content/plugins/ directory, and delete the entire really-simple-ssl folder. This is the most effective solution.

5. Quarantined Plugins

The Problem: A feature quarantines a potentially vulnerable plugin but doesn't properly restore it after the issue is fixed.

How to Fix It:

  • Manual Rename: Use FTP or your file manager to navigate to /wp-content/plugins/. Find the quarantined plugin's folder (it will have a changed name), and rename it back to its original directory name. You can then reactivate it from the Plugins page.

General Troubleshooting Steps

For any issue after an update, follow these steps first:

  1. Clear Caches: Clear your browser cache, any WordPress caching plugins, and your server-side cache (if applicable).
  2. Check for Errors: Check your browser's JavaScript console (F12) for errors and your server's PHP error logs for any relevant messages.
  3. Reinstall: Delete the plugin and install a fresh copy from the WordPress repository.

If problems persist, the WordPress support forums can be a valuable resource to see if others are experiencing the same issue and to find community-driven solutions.

Related Support Threads Support