18 engineers on Hacker News describe using Let's Encrypt first-hand: 7 endorse it, 4 regret it, 0 are mixed.
“A few months later and we are just using let's encrypt for everything, for free.”
endorse · production · cortesoft · 2025-12-09 · source ↗ · wrong label?“We migrated ~800 domains to LE back in 2019 and initially relied heavily on those expiration emails as a safety net.”
endorse · production · 6 yr · builtsimple · 2025-07-01 · source ↗ · wrong label?“We did run into a rate limiting issue with letsencrypt when we tried to provision too many certs at one time.”
regret · production · mooreds · 2025-02-18 · source ↗ · wrong label?“use letsencrypt for the SSL certs”
endorse · production · erinaceousjones · 2022-11-29 · source ↗ · wrong label?“Our biggest failure mode is TLS certificates failing to provision through Let's Encrypt”
regret · production · jrockway · 2021-07-27 · source ↗ · wrong label?“We used let's encrypt because we needed something dynamic so we didn't have to manage certs. ... For what it's worth I was happy with it.”
endorse · production · tasssko · 2021-03-18 · source ↗ · wrong label?“The difference for me is that Let's Encrypt has required this kind of manual intervention more often than the previous status quo.”
regret · personal · bscphil · 2020-09-10 · source ↗ · wrong label?“This bled into work where we replaced all paid certs(except wildcards, coming soon) and secured hundreds of domains”
endorse · production · twothamendment · 2017-11-21 · source ↗ · wrong label?“The issue we've run into with Let's Encrypt, is that they have a limit on the number of new (non-renewal) certs in a time period”
regret · production · CaliforniaKarl · 2017-10-24 · source ↗ · wrong label?“We switched to Let's Encrypt literally because of this, so that's a direct penalty for their stupidity on this one”
endorse · production · davidgerard · 2016-06-26 · source ↗ · wrong label?“Of course Let's Encrypt has been more then what we expected and will continue to use them until such time we are required to stop using them!”
endorse · production · puddintane · 2016-06-23 · source ↗ · wrong label?“So we use this to authenticate based on our fixed-IP/PTR/DNS to connect server to server to a 3rd party.”
neutral · production · rswail · 2025-12-16 · source ↗ · wrong label?“my very basic inhouse solution to do automatic Let's Encrypt integration ... is ran by cron every day”
neutral · production · timcambrant · 2024-05-06 · source ↗ · wrong label?“We now have a fully reproducible base EKS cluster deploy done with working cert-manager/letsencrypt, nginx ingress”
neutral · production · tthayer · 2020-12-22 · source ↗ · wrong label?“As long as I can respond to a DNS challenge, I can still get a letsencrypt certificate for that domain.”
neutral · production · akira2501 · 2020-06-28 · source ↗ · wrong label?“We've recently switched to a scheme where we run a Nginx reverse-proxy with LetsEncrypt. Everything is in docker containers.”
neutral · production · ansible · 2019-12-17 · source ↗ · wrong label?“We implement Let's Encrypt renewals on top of this using the DNS challenge”
neutral · production · lol768 · 2019-04-15 · source ↗ · wrong label?“our Nginx reverse proxy also has a cron job that runs letsencrypt automatic renewal once a week”
neutral · production · tzaman · 2016-12-20 · source ↗ · wrong label?