Options for adding/removing domains on the fly dynamically? Advice for thousands of domains?

[milkshake]

I have not setup a caddy server yet, but want to understand my options for adding/removing domains from the system.

When adding a domain, is the only option to update the configuration file with the domain? How do systems with thousands or more domains do this, or is the configuration file able to handle this type of scenerio?

Any advice from others who use caddy with thousands of domains would be great!

[francislavoie]

You’re looking for On-Demand TLS:

Automatic HTTPS - Caddy Documentation

[matt (Matt Holt)]

Yep, and this wiki guide can help with understanding it:

Serving tens of thousands of domains over HTTPS with Caddy

This guide is a free sample of what is available exclusively for sponsors in my Expert Caddy series, where I help you master the ways of the Caddy web server. (This guide is still WIP.) Many online businesses have invested thousands, even millions, of dollars for custom software and proprietary solutions to serve their customers’ websites over HTTPS. These traditional methods then cost thousands of dollars per year to maintain it in infrastructure, engineering, and payroll. I’ll show you how …

Once you get this set up, please consider sponsoring the project . Caddy is the only server that can do this for you (esp. for free).

[milkshake]

So what exactly does this endpoint have to return, just a 200 OK status with no body required?

[francislavoie]

That’s right. Caddy makes a GET request with a ?domain= query, and on a 200 OK it will continue with cert issuance, on any 4xx or 5xx status it will give up and fail the pending TLS handshake.