TLS Encryption from Let’s Encrypt!

Today, the Let’s Encrypt Public Beta has come out. I’ve wasted no time in obtaining SSL certificates for all of my subdomains; however, Jenkins is still awaiting a certificate. By Saturday, every service will be fully encrypted with HTTPS, which includes permanent redirects from all HTTP services to their HTTPS counterparts.
I’m really excited for this change that Let’s Encrypt is bringing to the Internet. Today, data encryption has become a must-have in order to protect websites and their users. Now I’m going to go get an extra hour of sleep tonight, feeling protected by the new encryption. See you guys! <3 nonemu

7 thoughts on “TLS Encryption from Let’s Encrypt!

  1. It appears that https://irc.nonemu.ninja and https://jenkins.nonemu.ninja are currently both using the SSL certificate for docs.nonemu.ninja , prompting firefox (and probably other browsers) to say that the connection is insecure and will not connect by default.

    If you want to use a single certificate for all of those domains, a certificate for *.nonemu.ninja might be worth looking into? Though, I’m not sure if Let’s Encrypt gives out wild-card certificates, I just started looking into them myself before I saw this.

      1. Alright. Still doesn’t really change the fact that there appears to be a problem there… Subject Alternative Name might be a way to do it? That way you could have just one domain?

        … And now SSL feels broken. Firefox gives me an error if I try to connect to this site over HTTPS (and all it says is “Secure Connection Failed” with no option to continue connecting. Thankfully HTTP still works…

        1. Thanks for the tips. The SSL issue seems to be fixed after tweaking the config slightly. I’m currently trying to get SAN to work with acme_tiny so I can validate nonemu and http://www.nonemu with the same certificate. I am also aware of the issues with my Jenkins/Nexus servers, and I am not sure what the problem is.

          1. Yeah, the main site works perfectly now (with redirects to https too!) now. If this is any help, {docs,jenkins,nexus}.nonemu.ninja now all use the ssl cert for files.nonemu.ninja . What is the rough setup for those 4 websites? Are you using apache? nginx?

          2. I don’t have certificates for any of those domains yet, so they’re not configured to respond to SSL requests. Nginx must have chosen files.nonemu.ninja as the fallback. Soon I should be able to get certificates for those.

Leave a Reply

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