Category: SSL & HTTPS
Remove .htaccess redirect on site lockout
The .htaccess is the fastest redirect, so why not enable it by default? When you enable the setting “301 .htaccess redirect” under SSL & Security -> “Settings” in the top menu bar -> SSL, Really Simple SSL will detect the most suitable redirect and then opens a test page to verify if this option won’t result in redirect loops. Even so, the detected redirect could cause a loop: there are a lot of server configurations, and some respond unexpectedly to
Redirection to subfolder domains redirects to https://www.domain.com/domain.com
If you are running multiple single-site WordPress websites in one hosting account, where you redirect to the correct domain using htaccess code like in this example: RewriteEngine on RewriteCond $1 !domain/ RewriteCond %{HTTP_HOST} ^domain.com$ [NC,OR] RewriteCond %{HTTP_HOST} ^www.domain.com$ RewriteRule (.*) /domain/$1 [L] The default Really Simple SSL redirect in combination with this code might cause a redirect that ends up like this: https://www.domain.com/domain.com To solve this, you have to add some lines to the .htaccess in your root folder. The root
My website is in a redirect loop
When you experience a redirect loop (the browser shows the “too many redirects” or ERR_TOO_MANY_REDIRECTS error), this can be caused by several things, I’ve listed the most common causes below. Most checks can be done without access to the back-end. If these steps all fail, and you still have a redirect loop, you can try to activate Really Simple SSL in safe mode. This will activate Really Simple SSL without a redirect and without your site URL becoming https. If all
Redirect loop in WordPress admin only, not on front end
WordPress depends on a variable, $_SERVER[“HTTPS”] to check if it is on SSL. As a consequence, when this variable is not set and SSL is forced, WordPress tries to redirect back to http. This causes redirect loops on the back-end only, and not on the front-end. Really Simple SSL fixes this by adding $_SERVER[“HTTPS”] = “on”; to your wp-config.php. If you have activated Really Simple SSL, enabled SSL, and still have this issue: something might have gone wrong with the
www not redirecting to non-www on Cloudflare
Recently I encountered an interesting issue with redirection from www to non-www. The non-www site worked perfectly after migration to SSL, but the www site gave a 404 Not Found error or an SSL server error. The issue was eventually resolved by the hosting company. If a user has connected a site to Cloudflare using the service offered by many hosting providers within Cpanel, then ONLY the domain at the root will be used. If you have installed your site