Plugin Author
Mark
(@markwolters)
It’s possible that the .htaccess rule is wrapped in an if module:
<IfModule mod_rewrite.c>
//redirect code
</IfModule>
This means the redirect is only ran when the mod_rewrite.c module is enabled in the server configuration. It’s possible your server doesn’t have this module enabled and therefore the redirect fails.
Is it possible that this applies for one or two websites only? I mean, can htaccess be modified for each website separately? Sorry for newbie qeustions, I’m a designer. 😉
Plugin Author
Mark
(@markwolters)
That’s certainly possible, each site has their own .htaccess file and server configuration. If one of the server configuration is different from the other (for example missing the mod.rewrite module), then this can happen. Your hosting provider can tell you if the module is enabled or not.
Ok, you are right. Htaccess files are really different.
I did a quick comparison and compared the wordpress section.
I also tried to copy the code to “non working” environment but it didn’t help.
This is wordpress section of the code from the site that is working OK:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^/\.well-known/cpanel-dcv/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/(?:\ Ballot169)?
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Sectigo\ DCV)?$
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/\.well-known/cpanel-dcv/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/(?:\ Ballot169)?
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Sectigo\ DCV)?$
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
This is the section from the site where it does not redirect to https:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} !^/\.well-known/cpanel-dcv/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/(?:\ Ballot169)?
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Sectigo\ DCV)?$
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/\.well-known/cpanel-dcv/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/(?:\ Ballot169)?
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Sectigo\ DCV)?$
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Do you have the .htaccess redirect in settings/ssl/settings enabled?
If you either do not have this option, or it’s not possible to enable it, you can also manually insert the redirect, by following these instructions:
https://really-simple-ssl.com/knowledge-base/manually-insert-htaccess-redirect-http-to-https/
In this case it is disabled (we are talking force redirect, yes?)
If i enable it then redirect is working fine. I have no problem enabling it but I fear somehow it may interfere with your plugin …
I’m not sure I understand you. The redirect in settings/ssl/settings, “enable .htaccess 301 redirect” is from this plugin, so it cannot interfere with it. Or od you mean something else.
If you are on https, a redirect to https cannot cause any issues.
I meant force https in cPanel.
Anyway, I solved the problem.
WP Cache plugin was causing this. I moved some sites to another server and there were some old paths in .htaccess.
I uninstalled and reinstalled the plugin and now everything is working fine.
The only thing left is the message “301 redirect to https set: .htaccess redirect” which isn’t available at one of the sites. I can’t enable this in your plugin settings as well (well, actually I can, but when the site is refreshed it’s back to off). But since everything is working fine I don’t really care. 😉
Sorry for wasting your time!
-
This reply was modified 4 years, 8 months ago by
Rico.
I know of one plugin which causes an issue when saving settings in Really Simple SSL: Amazon Associates Link Builder, do you have that enabled?
No, I don’t have Amazon Associates Link Builder.
But I tried this setting (Enable WordPress 301 redirection to SSL) on two of my other sites and they didn’t save either.
I guess one of your plugins is preventing the saving. Can you post a list of your plugins? Then we’ll investigate which one is causing the issue.
Thanks, we’ll investigate.
