Let’s Encrypt is a free, automated, and open Certificate Authority. It’s goal is to get all web pages on the internet, encrypted (using HTTPS/SSL). When web pages are sent via HTTPS, the contents cannot be modified in transit, ensuring that the receiver of the content receives the intended information. There are also other benefits of using HTTPS which you can read about here.
I have written a tutorial on how to get your site set up and using HTTPS/SSL on my wiki site, which you can find here.
The reason I have posted the tutorial on the wiki instead of directly here is to allow quicker navigation between tutorial headings. WordPress does not allow this in it’s design but the wiki platform does.
You can use this platform to provide any comments you might have regarding the tutorial
The purpose of this post is for me to announce the availability of a new “site” on my domain – a wiki site. This site can be found at: https://wiki.newteq.co.za.
I will be using the wiki site for more tutorial based posts and things to keep in mind when setting up servers, or configurations for applications.
My first post on the wiki platform will be an item regarding the set up of SSL on your apache web server, using Let’s Encrypt . Let’s Encrypt is a great way to get your website SSL secured without having to pay for SSL certs. The Let’s Encrypt drive is to ensure that all web traffic is sent over HTTPS. Let’s Encrypt ensures that you own the server that you are wanting to enable SSL on, making it perfect for anyone (like myself) who would like to ensure that their content is served over HTTPS, but aren’t a huge corporate with big pockets to get the Verisign (or similar) certs.
I have only covered a very high level overview of my understanding of Let’s Encrypt. If you wish to find out more about it, please visit their website
Once I have completed the Let’s Encrypt tutorial, I will be posting another article on here as notification.