Products · Product
Let's Encrypt
Raised as a usability problem by 28 people on Hacker News over 14 years (2012–2025), in 21 threads.
No issue was raised by at least 3 people in 3 threads this year.
No issue was raised by at least 3 people in 3 threads in the last 5 years.
Every issue, all time, most people first
Renewing certificates every three months needs a VM and manual stepsUnreviewed
20122026- Short certificate lifetimes force constant re-copying of certs and rebooting devices2025-08-13
- Must renew certificates every few months, with confusing error messages and hard-to-find release notes2020-09-10
- Renewing certs every three months needs a VM and a clumsy manual process2016-08-17
Docs only cover Certbot, leaving manual setup confusingUnreviewed
20122026- Forced to install certbot tool without knowing what it does2025-12-01
- Docs only say to use Certbot, leaving manual setup and account concepts confusing2023-01-04
- Tutorials reference certbot, which isn't findable under the Let's Encrypt name2020-09-10
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 26 complaints
- Forced to install certbot tool without knowing what it does2025-12-01
- Short certificate lifetimes force constant re-copying of certs and rebooting devices2025-08-13
- Docs only say to use Certbot, leaving manual setup and account concepts confusing2023-01-04
- Port forwarding for verification every three months is a hassle2022-11-01
- Requires tooling and knowledge, has many gotchas, and can suddenly break websites2022-02-20
- Getting certificates for local-only services is hard, with corporate hoops making deployment near impossible2021-11-16
- Too many CT log notifications, with no way to tell which are expected2020-11-23
- Error messages are garbage, giving no clue what broke when renewal fails2020-09-10
- Must renew certificates every few months, with confusing error messages and hard-to-find release notes2020-09-10
- Self-hosting certificate management keeps getting harder and more tedious over time2020-09-10
- Automatic renewal fails unpredictably, so user must manually check if it worked2020-09-10
- Tutorials reference certbot, which isn't findable under the Let's Encrypt name2020-09-10
- Proving domain ownership for wildcard certs requires periodic DNS TXT updates, needing server write access to DNS2020-01-27
- Up-to-date setup documentation is hard to find and client scripts needed fixing2019-12-17
- Setting up Let's Encrypt with node was a pain2017-01-23
- Setup is painful and the documentation is abysmal2016-09-20
- Renewing certs every three months needs a VM and a clumsy manual process2016-08-17
- Useless error messages made renewal take two hours and forced giving up2016-01-26
- Cryptic error messages hide the real fix, such as needing sudo -H2016-01-19
- Official client crashes with an error every time and documentation is sparse2015-12-21
- Stuck at step 5 with no visible progress and cryptic errors2015-12-04
- Running without root is hidden and hard to figure out; scripting needs interactive prompts2015-12-03
- The main client package is bloated and annoying to use2015-12-03
- Remembering a double-dash parameter is harder than a simple named command2015-10-27
- Certificate process is hostile and the UI is confusing at times2014-06-27
- Web interface is not great to use2012-01-14