[hardly_a_mirage]

Without any details, it's uncertain what the real issue was. It could very well have been attributed to a misconfiguration on your machine.

I manage over 20 client domains over a dozen servers. Have letsencrypt protecting them all. The only time I needed to manually intervene after the initial domain + SSL setup was to upgrade to ACME v2. Everything generally works out of the box with Letsencrypt + Certbot.

[jacquesm]

Good, so this hasn't bitten you. I'm sincerely happy for you. But my experience so far has been pretty rotten.

The real issue was a deprecated protocol, one that - as far as I know - could have been kept running at zero cost to LE because it already worked just fine.

[PaulKeeble]

Likewise I have had issues 3 times. In none of those cases did I really understand what went wrong, the fix was blow it away and redo it. Something just gets messed up the answer the community comes to is just start again. Its hard to answer the question of what went wrong when the error message is often garbage and gives no clue and just says the certificate can't be updated and there is no information on what just got broken.

The answer for me each time has been the age old turn it off and on again with redoing the install (or changing the way I utilised it in docker completely) and I have just found the whole thing more hassle than SSL certificates ever were.

[jacquesm]

The responses here are an interesting mix between those who have not had it happen to them (yet) and those who have (or have had it multiple times).

The former can't imagine the latter are anywhere near competent, it could obviously never happen to them so the person experiencing the problem must somehow be at fault.

It's the message board equivalent of 'can't reproduce', closed.

[hardly_a_mirage]

My comment was not accusation of incompetence, rather the lack of details provided. It's like receiving a ticket saying "This doesn't work. Fix it now"