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

Troubleshooting Common HTTPS Redirect Issues with Really Simple SSL

41 threads Sep 7, 2025 Plugin → Really simple security

Content

Getting your WordPress site to properly redirect all HTTP traffic to HTTPS is a crucial step in enabling SSL. While the Really Simple SSL plugin automates much of this process, certain server configurations or conflicts can prevent redirects from working as expected. This guide covers the most common redirect problems and their solutions, based on community reports and resolutions.

Why Your HTTP to HTTPS Redirect Might Not Be Working

If you've activated Really Simple SSL but your site isn't redirecting, or you're seeing errors like ERR_TOO_MANY_REDIRECTS, the cause is usually one of the following:

  • Caching: A page or server cache is serving an old, non-redirected version of your site.
  • Incorrect Redirect Method: The default WordPress redirect may not be sufficient for your server setup.
  • Server Configuration: Your server (especially NGINX or complex setups like NGINX -> Apache) may handle rewrite rules differently.
  • Conflicting Rules: Other rules in your .htaccess file might be interfering with the SSL redirect.
  • Domain/WWW Configuration: A mismatch between your WordPress Address (URL) and the domain being accessed can break redirects.

How to Fix HTTPS Redirect Issues

Follow these steps to diagnose and resolve the problem.

1. Clear All Caches

This is the most common fix. Clear your WordPress caching plugin's cache, your browser cache, and any server-level cache (e.g., Varnish, OPcache). Always test redirects in a private/incognito browser window afterward.

2. Enable the .htaccess Redirect

The plugin offers two primary redirect methods. If the default "WordPress redirect" isn't working, the more powerful .htaccess redirect often is.

  1. Go to SSL → Settings in your WordPress dashboard.
  2. Locate the "Enable 301 .htaccess redirect" option.
  3. Enable it and save your settings.
  4. Clear your cache again and test.

3. Check Your WordPress URL Settings

WordPress will redirect to the URL defined in its settings. If your www and non-www traffic aren't consolidating, check this first.

  1. Go to Settings → General.
  2. Ensure both the WordPress Address (URL) and Site Address (URL) are set to your preferred version, either https://example.com or https://www.example.com.

4. Verify .htaccess File Integrity

If you have access to your site's files, check the .htaccess file. The Really Simple SSL rules should be placed above the standard WordPress rewrite block. In some cases, especially with multi-site or subfolder installations, the plugin's rules might not be placed correctly, leading to redirect loops or failed redirects for specific paths. Manually ensuring the rules are at the top of the file can resolve this.

5. Complex Server Setups (NGINX, etc.)

Really Simple SSL primarily manages Apache's .htaccess files. If your site runs on NGINX alone or behind an NGINX proxy (e.g., NGINX -> Apache), the plugin cannot edit the NGINX configuration file. You will need to manually add the redirect rules to your NGINX server block. A basic rule looks like this:

server {
    listen 80;
    server_name example.com www.example.com;
    return 301 https://example.com$request_uri;
}

6. Force Deactivation for Migration

If you are moving your site from HTTPS to HTTP, the plugin will try to force HTTPS. To cleanly revert to HTTP, you need to use the plugin's force deactivation method. The Really Simple SSL team provides a guide on how to force deactivation when you cannot access your dashboard.

When the Issue Isn't Really Simple SSL

Sometimes, the redirect problem is related to a broader configuration issue:

  • Old Domain SSL Certificates: Redirecting an old HTTP domain to a new HTTPS domain requires that the old domain also has a valid SSL certificate if the redirect passes through an HTTPS connection, otherwise browsers will show a certificate error.
  • External Redirects: Redirects set up at the DNS or server level (e.g., in cPanel) will take precedence over WordPress rules. Check with your host if you have conflicting redirects.

By methodically working through these solutions, you can identify and resolve the barrier preventing your site from correctly forcing HTTPS connections.

Related Support Threads Support