4 ms·
Have you tried let’s encrypt a la certbot? It wasn’t a painless process when I did it but I do have autorenewing “green lock” SSL certs for free.
by willis936 7y ago
Have you tried let’s encrypt a la certbot? It wasn’t a painless process when I did it but I do have autorenewing “green lock” SSL certs for free.
- henvic 7y agoYes, I have. Let's Encrypt ACME challenge resolved this from now on. However, I'm using a really old machine + OS, and the nginx version I'm running is old enough not to be compatible with it. So, instead of having a hard time updating the server, I decided to migrate the site to a newer machine (even because some AWS technical limitations don't let me migrate to a new instance type). ~10 years ago I slacked in getting an HTTPS certificate as this would have meant a lot of money. ~ Today, I want to use the ACME challenge with Let's Encrypt (no need of OV for a portfolio website), but I never find the time to finish the migration (that should take more 4 to 16 hours).
- Jenda_ 7y agoThere are ACME clients written in Python 2 or even pure shell -- should work even on very old systems (but not older than ~2010, you need openssl with TLS1.2 support). I personally prefer them even on current systems, as I don't really like the "automagic" nature of certbot.
- m_eiman 7y agoI got tired of manually restarting this or that every two months or so due to failed letsencrypt updates that left my sites inaccessible, eventually I replaced the web server with a new one with more current versions. Hopefully it’ll keep things together for a few years…
- willis936 7y agoI’ve been running it for 3-4 years. After a long initial setup, I’ve only had to touch it once: when some authentication protocol was deprecated. A small price to pay, all things considered.