really simple SSL 500 internal Server error

  • Resolved aaddoe

    (@aaddoe)


    2 years ago

    Hi, I have the same problem since the really simple was updated 6. 04 I think.

    I have a 500 internal server error.

    I try to reinstall the old version of the plugin or to write on the htaccess file but it doesnt work.

    # BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

    I’m not a webmaster and I manage my website alone.
    Could you help me ?

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

    (@rogierlankhorst)

    @aaddoe and if you remove all lines in the .htaccess? Can you then access /wp-admin again?

    Thread Starter aaddoe

    (@aaddoe)

    Yes, it works !

    So, now I can see its the 6.0.4 version.
    And it’s written there is a new one (6.0.5).

    So I must wait until there is another one ?

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    The 6.0.5 version prevents this issue from happening again. So you can update.

    To reset your .htaccess file, please go to settings/permalinks and save the settings.

    Thread Starter aaddoe

    (@aaddoe)

    Ok.

    I don’t understand:
    To reset your .htaccess file, please go to settings/permalinks and save the settings.

    Where do I go ? In the WordPress settings ?

    Plugin Support Aert Hulsebos

    (@aahulsebos)

    Hi @aaddoe, Yes,

    WordPress Settings -> Permalinks & Save

    regards Aert

    Thread Starter aaddoe

    (@aaddoe)

    Thanks a lot Aert and Rogier.

    I appreciate your help.

    Regards

    Thread Starter aaddoe

    (@aaddoe)

    Hi,

    It’s happened again…

    I delete all the line about really simple. And after a while the 500 internal error appear.
    Is there a way to solve this problem ?
    Do you plan to make an update ?

    If I desactivate the pugin, there will be others problems I suppose.

    Thread Starter aaddoe

    (@aaddoe)

    I use Wordfence and Short Pixel.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    This is the 6.0.5 version you have the issue with?

    Thread Starter aaddoe

    (@aaddoe)

    Yes

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    I have created a new version which removes the upgrade process for the .htaccess, and uses another method to prevent simultaneous upgrades:

    https://github.com/Really-Simple-Plugins/really-simple-ssl/compare?expand=1

    Hope this resolves the issue for you.

    Thread Starter aaddoe

    (@aaddoe)

    Thanks, but I don’t understand what to do with your link.

    Sorry I’m beginner :-/

    The strange thing : it was when I wanted to write a post that it didn’t work.
    Since I changed the file again, and since I don’t do anything, nothing happened.
    The site is OK.
    The problem seems to exist when I want to write a post.

    Thread Starter aaddoe

    (@aaddoe)

    Hi Rogier,

    I upgraded to 6.0.7 and there is no problem since 20 min.
    I’m crossing the finger that it continues… (yesterday, after a while it crashed again).

    Thanks for your help

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Hi @aaddoe thanks for your feedback.
    Multiple users are confirming the issue is resolved now. So I think we’re good now.

    Sorry again for the trouble. We’re still investigating which plugin the conflict was with, to ensure this doesn’t happen again.

    Thread Starter aaddoe

    (@aaddoe)

    I sent you the list of my plug in, by e-mail.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘really simple SSL 500 internal Server error’ is closed to new replies.