Plugin Author
Mark
(@markwolters)
Hi,
cloning while on https:// should work if the new server has an SSL certificate for the domain name. Usually if there are SSL issues when migrating you would see an insecure certificate warning or mixed content. Possibly there’s something else going wrong, I’d suggest to enable debugging in WordPress as described here to get more information about the cause of your issue: https://codex.ww.wp.xz.cn/Debugging_in_WordPress
Do you think it would be okay to temporarily deactivate Really Simple SSL and revert to http then clone the site over to the GoDaddy staging area and activate it again? GoDaddy won’t activate an SSL on a Managed WordPress site until a domain is assigned. We don’t want to do that until the cloning has taken place. So the steps I’m thinking about are:
1. Deactivate Really Simple SSL, revert the existing site to HTTP temporarily.
2. Clone the existing site over to the GoDaddy Managed WordPress site.
3. Make some minor fixes.
4. Push the staging to production.
5. Point / assign the domain name to the production site.
6. Activate the SSL
7. Activate Really Simple SSL
Do you think that would work? Thanks!
Plugin Author
Mark
(@markwolters)
It is ok to temporarily deactivate Really Simple SSL for the migration, do note that having HTTP Strict Transport Security can cause issues on the live site if it’s enabled and the site reverts back to http:// (see https://really-simple-ssl.com/hsts-http-strict-transport-security-good/). Usually you can leave https:// enabled when migrating a site. The white screen might have a different cause, to check what’s causing the white screen you can enable debugging in WordPress, possibly there’s another plugin giving an error on the new hosting environment.
The problem is that the old developer who is giving my client the runaround won’t give us the FTP creds. I only have access to WordPress. Just to give you an idea of what kind of people they are, they quoted my client 36 hours to put a blog page up. I did it in 10 minutes yesterday including writing a blog post. So I can’t really turn on debugging. Kind of operating blind here. Thanks though. And Strict Transport Security is not enabled so…hopefully this works.
