5 ms·

I find the documentation for the syntax to be a bit lacking if you want to do anything that isn't very basic and how they want you to do it. For example, I want

by pgug 1y ago

I find the documentation for the syntax to be a bit lacking if you want to do anything that isn't very basic and how they want you to do it. For example, I want to use a wildcard certificate for my internal services to hide service names from certificate transparency logs, and I can't get the syntax working. Chatgpt and gemini also couldn't.

cpach 1y ago
This integration doesn’t support the dns-01 challenge. So wildcard certs are out of the question at this point.
- cpach 1y ago
  PS. Oh, this subthread is about Caddy, not Nginx. Nevermind my comment then!
nadanke 1y ago
For wildcards you need a Caddy build that includes the dns plugin for your specific provider. There's a tool called xcaddy that helps with that. It's still kinda annoying because now you need to manage the binary for yourself but when I tried it with Hetzner it worked fine.
- snickerdoodle12 1y ago
  In case it helps someone else, this is what I do: FROM caddy:2-builder AS builder RUN xcaddy build \ --with github.com/caddy-dns/cloudflare \ --with github.com/greenpau/caddy-security FROM caddy:2 COPY --from=builder /usr/bin/caddy /usr/bin/caddy COPY Caddyfile /etc/caddy/Caddyfile Then just build & run it via docker compose
dizhn 1y ago
This here is how it's done, where you have a wildcard dns entry for subdomains of secret.domain.com. { acme_dns cloudflare oWN-HR__kxRoDhrixaQbI6M0uwS4bfXub4g4xia2 debug } *.secret.domain.com { @sso host sso.secret.domain.com handle @sso { reverse_proxy 192.168.200.4:9000 } @adguard host adguard.secret.domain.com handle @adguard { reverse_proxy 192.168.200.4:9000 } @forge host forge.secret.domain.com handle @forge { reverse_proxy http://forgejo:3000 } # respond to whatever doesn't match handle { respond "Wildcard subdomain does not have a web configuration!" } handle_errors { respond "Error {err.status_code} {err.status_text}" } }
- pgug 1y ago
  Thank you, I will try that later today.

by pgug 1y ago

cpach 1y ago

This integration doesn’t support the dns-01 challenge. So wildcard certs are out of the question at this point.

cpach 1y ago
PS. Oh, this subthread is about Caddy, not Nginx. Nevermind my comment then!

nadanke 1y ago

For wildcards you need a Caddy build that includes the dns plugin for your specific provider. There's a tool called xcaddy that helps with that. It's still kinda annoying because now you need to manage the binary for yourself but when I tried it with Hetzner it worked fine.

snickerdoodle12 1y ago
In case it helps someone else, this is what I do: FROM caddy:2-builder AS builder RUN xcaddy build \ --with github.com/caddy-dns/cloudflare \ --with github.com/greenpau/caddy-security FROM caddy:2 COPY --from=builder /usr/bin/caddy /usr/bin/caddy COPY Caddyfile /etc/caddy/Caddyfile Then just build & run it via docker compose

dizhn 1y ago

This here is how it's done, where you have a wildcard dns entry for subdomains of secret.domain.com. { acme_dns cloudflare oWN-HR__kxRoDhrixaQbI6M0uwS4bfXub4g4xia2 debug } *.secret.domain.com { @sso host sso.secret.domain.com handle @sso { reverse_proxy 192.168.200.4:9000 } @adguard host adguard.secret.domain.com handle @adguard { reverse_proxy 192.168.200.4:9000 } @forge host forge.secret.domain.com handle @forge { reverse_proxy http://forgejo:3000 } # respond to whatever doesn't match handle { respond "Wildcard subdomain does not have a web configuration!" } handle_errors { respond "Error {err.status_code} {err.status_text}" } }

pgug 1y ago
Thank you, I will try that later today.