Skip to content
local-cert
Browse the documentation

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.

ValueWhere to find itIn this guide
ACME directoryfixed for each instancehttps://certs.example.com/acme/directory
Key ID (kid)Keys & access → EAB credentialseab_XXXXXXXXXXXXXXXX
HMAC keyshown only once, at creationCLE_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

  1. Give the application the domain https://nas.home.example.com.
  2. In its settings, uncheck the option that makes the container labels read-only.
  3. In the labels, replace certresolver=letsencrypt with certresolver=localcert on the HTTPS router.
  4. Redeploy.
expected label
traefik.http.routers.https-0-xxxxxxxx.tls.certresolver=localcert

Good to know

  • If the server's proxy is Caddy, follow the Caddy guide instead.
  • When Coolify regenerates the labels, letsencrypt comes back: that is why read-only labels must stay disabled on these applications.