When I first started Pinboard, it would take me upwards of two hours to update a forgotten TLS certificate in a cold sweat, but after ten years of annually forgetting to update the certificate in time I have it down to seven minutes.
-
-
I subscribe to your artisanal bookmarking site for the wabi sabi.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Look, if people can’t trust your self signed certificates, how can they trust you to archive their stuff
- Show replies
New conversation -
-
-
Renewing certs on time didn’t help delicious.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You can replace that customary and sacred rite with the newfangeled quarterly forgettin' o'the fixin' 'o the script that stopped working randomly, that fucking thing
-
Exactly. And on some Linux flavors/configurations, it works when you run it manually, but not when run from cron (even under the correct user), because security.
End of conversation
New conversation -
-
-
Fixing the broken let's-encrypt-certbot-crontab (when it inevitably breaks) would probably take 2 hours minimum, aka 17 years worth of your current 7-minute-per-year maintenance windows. (So sad that > 398 days no longer allowed! I loved my old 5-year certs!)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Incidentally your website still says 'Not Secure' in the browser, you're probably not redirecting to https automatically. Note that you can stick Cloudflare (free) in front of your site and it can do the frontend cert for you, and you get free caching.
-
Literal LOL at this. Tell me more!
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.