Title: Cloning Problems
Last modified: December 25, 2018

---

# Cloning Problems

 *  Resolved [TheViv](https://wordpress.org/support/users/octotoot/)
 * (@octotoot)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/cloning-problems/)
 * Seems to be a problem when having Really Simple SSL activated and then cloning
   the site – all kinds of havoc occurs on clone site. When I disabled it, problem
   goes away. I am using ManageWP for cloning. Thoughts?

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Contributor [Rogier Lankhorst](https://wordpress.org/support/users/rogierlankhorst/)
 * (@rogierlankhorst)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/cloning-problems/#post-11024998)
 * Hi [@octotoot](https://wordpress.org/support/users/octotoot/),
 * Do you have some more details on the problems you are experiencing?
 * Without such details I have to guess. But my first guess would be that your destination
   site does not have an SSL certificate, or that the server setup is different.
   If there is no SSL certificate, there are several solutions:
 * – install a certificate on the destination site
    – use a remote deactivation 
   procedure ([https://really-simple-ssl.com/knowledge-base/uninstall-websitebackend-not-accessible/](https://really-simple-ssl.com/knowledge-base/uninstall-websitebackend-not-accessible/))–
   Deactivate Really Simple SSL before cloning
 * In case of a different server config, there can be several causes: for example
   if the current server needs a .htaccess redirect with RewriteCond %{HTTPS} !=
   on [NC] but the destination server uses RewriteCond %{HTTP:X-Forwarded-Proto}!
   https, this could lead to redirect loops if you just copy the site.
 * So generally speaking, if the server is completely different, it might be better
   to deactivate the plugin, then do a fresh activation so the plugin can detect
   the server setup and configure accordingly.
 * If you can provide me with more details, I might be able tell you more.
 *  Thread Starter [TheViv](https://wordpress.org/support/users/octotoot/)
 * (@octotoot)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/cloning-problems/#post-11030661)
 * This is a clone site. Sits on same server. I will disable SSL when I clone.
 *  Plugin Contributor [Rogier Lankhorst](https://wordpress.org/support/users/rogierlankhorst/)
 * (@rogierlankhorst)
 * [7 years, 4 months ago](https://wordpress.org/support/topic/cloning-problems/#post-11030682)
 * If the domain is a subdomain, for example staging.domain.com, you probably don’t
   have an SSL certificate on the subdomain: this would require a wildcard certificate.
   Disabling SSL will then resolve the issue.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Cloning Problems’ is closed to new replies.

 * ![](https://ps.w.org/really-simple-ssl/assets/icon-256x256.png?rev=2839720)
 * [Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)](https://wordpress.org/plugins/really-simple-ssl/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/really-simple-ssl/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/really-simple-ssl/)
 * [Active Topics](https://wordpress.org/support/plugin/really-simple-ssl/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/really-simple-ssl/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/really-simple-ssl/reviews/)

## Tags

 * [clone](https://wordpress.org/support/topic-tag/clone/)

 * 3 replies
 * 2 participants
 * Last reply from: [Rogier Lankhorst](https://wordpress.org/support/users/rogierlankhorst/)
 * Last activity: [7 years, 4 months ago](https://wordpress.org/support/topic/cloning-problems/#post-11030682)
 * Status: resolved