hackers.mu using “Let’s Encrypt”!

14 Nov

hackers.mu using “Let’s Encrypt”!





Following an article written by Logan about Let’s Encrypt, I decided to embark on the journey to try out Let’s Encrypt.

Surprisingly, that was pretty easy to get to work on our FreeBSD machine, and as you can check, https://hackers.mu is successfully verified by Let’s Encrypt, and seems to be working nicely.


Hmm, seems like we are the first ones in Mauritius to be using it! Cheers Logan, beer on this.



Here’s an example a friend tried to check on his side (user sent screenshots),

12243795_10154398551444741_1174337592_n 12242330_10154398551424741_1054219415_n 12244137_10154398551374741_1838922731_n 12231326_10154398531664741_1972642516_n12231210_10154398556934741_2038910962_n 12233459_10154398556799741_1652574398_n









Tada, this looks awesome! thegodof.net shall be migrated in due time, let hackers.mu be our beta for now.

ps. You may have to accept the certificate as on some older browsers, Let’s Encrypt is not a recognized as an official certificate authority.

pps. SSLlabs gives us a grade B, since Let’s Encrypt is currently in beta. Graded A+ now 🙂

update 2016:

After expiry of the certificate, it was suprisingly easy to update the certificates and getting up and running, it was as simple as doing”
./letsencrypt-auto certonly --non-interactive --webroot -w /path/to/your/web/directory/ -d www.hackers.mu --debug

That was it, then I just linked the certs from my webserver, and tada!


  1. Interesting. I have been using CAcert for non-critical SSL/TLS deployments for a while. I’ll take a look at this new CA soon. Thanks.

      1. I have tried Let’s Encrypt on an experimental basis on one of my personal domains and I can say it is working fine. I will be recommending Lets Encrypt to my clients who need rudimentary SSL/TLS services but for some reason do not want to invest in certificates that go through a more stringent validation process.

  2. Sweettt try Let’s Encrypt on nginx work fine so far, just a little head up for the domain auth, stop nginx cause it uses port 80.

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.