Website became Really Slow after SSL

Home Forums General issues Website became Really Slow after SSL

This topic contains 74 replies, has 6 voices, and was last updated by  Rogier Lankhorst 1 week, 1 day ago.

Viewing 15 posts - 61 through 75 (of 75 total)
  • Author
  • #95145 Reply

    Mark Wolters

    Hi Chris,

    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).


    #95278 Reply

    Christian Öhrn

    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…

    #95316 Reply

    Mark Wolters

    It’s the ‘Enable .htaccess redirect’ option, that should add the redirect to the .htaccess file.


    • This reply was modified 1 week, 4 days ago by  Mark Wolters.
    #95352 Reply

    Christian Öhrn

    Ok thanks!

    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
    ** 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 https

    #95415 Reply

    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:

    #95665 Reply

    Christian Öhrn

    Hm not to my knowledge! which option in the settings is this?

    The site we are talking about is if you wanna check in pingdom..

    thanks for the link, we will check that

    #95679 Reply

    Mark Wolters

    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.


    #96130 Reply

    Christian Öhrn

    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?

    #96134 Reply

    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.

    #96135 Reply

    Christian Öhrn

    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?

    #96136 Reply

    What type of server are you using? (apache/Nginx/litespeed/IIS)?

    #96137 Reply

    Christian Öhrn

    it should be apache as we use cpanel

    #96293 Reply

    Mark Wolters

    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.


    #96307 Reply

    Christian Öhrn

    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!

    #96553 Reply

    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.
    error_log(print_r($server_raw, true));

    If you add to your wp-config.php (replace the current wp_debug:
    define(‘WP_DEBUG’, true);
    define(‘WP_DEBUG_DISPLAY’, false); //prevents from showing errors on the front-end
    define(‘WP_DEBUG_LOG’, true);

    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.

Viewing 15 posts - 61 through 75 (of 75 total)
Reply To: Website became Really Slow after SSL
Your information: