Experiencing SSL-related issues after migrating your WordPress site with Duplicator Pro? This guide offers practical steps to troubleshoot and resolve common SSL problems, ensuring your site remains secure and functions correctly post-migration.

To begin with, make sure you are using the latest version of Duplicator Pro. Please check the changelog and system requirements.

Option 1: SSL Issues Checklist

If you’re experiencing SSL-related issues while moving from HTTPS to HTTP or vice versa, follow this checklist to troubleshoot and resolve the problem.

Check SSL Plugins:

If you have an SSL plugin installed that manages SSL links, try the following:

• Deactivate and reactivate the plugin.
• Temporarily remove the plugin to check if the issue persists.

SSL-related plugins can also be disabled on Step 3 of the Duplicator installer under the Options section.

The most common real cause of SSL/padlock issues after a migration is mixed content: leftover http:// references still sitting in the database while the site now runs on https://. Duplicator’s installer includes a Custom Search & Replace option (Step 3 » Engine) built for exactly this: re-run the installer and add a search-and-replace pair for the full old URL (http://) to the new URL (https://). If re-running the installer isn’t practical after the fact, a dedicated search-and-replace plugin can perform the same database update.

Also check Settings » General in the WordPress admin to confirm the Site Address (URL) and WordPress Address (URL) both use https://, not http://.

Modify wp-config.php:

Open your wp-config.php file and look for the following constant:

define('FORCE_SSL_ADMIN', true);

Note: Try toggling it between true/false and see if it resolves the issue.

Check WordPress Codex Recommendations:

Review the Administration Over SSL documentation in the WordPress Codex to ensure your site follows the best SSL practices.

Option 2: Adjust Apache SSL Configuration

On some hosting environments, modifying the Apache SSL configuration can resolve SSL issues.

1. Open or ask your hosting provider to edit the ssl.config file.
2. Add the following lines:
   • RequestHeader set X-Forwarded-Proto “https”
   • RequestHeader set X-Forwarded-Port “443”
3. Save the changes and restart the Apache server (if applicable).

Note: If you’re unsure how to modify your Apache configuration, contact your hosting provider for assistance.

By following these steps, you should be able to resolve common SSL issues and ensure a smooth migration.

If sub-pages look broken or blank alongside the SSL issue, see How to Fix Home Page and/or Sub-Pages Not Showing. If the install report shows database warnings, see Resolving the Installer Database Errors and Warnings on the Install Report.