← sources

How to deploy a SSL certificate (wildcard) across multiple hosts?

source: reddit (reddit:selfhosted)published 2026-10-18 20:49ingested 2026-10-19 02:40

retained text

Hi! I have several services hosted on two mini-PCs at home, plus Home Assistant on a Raspberry Pi, a NAS, and a cloud VM that acts as a reverse proxy for internet "clients" (using Nginx + mTLS). Every home host have a NGINX that reverse request only for services that hosted on that server. Everything works great, but... how do you manage wildcard SSL certificates for services across multiple hosts?

Back when I had just one host and a couple of services, the HTTP-01 challenge worked perfectly. As the number of services grew, I switched to the DNS-01 challenge — it’s much more convenient. It means fewer Nginx configurations to manage, and it’s easier to keep track of certificate expiration dates.

Now that I have two hosts (plus the cloud VM, making it three), I can no longer use the HTTP-01 challenge for each of them; since NAT only allows me to forward ports 80 and 443 to a single host, the challenge process fails for any other host.

Currently, I am running a DNS challenge on three servers and obtaining three valid wildcard certificates; HOWEVER, automatic renewal does not work — or rather, it only works for the last server that was activated(registered in LE).

It looks like I might be doing something wrong.

It seems that a wildcard certificate should be obtained by one server and then distributed to all the other servers. But how? A Bash script? Ansible? Are there perhaps any self-hosted applications for this?

I know it would be possible to use a single reverse proxy and route all "client" traffic through it, but that creates new problems and doesn't seem like an elegant solution.

P.S. I’m using LE, if that matters

document fetched 2026-10-19 00:27 · canonical https://reddit.com/r/selfhosted/comments/1x9dzwl/how_to_deploy_a_ssl_certificate_wildcard_across