• Remember to click the ‘Save changes‘ button to save your changes.
• WordPress will log you out and ask you to re-login once the adjustments are saved.
• Then, in your .htaccess file, add the following code to set up WordPress redirects from HTTP to HTTPS.

RewriteEngine On
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]

If you’re using Nginx servers (which most people aren’t), you must add the following code to your nginx.conf file to convert from HTTP to HTTPS and must restart the Nginx after adding the below code:

if ($server_port = 80 ) {
return 301 https://$host$request_uri;
}

Note: Here, I have used mydomain.com as an example. So, you replace mydomain.com with your actual domain.

WordPress will not load the whole website with https. You need to configure SSL in the wp-admin.php file if you want to force your site to be loaded with https.

Add the following code to the wp-admin.php file to do that.

define('FORCE_SSL_ADMIN,' true);

Your website is now ready to use SSL/HTTPS but will show mixed content errors. Stylesheets, images, and other sources are the reason for these errors because they are still loading with HTTP in the URL, which is insecure.

But how will you know if something like that happens? You cannot see the padlock icon in your website address bar. Sometimes, you can see the padlock icon in the browser’s address bar with a notification because some modern browsers block insecure and unsafe resources.

You can use the inspect tool to know which resource or script is causing the error. You will see some warnings in the console with details of mixed content items that show the insecurity errors, as shown in the figure below.