Wildcard subdomain, acme failing

[francislavoie]

@UltraBlack

but I’m facing issues with services like the nextcloud AIO container that just straight up refuse being hosted on a path instead of a subdomain.

See The "subfolder problem", OR, "why can't I reverse proxy my app into a subfolder?", that’ll be true for most apps. It’s not an easy problem to solve. Subdomains are the way to go.

@UltraBlack

I’m no DNS expert so it takes me often multiple tries to get a DNS config working properly, and each time I forget to lower the TTL so the changes apply more quickly.
I just want this centralized all in my caddy config. I don’t wanna have to mess with DNS every time I want to try a docker container.

You don’t have to use a wildcard cert in Caddy if you used a wildcard DNS record. You can use individual subdomains in your Caddyfile and just have the one * wildcard DNS A record pointing to your IP address.

@UltraBlack

3. Caddy version:

2.7.6

Please upgrade to the latest version, 2.8.4. It solves some issues surrounding DNS challenge propagation checks.

But are you sure you actually need a wildcard cert? You could just use the ACME HTTP challenge if I understand your setup, simpler config and no need for a DNS plugin.