• Resolved Nick

    (@hellosite)


    Hello,

    There is an issue with the activation of the .htaccess 301 redirection on the PlanetHoster server. I did not have this issue before. This problem occurs even on a fresh website after activating the .htaccess 301 redirection.

    Can you please help me ?

    Best Regards

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    If you load

    https://yourdomain.com/wp-content/plugins/really-simple-ssl/ssl-test-page.php

    (with your domain instead of the example domain)

    What is the result you see there?

    Thread Starter Nick

    (@hellosite)

    Hello @rogierlankhorst

    It show me this page https://prnt.sc/raupEfE4K4ZL

    When I activate this ?.htaccess 301 redirection the plugin’s page also disapear https://prnt.sc/OVi3dVvXz8Q8

    Best Regards

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    This is a pretty normal result, which should lead to the most common htaccess redirect code:

    <IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteCond %{HTTPS} !=on [NC]
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%/$1 [R=301,L]
    </IfModule>

    Can you check which of the below redirects works on your site?

    https://really-simple-ssl.com/manually-insert-htaccess-redirect-http-to-https/

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Please also check if it helps to add

    $_SERVER[ "HTTPS" ] = "on";

    To your wp-config.php

    Thread Starter Nick

    (@hellosite)

    Hello @rogierlankhorst

    I have added the code but it again break the website

    It is a litespeed server

    Plugin Author Mark

    (@markwolters)

    Hi @hellosite,

    could you provide us with the contents of your .htaccess file so we can have a look at what the issue might be?

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @hellosite in addition to that, please also check if any of the other suggested redirects here work:

    https://really-simple-ssl.com/manually-insert-htaccess-redirect-http-to-https/

    If so, please let us know which one so we can take a look at the logic in the plugin leading to the redirect.

    Thread Starter Nick

    (@hellosite)

    Hello @rogierlankhorst

    Unfortunately, it does not works

    But I always use your plugin on my others websites and it works fine

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Nothing has changed in the plugin in regards to .htaccess. And if it works on your other websites, maybe there is a conflict with another plugin.

    If you can share your .htaccess contents here we can take a look.

    Did you mean you tried all .htaccess redirect variants? Because if none of them work, the host has changed something in a way that it doesn’t support .htaccess redirects anymore possibly.

    Either that, or something goes wrong with writing to the .htaccess. In that case, we need to see the .htaccess.

    I haven’t heard of any other issues in the latest version, with an estimated 1 million updates. Which suggests that there’s something very specific to your setup which is causing this.

    If you can share your domain we can check if we see anything else.

    Plugin Support jarnovos

    (@jarnovos)

    Hi @hellosite,

    I’ve marked the thread as resolved as we haven’t heard back from you in a while.

    Let us know if you do require further assistance though. If you additionally share the content of your .htaccess file and your domain, that’d allow us to investigate further.

    Kind regards, Jarno

    Thread Starter Nick

    (@hellosite)

    Hello @markwolters @jarnovos

    Sorry for the delayed response.

    I’m experiencing the same issue with another hosting service, Hostinger.

    I received a response from the PlanetHoster support team regarding the issue with the plugin. Here is their response.”


    ” The “Really Simply Security” plugin detects the environment using a PHP script and since it comes with environment variables like “X-Forwarded(..)”, it assumes that everything is behind a proxy… even though our static files are served upstream without the proxy. “

    To fix this, it is better to add the following line:

    RewriteCond %{HTTPS} !=on

    So the final result would be:

    Begin Really Simple Security

    RewriteEngine on RewriteCond %{HTTP:X-Forwarded-Proto} !https RewriteCond %{HTTPS} !=on RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]

    What do you think about it ? I didn’t tried what they have suggested

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    The suggested code is the same as the “standard” version I posted some comments back. I read in your response on that item that you tried it, and that it didn’t work for you. But I would check if it works, just to be sure.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Issue in the last version’ is closed to new replies.