On 2017/12/06 14:13, Tim Kuijsten wrote: > But I suspect the demand for acme-client on non-webservers > will rise and it will feel more like a kludge to configure, start and stop a > webserver in those environments.
Using HTTP at all for these (even if it's only running temporarily) feels like a kludge to me. I have some, and some https servers that aren't public access where it's still useful to have a certificate (letsencrypt's HTTP checks can come from various locations so they can't just be whitelisted). I'm using DNS-01 (currently with Kristaps' version of acme-client) for those.
