Question 1

Why does the Caddy download page install version 1 of the Hetzner DNS module instead of version 2?

Accepted Answer

The Caddy download page shows the latest version submitted by the package maintainer via a pull request. Until the maintainer updates the entry to point to v2, users can bypass the download page by building with xcaddy: `xcaddy build --with github.com/caddy-dns/hetzner/v2` or by using the `caddy add-package` command: `caddy add-package github.com/caddy-dns/hetzner/v2`. This ensures the v2 module is included.

Question 2

How to pass client IP to the on_demand_tls ask endpoint for rate limiting and abuse prevention?

Accepted Answer

Caddy does not pass the client IP natively, but you can implement a custom permission module. In your module, retrieve the remote IP from the request context (see automation.go#L325 for example) and include it in your ask endpoint call (e.g., add as query parameter). Then process rate limiting on your backend. Full docs: https://caddyserver.com/docs/caddyfile/options#on-demand-tls

Question 3

How to manage custom DNS zone records with Caddy?

Accepted Answer

Use the external caddy-zone-manager plugin (github.com/infogulch/caddy-zone-manager). It allows defining arbitrary DNS records in the Caddyfile and syncing them to supported DNS providers. Build Caddy with the plugin using xcaddy: `xcaddy build --with github.com/infogulch/caddy-zone-manager`. Note that this plugin is not included in the official Caddy distribution and should be used with caution, especially regarding record ownership and deletion modes. The plugin supports modes like log_only, append_set, and append_set_delete to control sync behavior.

Question 4

Why does Caddy's http.request.proto placeholder return HTTP/2.0 instead of HTTP/2?

Accepted Answer

The placeholder exposes Go's http.Request.Proto, which uses the HTTP/. format. For HTTP/2 and HTTP/3, Go's internals and the quic-go library produce 'HTTP/2.0' and 'HTTP/3.0' to maintain compatibility with CGI/FCGI expectations (e.g., SERVER_PROTOCOL). As a workaround, use a Caddyfile map to rename the values: `map {http.request.proto} {proto_name} { HTTP/2.0 HTTP/2 HTTP/3.0 HTTP/3 default {http.request.proto} }`. A future dedicated placeholder (e.g., http.request.proto.name) may provide the spec-compliant protocol name.

Question 5

Why does Caddy not cache externally-managed certificates fetched via get_certificate, and how can I enable caching?

Accepted Answer

When using `get_certificate http://...`, Caddy treats the certificate as externally managed and does not cache it, because caching and renewal logic is the responsibility of the certificate manager. To introduce caching, implement a custom certmagic.Manager module. Base your implementation on the existing HTTP manager (see modules/caddytls/certmanagers.go in the Caddy repo) and add a caching layer. Then configure Caddy to use your custom manager instead of the stock `get` module. This will allow Caddy to cache and reuse certificates instead of fetching from your endpoint on every request.

caddy

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects