- May 8, 2018 at 3:01 pm #95145
the free version of Really Simple SSL can also add a .htaccess redirect. You can select the .htaccess redirect option in the plugin settings (Settings->SSL->Settings).
MarkMay 9, 2018 at 10:40 am #95278
Hi again Mark,
Ok well which setting would that be in the settings tab?
I think we have most of the enabled, but the troubleshooting feature still says it is not active…May 9, 2018 at 2:46 pm #95316
It’s the ‘Enable .htaccess redirect’ option, that should add the redirect to the .htaccess file.
May 9, 2018 at 3:25 pm #95352
- This reply was modified 1 week, 4 days ago by Mark Wolters.
but we have this option on and in the troubleshooting section it says: (so i guess it aint right?)
* WordPress redirect
* Mixed content fixer
SSL is enabled for this site
** Detecting configuration **
plugin version: 2.5.26
Already on SSL, start detecting configuration
SSL type: SERVER-HTTPS-ON
** Configuring SSL **
checking if .htaccess can or should be edited…
.htaccess does not contain default Really Simple SSL redirect
retrieving redirect rules
converting siteurl and homeurl to httpsMay 9, 2018 at 9:38 pm #95415
You didn’t enable “stop editing the .htaccess file”? Because that will prevent this insertion.
If the plugin somehow cannot insert the .htaccess redirect, you can also do this manually:
https://really-simple-ssl.com/knowledge-base/manually-insert-htaccess-redirect-http-to-https/May 11, 2018 at 10:08 am #95665
Hm not to my knowledge! which option in the settings is this?
The site we are talking about is wallox.se if you wanna check in pingdom..
thanks for the link, we will check thatMay 11, 2018 at 11:03 am #95679
The ‘stop editing the .htaccess file’ option.
Your site seems to be working fine over SSL. It also redirects http:// to https:// so there seems to be a redirect active currently. The .htaccess redirect option is not required, we do recommend to enable it when possible because it’s the fastest redirect.
MarkMay 13, 2018 at 12:00 pm #96130
hmm i we dont have one of those options i think..
i checked on another site and seems the options in the plugins varies…
The other site had much more options and as well the .htacess option you mention while the other sites dont!
Do you know why this is?May 13, 2018 at 12:27 pm #96134
The options are visible depending on your server. Depending on your server (NGINX, apache, litespeed or IIS), if you disabled file writing permissions on the .htacces, if the server generates a loop on the suggested redirect etc, the plugin will show different options.
In your case I would insert the redirect rules manually.May 13, 2018 at 12:30 pm #96135
Ok great then i know where we should check!
maybe easiest to just enable the permissions on the server, as we have many sites on it… and to do the htacess edit on all might take time and give a bigger chance of errors! or what you think?May 13, 2018 at 12:32 pm #96136
What type of server are you using? (apache/Nginx/litespeed/IIS)?May 13, 2018 at 12:50 pm #96137
it should be apache as we use cpanelMay 14, 2018 at 9:29 am #96293
Apache uses an .htaccess file so you should be able to add the redirect rules manually. You can always create a backup of the current .htaccess file so you can quickly restore it if anything goes wrong.
MarkMay 14, 2018 at 10:28 am #96307
but there must be some form of setting for this so we get the options in the plugin?
as we have about 20 sites on this server to edit all the htacess will take sometime…
I really appriciate all the help thanks!May 15, 2018 at 7:21 am #96553
Apparently your server is not recognised as apache. You could test what it outputs by putting in some logging at the file class-server.php, line 52.
If you add to your wp-config.php (replace the current wp_debug:
define(‘WP_DEBUG_DISPLAY’, false); //prevents from showing errors on the front-end
The server output will get written to wp-content/debug.log
I’m interested what that is. Possibly we can adjust the code somewhat so the plugin recognises your server setup as well.