Mixing stored TLS certificates and automatic TLS certificates uses wrong certs

[timelordx]

@pfish

The logs indicate that Caddy is successfully provisioning a certificate for other-caddy-ssl.ttdi.us, but when I make a request to it, Caddy tries to present me with the certificate for *.caddy-ssl-test.ttdi.us.

@pfish

but it does seem like something is wrong with the way Caddy is looking for TLS certificates and this may indicate some kind of bug.

Problems mixing automatic and on demand TLS

You didn’t mention which version of Caddy you’re using, so I’ll assume it’s somewhere in the 2.10.x range. Starting with version 2.10.0, if there’s a wildcard domain configured, its wildcard certificate will be used for all matching subdomains. From the v2.10.0 release notes: Wildcards used by default: Previously, Caddy would obtain individual certificates for every domain in your config literally; now wildcards, if present, will be utilized for subdomains, rather than obtaining individual …