4 ms·
If you are looking for ease of use and stability, there is an alternative solution. Issue self-signed certificates on your server, and then use a service like C
by csomar 6y ago
If you are looking for ease of use and stability, there is an alternative solution. Issue self-signed certificates on your server, and then use a service like CloudFlare that handles the front-user certificates. The whole traffic is encrypted now, but you don't need a CA authority to deal with.
The people who are benefiting from Let's Encrypt are the least technical who can't even SSH into a server. They get the certificate from their hosting provider automagically. It's reasonable that LE and the people writing software for it will focus on them rather than another developer doing a manual integration.
- jacquesm 6y agoThat's a valid point.
- bigiain 6y ago> then use a service like CloudFlare that ... MITMs all your user's traffic through a company that's made questionable ethical decisions in the past. :sigh:
- maple3142 6y agoAren't all CDNs MITM?
- bpizzi 6y agoCompletely relevant. There's a variant where you don't need CF: compile/install Caddyserver on your box, let it handle the LE certificates by itself, and use it as a reverse proxy to deliver the request to your current webserver. Caddy being a stand alone binary (it's even possible statically link GLIBC), you can even work yourself around an old distro and dependencies nightmares. Caddy's config file is on par with Nginx in terms of simplicity, the learning phase is quiet small, I would even say nonexistent for someone with a technical background as OP.