Hello,
I am also having problems, have you found a solution?
https://www.gezipgeliyorum.com
Thanks for joining in! No solution. I will publish it here should it appear.
Hi @aclassifier,
Have you already clicked the Activate SSL button in the Really Simple Security Dashboard, as this will enforce HTTPS on your site?
If so, but things don’t seem to work as expected yet, you can try switching from the standard 301 PHP Redirect (WordPress redirect) to a 301 .htaccess redirect.
Kind regards, Jarno
Yes, it’s on “301 PHP redirect”. I don’t dare to change that, do I?
My top level (above /home of WordPress) .htaccess file looks like this:
#Rewrite everything to https
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Hi @aclassifier,
Okay, so you’re currently using a .htaccess redirect from HTTP to HTTPS other than the one added by this plugin? This didn’t immediately become clear to me from your initial post, I thought your question related to the 301 .htaccess redirect from this plugin.
You could try switching to the plugin’s 301 .htaccess redirect instead. The plugin’s version is slightly more robust with a check to ensure that mod_rewrite is available before applying the rule; and uses a case-insensitive HTTPS check.
While the .htaccess redirect shouldn’t cause issues you can always follow these steps to revert the change (https://really-simple-ssl.com/remove-htaccess-redirect-site-lockout/) if that does turn out to be necessary.
Kind regards, Jarno
@jarnovos thanks. I didn’t really know what the problem was, so I guess it was hard to describe the problem. But I guess an experienced user may diagnose this fast when opening and pressing the links in those two sites I mentioned.
It may be a good idea (if you do have the time) to see if my three bullet points in the initial list are correct observations before I attempt a change..
Hi @aclassifier,
I’ve reviewed the points you provided, but I am not entirely sure whether I fully understand all of them.
From what I can see you’re currently not using the 301 .htaccess redirect provided by Really Simple Security; and as your question seems to concern a redirect rule that isn’t set by (or managed through) this plugin, this makes it quite difficult for me to accurately diagnose or address the behavior you’re seeing.
While I’m happy to provide support for features within the Really Simple Security plugin, I am not able to fully assist you with debugging configurations ‘outside’ of the plugin’s scope.
I’d try either temporarily disabling your custom redirect and enabling the 301 redirect through Really Simple Security to see if it fixes your issue. You can test your http:// URLs in a tool such as https://redirect.li/ to see if they are properly being redirected to https://, so you can be sure it is not a browser related problem.
Kind regards, Jarno
Thanks for your time! I really appreciate it! That’s right, I wasn’t clear enough on the fact that I did not dare to switch to “301 .htaccess redirect” provided by Really Simple Security, but kept the “301 PHP redirect”, also by you.
The https://redirect.li/ is interesting:
http://www.teigfam.net/oyvind/home was kept by two routers by one.com but on the third in fact “Redirected by WordPress – Really Simple Security” to https. To me it looks like you are doing your job.
But then, above WordPress, at http://www.teigfam.net/oyvind it is also redirected to https, now already by the first of the three routers!
Plus today even point 3 in https://www.teigfam.net/oyvind/tst/http_and_https.html showed up as https.
I will contact one.com and hear what they say. I am blank. I am not even certain any more if I have a problem… Or do I?
-
This reply was modified 1 year, 4 months ago by
aclassifier. Reason: typo
Hi @aclassifier,
While those URLs indeed seem fine at first glance, you could always reach out to your host and ask them to review your configuration.
Just to further clarify the difference between these redirects: the .htaccess redirect (such as the one you’ve configured manually) happens at the server level, so before WordPress is even loaded. And the 301 PHP redirect (the one that you currently have enabled in this plugin) occurs later in the process, after WordPress has loaded. This means that if a .htaccess redirect is in place, it will always take precedence over the PHP redirect.
Kind regards, Jarno
