Really Simple SSL broke my website

Hello, Ron.
I had same problem with this plugin 1 week ago, so, what I did :
1. Edited config.php
2. Checked database
After this manipulations I got access at : website/wp-login.php?itsec-hb-token=wplogin
Try it

Seva
P.S. Link to website isn’t working, because of this I couldn’t check it myself

• This reply was modified 4 years, 5 months ago by sewaca.

Thank you @sewaca unfortunately that doesnt work for me. It immediately pushes me to the https version and i get an error saying this page isnt working

Hi @mxgphistory,

your site currently returns a 403 forbidden error. This indicates something is blocking access to the site over https://. Usually the force-deactivate.php should force your site back to https://. It could be there’s an additional method of forcing SSL active. Could you post or send us the contents of your .htaccess file so we can have a look? Do you use a CDN on the site? Your hosting provider or CDN might also have an option to force the site over https://. Could you check if that is unchecked?

hello @markwolters thank you for your quick reply.
As i said i could not be able to bring the site back to http with force-deactivate.php
I might be doing something wrong since i never do this kind of stuff, but i’m pretty sure i followed the steps as described.

The content of the htaccss file is:
# 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
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
</IfModule>
# END WordPress
# BEGIN LiteSpeed
# The directives (lines) between “BEGIN LiteSpeed” and “END LiteSpeed” are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule Litespeed>
SetEnv noabort 1
</IfModule>
# END LiteSpeed

I did not know what CDN is before you mentioned it, but looked it up and i did not install a plugin for this. I also quickly checked the theme i’m using if there is any reference to CDN and there is not.

As for the opt to force the site via the hosting provider:
I use directadmin.
under SSL, there is the option “Force SSL with https redirect”, which is unchecked.
Under domain setup i have ‘no redirection’ under ‘Force redirect’, and under ‘private-html setup’ i have ‘use a directory named private_html’, and ‘force ssl with https redirect’ is unchecked.

Thank you for your help.

Ron

@mxgphistory your .htaccess file still contains a redirect to https://. Could you try to remove the following lines to see if that resolves the issue:

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

The redirect to https:// generally shouldn’t be inserted in the WordPress block. Really Simple SSL adds it outside the WP block. Possibly a different plugin has entered the redirect in that place.

Hello thanks for the quick reply. I removed the text, but nothing has changed. I still get the error.

Ron

@mxgphistory the website doesn’t redirect to https:// anymore but doesn’t work correctly. It currently returns an internal server error. To find out what is causing this exactly, you could enable debugging in WordPress by adding the following to your wp-config.php file:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);

This can write a more detailed error to a debug.log file in the /wp-content/ folder which can provide more information about the exact cause of the current issue.

Ok edited the wp-config file, however where can i find this log, because there is no file in the wp-content folder

edit: no new file with a log, there are obviously some files and subfolders in this folder

• This reply was modified 4 years, 5 months ago by mxgphistory.

@mxgphistory if there’s no debug.log file in the /wp-content/ folder, the server error it not caused by a PHP related error. I’d suggest to contact your hosting provider about this, they will be able to check what is causing the issue.

Ok, i will contact the hosting provider and get back to you.

@mxgphistory in some cases the error logs end up in the root of the website, in an error_log file.

It is also possible the error is in your .htaccess. Please try renaming the .htaccess file to something else, to check if that is the cause.