Is your website securely using HTTPS encryption?
If it isn’t, it should be.
HTTPS is the term used for Secure HTTP connections. It provides a safer and more secure connection for you and your website visitors. Each website that uses a HTTPS connection is issued an SSL (Secure Sockets Layer) certificate. If the website certificate does not match correctly with what should be there, the browser will warn the visitor.
Modern browsers also warn the user if a website is still using the older HTTP connection.
Three years ago Google advised that HTTPS was now a ranking factor and it is apparently even more of a ranking factor today.
So in addition to creating a safer website, you can also increase your search engine presence and organic traffic by adopting an HTTPS connection.
In this tutorial I will show you how you can do that using Cloudflare.
Getting an SSL Certificate
Many hosting companies charge for providing an SSL certificate, though it is becoming more common for hosting companies to offer one with plans.
I personally use the website performance and security service Cloudflare as it offers a free SSL certificate. Their free plan also offers many other fantastic free tools such as a Content Delivery Network (CDN) to improve performance, security tools, and a range of apps from popular internet services.
If you are not using Cloudflare to provide an SSL connection, do not make any of the changes suggested in this tutorial. This tutorial is not for you.
How to Change Your WordPress URLs to HTTPS Using Cloudflare
Below you will find the exact steps I took to took to make KevinMuldoon.com secure. You can perform any of these steps in a different order, but you may find that your website will not work correctly temporarily.
Please be conscious of the specific changes you have made and refer back to this tutorial if you are unsure. Cloudflare sometimes takes a few minutes to perform changes (sometimes longer) and you will need to ensure you clear any cache to make sure those changes are being shown in your browser. You may have to clear browser cookies too.
It goes without saying that I accept no responsibility for your website going down temporarily or for your website acting weird, but don’t worry, this is not something to panic over. It should only take you a few minutes to perform these steps and you can simply reverse any changes you make if you are unsure.
If you are not confident about any of this, step away from your computer and ask your hosting company for help.
Please also note that this guide is specifically for setting up HTTPS with Cloudflare on WordPress (though it is worth mentioning that the process of using Cloudflare’s SSL certificates is generally easier with other platforms).
This plugin fixes the infinite redirect loops that will occur when using Flexible SSL.
Next you need to login into Cloudflare and go to the Crypto page.
Go to the Crypto page in Cloudflare.
In the SSL section, change the setting to Flexible (it was probably set to Off or Full previously).
Read “What do the SSL options mean?” on Cloudflare’s website for an understanding of what the available SSL settings mean.
Warning: If SSL is set to Flexible and Cloudflare Flexible SSL is not activated, your website will mess up. Be sure to change SSL back to Full if you ever need to deactivate Cloudflare Flexible SSL e.g. if you have deactivated all WordPress plugins in order to debug errors.
Set SSL to Flexible.
Scroll down to the section entitled “Always use HTTPS” and switch it on.
This redirects all HTTP requests to HTTPS.
Set Always use HTTPS to On.
OK, this is the part of the tutorial where it gets a little tricky since the status of your website at this point will depend on how your website is setup.
I use WP Rocket to improve my website’s performance. When WP Rocket is enabled at this stage, my website has successfully changed from HTTP to HTTPS. Unfortunately, my website design was all messed up as parts of my design that were linked relatively were not displaying correctly.
To fix this problem, I opened the WP Rocket settings page and clicked on the Cloudflare tab.
Click on the Cloudflare tab in WP Rocket.
Then I ensured that Relative Protocol was switched on.
It is unlikely that you had this setting enabled previously as it is only required when using Cloudflare’s Flexible SSL connection.
Ensure that Relative Protocol is turned on.
At this point, my website was securely using HTTPS and it had no design issues. If you are using a different caching solution, you may have to enable a similar option.
Obviously, for the benefit of this tutorial, I had to test these steps for people who don’t use WP Rocket.
When I disabled WP Rocket, something bizarre happened.
I did not experience any design issues like I did when WP Rocket was enabled without Relative Protocol activated, however my website was no longer secure. My website URLs were using HTTPS, but my browser stated that the connected was insecure.
To fix this issue I installed the free WordPress plugin SSL Insecure Content Fixer. I selected the content setting and that fixed everything; though you may want to test all settings on your website to see which works best for you as some options may break something on your website.
With WP Rocket disabled, SSL Insecure Content Fixer was able to make my website fully HTTPS compliant.
Try different settings in SSL Insecure Content Fixer to see what works.
You may have noticed that at no point during the steps did I recommend changing the WordPress Address (URL) or Site Address (URL) fields that are located in your WordPress general settings page.
Many guides suggest changing your website addresses from http://www.domain.com to https://www.domain.com (via the settings area or directly within your website database). This is not necessary when using Cloudflare and can actually cause a lot of problems.
If you made the mistake of changing your website address to HTTPS in the general WordPress settings area, change it back.
No part of the process of changing your WordPress website from HTTP to HTTPS using Cloudflare is difficult; however you may encounter a couple of setbacks along the way. It’s a case of trial and error to get things working.
If your browser is not showing what you think it should be, clear your browser cookies, login and logout of WordPress, and go back and revert the changes you made and then start again.
If you need further help, I highly recommend reading the article “WordPress Cloudflare Flexible SSL – Making It Work” by iControlWP (the same people who created the Cloudflare Flexible SSL plugin you need to use). It’s a good tutorial and there are lots of comments from WordPress users giving their own suggestions on how to get HTTPS working.
The Cloudflare article “How do I fix mixed content issues or the infinite redirect loop error after enabling Flexible SSL with WordPress?” also has some information you will find useful.
If you are still finding it difficult to get everything working, I encourage you to speak to your website hosting company.
The post Configuring Cloudflare Flexible SSL on WordPress – HTTP to HTTPS appeared first on Kevin Muldoon.
Go to Source
Author: Kevin Muldoon
Powered by WPeMatico