Should this information become inaccessible because certs weren't paid for?
This is exactly the point I was going after. It would be one thing if the cert had just expired but cmon, October 31, 2017 really?
In my case, it's because I haven't had the desire to go in and redo the nginx config on this machine. But sure, that makes the content wrong, or something.
If your own Nginx server cannot serve up a proper and protected session, why should I consider what you've written on the website? Actually how can I know that what I'm reading is what you wrote if the session is already compromised from the start?
> but you hadn't paid your protection money to the CA racket in a while.
Yes, you sometimes have to pay for that cert from a CA but that's not why certificates expire.
Besides, your CA is Let's Encrypt so this point is completely useless but it does make an easy excuse.
Enough with the drama please.
>Enough with the drama please.
Indeed. Petty sniping in an attempt to avoid engaging the content lowers the level of discourse substantially.