# Wildcard SSL for LAN-only services with Let’s Encrypt: do I need a reverse proxy? — retained record

> Retained reddit record from reddit:homelab.

Canonical: https://highsignal.app/data/records/5f90f778565645e2

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:homelab)  published 2026-09-21 12:10 ingested 2026-09-22 02:39

[original source ↗](https://www.reddit.com/r/homelab/comments/1wmazrf/wildcard_ssl_for_lanonly_services_with_lets/)

## retained text



```
I own mydomain.com and want to secure all my internal services (like Nextcloud, Home Assistant, etc.) with SSL using a wildcard cert for \*.home.mydomain.com. These services are **only accessible on my LAN,** I don’t want to expose them publicly. Remote access is already handled via WireGuard, so no need for public exposure. The .home.mydomain.com subdomain doesn’t have any public DNS records; it’s all resolved internally by my Pi-hole.

I’d love to use Let’s Encrypt for the certs and have them auto-renew, but I’m not sure how to make that work since wildcard certs require DNS validation. Do I need to set up a reverse proxy like Nginx or Traefik to handle this, or is there a simpler way? Would a reverse proxy add a lot of complexity, or is it pretty standard for this kind of setup?

I’ve seen some people use self-signed certs or local CAs, but I’d really prefer to stick with Let’s Encrypt if possible. Am I missing something obvious, or is this more complicated than it needs to be? How do you guys handle SSL for internal services?
```



document fetched 2026-09-22 00:36 · canonical https://reddit.com/r/homelab/comments/1wmazrf/wildcard_ssl_for_lanonly_services_with_lets
