Caddy Certs and Port Specific Redirection SANS HTTPS

[francislavoie]

@tcb

Is the proper way to tell caddy to use http rather than https for a specific domain/subdomain to declare port 80 after the domain/subdomain as I did above?

Yeah, just specify http:// scheme on the site address, or use the HTTP port, and that domain won’t qualify for Automatic HTTPS:

Automatic HTTPS - Caddy Documentation

@tcb

Can Caddy automatically obtain wildcard certs usable by other servers, e.g. ejabberd XMPP server, on other subdomains?

Yes, but you need to configure Caddy with the appropriate DNS plugin for your DNS provider, and configure a site block with *.14servers.net.

Automatic HTTPS - Caddy Documentation

Note that when you use the Caddyfile, there’s no way to tell Caddy to manage a certificate for a domain but not enable an HTTPS server for it. If you need fine grained, control over that, you can use JSON config directly.

Using Caddy to keep certificates renewed

You can use Caddy as an automated certificate manager to keep certificates renewed without having to run an HTTPS server [1]. This way, the certificates can be used by other programs that need them. Caddy’s tls app can be configured without the need for an HTTP server. It can keep certificates renewed. Without additional configuration, assets (certificates, keys, and metadata) are stored in a data directory on the local file system at a location dependent upon your OS. The simplest form is to …