That is the next big thing on the [very close] horizen.
Oh, and I also collect BAD IPs.
I have 4.6M+ [very bad ones] so far
That is the next big thing on the [very close] horizen.
Oh, and I also collect BAD IPs.
I have 4.6M+ [very bad ones] so far
But we digress...
I really don't see how the SNI-hole thing is related to your problem at all.
LE uses SNI.
Your server uses SNI.
Things failed.
Now things work.
We I really don't know why it went down nor why it went up.
My only guess is that it will happen again.
Maybe then we can dig deeper into the problem [and actually solve it - once and for all].
I think you may be confusing me with the OP (JulienCKJM). I didn't start this thread; I merely replied to the OP here since his issue had some similarities to my own. It was he who brought up the SNI-hole thing. I merely suggested the manual cert renewal method to him as a workaround for future renewal script failures with ensuing expired certs. My own thread was posted first, albeit we both experienced the "(5) certs were issued in the last 168 hours" message from letsencrypt and were temporarily blocked.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.