> especially considering that the Caddy web server does something similar and will go down if 1 out of 10 sites fails to provision the SSL/TLS certificate
What? That's not true. From the Caddy docs [1]:
> Caddy does its best to continue if errors occur with certificate management. By default, certificate management is performed in the background. This means it will not block startup or slow down your sites. However, it also means that the server will be running even before all certificates are available. Running in the background allows Caddy to retry with exponential backoff over a long period of time.
Caddy will actually keep your site online when other servers don't. See the bottom of this page: https://caddyserver.com/v2
What? That's not true. From the Caddy docs [1]:
> Caddy does its best to continue if errors occur with certificate management. By default, certificate management is performed in the background. This means it will not block startup or slow down your sites. However, it also means that the server will be running even before all certificates are available. Running in the background allows Caddy to retry with exponential backoff over a long period of time.
Caddy will actually keep your site online when other servers don't. See the bottom of this page: https://caddyserver.com/v2
[1]: https://caddyserver.com/docs/automatic-https#errors