3 ms·
And then when Let's Encrypt's certificate renewal server was down for a few hours, Caddy wasn't able to start because it required to establish a connection with
by foepys 8y ago
And then when Let's Encrypt's certificate renewal server was down for a few hours, Caddy wasn't able to start because it required to establish a connection with LE to check the certificate and it wasn't able to determine that there was an old, still valid cert available on disk. The bug tracker on Github went wild because people were unable to bring their websites back up but the author was unwilling to acknowledge it as a bug and kept closing the issues. [1]
That was when Caddy lost all its reputation for me.
1: https://github.com/mholt/caddy/issues/1680 https://github.com/mholt/caddy/issues/1680
- jjnoakes 8y agoI am not on any side in this battle, but the issue was closed only once, and after users disagreed with the author's reasoning for why it behaved the way it did, the author fixed it the same day it was closed... Doesn't seem as bad as you are portraying it... certainly not "lost all its reputation for [you]" bad?