Ricardo N Feliciano

3 minute read

For some people, the first time setting up Let’s Encrypt can be a little daunting. That’s okay. It’s beta software that doesn’t yet have a fully polished process. It’s beta software that turned the whole process of obtaining a commercially signed SSL certificate on its head. I was a bit confused at first because I have several websites (including this one) running on a load-balanced setup using a Linode NodeBalancer.

This means that my backends, where my sites live, do not handle HTTPS traffic at all. The SSL certificate for my domain name is actually loaded on the NodeBalancer via Linode Manager and serves as the HTTPS endpoint for all my traffic. So how do I get Let’s Encrypt to properly generate an SSL certificate for me and then what do I do with it? Here’s how I got everything to work. This same process would also work on custom-made load-balancers. It doesn’t have to be a NodeBalancer, I just like the convenience of having one.