Dokploy
Dokploy routes everything through Traefik. You add a second certificate resolver next to the Let's Encrypt one, then pick it domain by domain.
| Value | Where to find it | In this guide |
|---|---|---|
| ACME directory | fixed for each instance | https://certs.example.com/acme/directory |
| Key ID (kid) | Keys & access → EAB credentials | eab_XXXXXXXXXXXXXXXX |
| HMAC key | shown only once, at creation | CLE_HMAC |
1. Add the resolver
In Dokploy: Web Server → Traefik → edit the main configuration (the /etc/dokploy/traefik/traefik.yml file on the server). Under certificatesResolvers, keep letsencrypt and add:
traefik.yml (excerpt)
certificatesResolvers:
letsencrypt:
# … unchanged …
localcert:
acme:
caServer: https://certs.example.com/acme/directory
email: ops@example.com
storage: /etc/dokploy/traefik/dynamic/acme-localcert.json
eab:
kid: eab_XXXXXXXXXXXXXXXX
hmacEncoded: CLE_HMAC
httpChallenge:
entryPoint: webSave, then reload Traefik from the same page (Reload). The static configuration is only re-read when Traefik restarts.
2. Use it on a domain
- In the application → Domains → add
nas.home.example.com. - Enable HTTPS.
- Certificate provider: Custom, resolver
localcert.
3. DNS
nas.home.example.com must point to the Dokploy server's LAN address. local-cert can publish that A record for you: see DNS in the API.
Good to know
- The public domains of your other applications stay on
letsencrypt: the two resolvers coexist. - Keep a separate
storagefile per resolver, as above. - Everything else behaves as in Traefik: see Traefik.