[subpixel]

I have pages on Netlify with their one-click SSL, and more than once the certificate has (here my ignorance becomes apparent) stopped working, breaking the site (since https is forced server-side and/or cached by browsers like Safari). To get the site up and running again I've needed to contact support and have them manually issue a new certificate.

Maybe this is way easier than handling things on my own, but it seems like an achilles heel of fully automated SSL.

[icebraining]

Sounds like they just have a poor auto-TLS infrastructure. A good system will (1) try to generate multiple times ahead of expiration and (2) warn humans if the cert is about to expire.

[tialaramex]

Yup, this is definitely a Quality of Implementation issue, like if you go to a cheap bulk host and every few months your web site is just "down" due to some idiot error they made.

If it's cheap or free, well, hard to complain.