in reply to Jonathan

I went the full Monty. DNS server at home, step-ca (certificate authority) in a container, so now all my (virtual) machines get name resolution and certificates via certbot. See jan.wildeboer.net/2025/08/My-D… and jan.wildeboer.net/2025/07/lets… @bjoern @homelab @homelab_de
in reply to Jonathan

I realise it via a nginx proxy manager container (which is very large). An approach is described there:
youtube.com/watch?v=qlcVx-k-02…
This entry was edited (5 hours ago)
in reply to Jonathan

@bjoern@sengotta.net @homelab @homelab_de I can only underline what @jwildeboer@wildeboer.net already wrote - install your own CA using #step-ca.

Once all is up and running, SSL certificates and warnings turn into a no-issue in your home network. I've done that a few months ago and have not thought about them once since then.

Install step-ca and look no further.

This entry was edited (5 hours ago)
in reply to Jonathan

I do this with let’s encrypt, a free subdomain from freedns.afraid.org/ and an inadyn script with a 5 minute cron to compare rotating public IPs.
in reply to Jonathan

@homelab@fedigroups.social_de it’s fairly straightforward to set up your own internal CA and add it to your system / browser’s trust store. You can do it with openssl or with a GUI tool like xCA.

Or, apparently, step-ca is a thing, which should let you use an ACME client to automate issuing internal certs hub.docker.com/r/smallstep/ste…

This entry was edited (5 hours ago)
in reply to kate

I’ll revisit the dns challenge when letsencrypt adds the static entry option DNS-PERSIST-01 [1]. Right now you need to dynamically update dns for this to work.

[1] letsencrypt.org/2025/12/02/fro…

@abulling @interpipes @jonathan859 @bjoern @homelab

This entry was edited (4 hours ago)