dehydrated

Set up once and then a cron-task? [0] It doesn't have to be a pain. The tooling around this all exists. It's very very nearly maintenance free [1]. [0] There's lots of tooling. My current preference is for https://github.com/lukas2511/dehydrated [1] If something breaks you have to pay attention, otherwise... Not so much.

+1 https://github.com/lukas2511/dehydrated

You can use dehydrated [1] which is a single shell script that you can trigger via cron to do the whole let's encrypt stuff for you. No dependancies other than curl. [1] https://github.com/lukas2511/dehydrated

I've had good luck with dehydrated (https://github.com/lukas2511/dehydrated) It takes a file with a list of domains to check and you can write your own hooks to handle the DNS management and certificate deployment however you want.

Nope. I’m using LXC and have set things up manually. It’s just a basic setup with dehydrated[1], some bash scripts for deployment and cron though. [1] https://github.com/lukas2511/dehydrated

You can achieve this without exposing any service. Let's Encrypt allows you to prove ownership of a domain through DNS 01 hooks. I personally use Duck DNS [1] for main internal domains, so I can have a certificate that most tools will recognize as valid. This saves me from adding my cert in every machine that will use that service. I use dehydrated [2] to get a Let's Encrypt certificate using Duck DNS. There is a good article explaining that by Andreas Gohr [3]. [1] - https://www.duckdns.org/ [2] - https://github.com/lukas2511/dehydrated [3] - https://www.splitbrain.org/blog/2017-08/10-homeassistant_duc...