Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter rjt1985

    (@rjt1985)

    The reason I’m asking you about this is because your plugin is the only thing writing to my htaccess file, and my host believes that the problem lies in rewrites.

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Hi,

    All SSL redirects only take effect when the site is requested over http. So if you change the cron url to https, an SSL redirect no longer happens. All .htaccess redirects by Really Simple SSL are 301 by the way.

    As WordPress redirects your site to the preferred url, you should check that your provider uses the preferred url. For example, if your home_url is https://www.domain.com, do not use https://domain.com, but the one with www.

    Thread Starter rjt1985

    (@rjt1985)

    Thanks for the reply! I’ve asked my host and they have replied with the following…

    “Makes sense, but we’re not calling the cron via http but via the command line – so that isn’t the issue. Does the plugin do anything other than use the .htaccess?”

    I’d appreciate any light you could shed on this.

    R

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    You could deactivate the plugin, which would remove any edits made, and then check if it starts working. If not, try deactivating the other plugins one by one. Redirects can also be done in the WordPress itself.

    Do you maybe use a hide my wp plugin or something like that? I found a thread where the rewriting of the default wp folders caused this problem. Other possible causes: a security, caching, redirection or multilanguage plugin.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Really Simple SSL affecting cron job?’ is closed to new replies.