Live vs. localhost

  • Resolved blueeventhorizon

    (@blueeventhorizon)


    8 years, 1 month ago

    Hi Rogier,

    I am a little nervous to use your plug-in – I tried converting over to https before, lost access to my back-end and experienced a lot of stress until I got my back-up restored.

    Background: I use a localhost installation for development work on my website, accessed via MAMP. I like this, it’s fast and secure, I don’t need internet access and, of course, if I screw-up it is only the dev-site. I use the Duplicator plug-in and FileZilla to migrate back and forth

    Question: If I convert my live site over to https, how does that impact my ability to duplicate my live site, copy it over to my local machine and run it locally using MAMP?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Hi,

    If you copy a live site with Really Simple SSL active to a non-ssl environment, Really Simple SSL will still be active, so your site will be forced over https. To deactivate the plugin without accessing the admin you can use the remote deactivation script:

    https://really-simple-ssl.com/knowledge-base/uninstall-websitebackend-not-accessible/

    Another way is to deactivate the plugin on the live site before making the copy, then make a copy, and then activate it again. But that’s not my preferred method.

    A third method would be to rename the Really Simple SSL plugin folder after you have installed the new copy on http, and remove the .htaccess redirects. Then when you load the site, the plugin won’t change the url’s back to https, because it’s deactivated.

    I guess it depends on your own preferences what’s best for you.

    Thread Starter blueeventhorizon

    (@blueeventhorizon)

    Hi Rogier,

    Thanks for the detailed reply.

    You mention the deactivate-duplicate-reactivate approach, indicating this would not be your preferred procedure. Aside from the risk of forgetting to do it, is there a more fundamental reason you dislike this?

    Another approach is to set up a “dev” subdomain. Can you confirm that I would be able to “set and forget” Really Simple SSL in that scenario.

    Thanks in advance!

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    Well, deactivating the plugin would mean the site would be temporarily available over http, with possible mixed content issues for those who are visiting the site in the meantime. While this is not a great risk/problem, I personally don’t like to edit a live site this way. But it is not harmfull.

    On a dev subdomain you could of course deactivate the plugin without the above issues, then copy the site. But I think you can better just not activate the SSL on the subdomain.

    Thread Starter blueeventhorizon

    (@blueeventhorizon)

    Once again, thanks for your detailed response. It’s very helpful. My site has very low traffic, so switching off SSL for five minutes while I duplicate it is not a big deal.

    I look forward to trying out your plug-in and, hopefully, giving it a 5-star rating!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Live vs. localhost’ is closed to new replies.