If you didn’t enable the .htaccess redirect in your site, you may see a new plus one, with a notice in your dashboard (since version 3.2) WordPress 301 redirect enabled. We recommend to enable the .htaccess redirect option on your specific setup. This setting is not enabled by default, because on some setups you may …
I recently came across an issue where the AutoSSL let’s encrypt plugin can’t verify the domain. Strange though it may seem, this tool needs to access the website over http to renew the SSL certificate. A solution can be to disable the .htaccess redirect, renew, then enable again, but this is not a very elegant …
After you enable Really Simple SSL, by default a PHP redirect is activated, which is called wp 301 redirect in the plugin. If you notice your site can still be reached over http://, possibly the redirect does not work because the site is cached. If you’re using Apache or litespeed, the best redirect method is …
If you are running multiple single site WordPress websites in one hosting account, where you redirect to the correct domain using htaccess code like the example this: 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 …
If you have several subdomains, or add-on domains, but do not use WordPress Multisite, you’ll need a way to prevent Really Simple SSL from forwarding all subdomains to https. That is, if these subdomains do not have an SSL certificate of course. 1. In settings/ssl, disable the wp redirect, and enable the .htaccess 301 redirect. …