Coolify
Coolify's default proxy is Traefik, configured through arguments. You add a resolver for local-cert, then reference it in the labels of the relevant applications.
| 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
Servers → your server → Proxy → Configuration. In the command section of the Traefik service, after the --certificatesresolvers.letsencrypt… lines, add:
proxy configuration (excerpt)
- '--certificatesresolvers.localcert.acme.caserver=https://certs.example.com/acme/directory'
- '--certificatesresolvers.localcert.acme.email=ops@example.com'
- '--certificatesresolvers.localcert.acme.storage=/traefik/acme-localcert.json'
- '--certificatesresolvers.localcert.acme.eab.kid=eab_XXXXXXXXXXXXXXXX'
- '--certificatesresolvers.localcert.acme.eab.hmacencoded=CLE_HMAC'
- '--certificatesresolvers.localcert.acme.httpchallenge.entrypoint=http'Save, then Restart Proxy. In Coolify, the entrypoints are named http and https.
2. Use it on an application
- Give the application the domain
https://nas.home.example.com. - In its settings, uncheck the option that makes the container labels read-only.
- In the labels, replace
certresolver=letsencryptwithcertresolver=localcerton the HTTPS router. - Redeploy.
expected label
traefik.http.routers.https-0-xxxxxxxx.tls.certresolver=localcertGood to know
- If the server's proxy is Caddy, follow the Caddy guide instead.
- When Coolify regenerates the labels,
letsencryptcomes back: that is why read-only labels must stay disabled on these applications.