Hi @woodofspoon,
The “403 Forbidden” warning can appear due to a security tool/restriction on your server which prevents access to the site, although it’s not caused by Really Simple SSL (which is also why it persists upon de-activating the plugin).
Common causes include insufficient file/directory permissions, the .htaccess file containing a certain rule that denies access, IP bans or the server configuration.
Your hosting provider should be able to provide you with further insights regarding the cause of the behavior.
Kind regards, Jarno
this is how .htaccess looks like:
BEGIN WordPress
RewriteEngine On RewriteBase / RewriteRule ^index.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L]
END WordPress
Hi @woodofspoon,
It doesn’t look like this .htaccess currently contains any rules related to Really Simple SSL, and I would therefore expect the plugin to be unrelated to the 403 Forbidden error on your website.
I pasted these rules in my own .htaccess file as well, which didn’t result in the same 403 Forbidden error appearing on my end either. So, my assumption would be that it’s the result of some other configuration.
Your hosting provider can offer additional information and help you understand the cause of the issue.
Kind regards, Jarno
