Caddy proxy with on_demand_tls global setting

[adamghill]

I understand that Caddy is not the first choice as a proxy (as mentioned in the docs), however I am currently using it for its on_demand_tls feature which seems to work well. Basically, I was looking to support something like bearblog's Caddyfile for my own app.

One thing I am running into is that sometimes (I can't exactly figure out why/when), Coolify seems to overwrite any changes I make to /data/coolify/proxy/dynamic/Caddyfile. Unfortunately, for on_demand_tls to work something like

{
    on_demand_tls {
        ask https://example.com/ping
    }
}

must be a global setting and it needs to be read first, i.e. before the import, so I can't have it loaded dynamically in a caddy file (I don't think).

Is there a way to prevent Coolify from overwriting the Caddyfile (or a way to change the default Caddyfile)?

I'm also open to using Traeffik if it has a similar on-demand TLS feature, but from what I can tell it might not be supported?

[dbondarchuk]

I managed to do it:

1. In your Server->Proxy, add the following labels in the Docker Compose file for Caddy (Coolify Proxy):

- caddy.on_demand_tls=
- caddy.on_demand_tls.ask=http://domain-checker:5555/check

If you are using "internal" service (like from Docker Compose), you need to specify the service name, as {{upstreams}} won't work
Also, disable Override default request handler if it is enabled.

2. Add a new Dynamic configuration to proxy (i.,e tls_on_demand.caddy):

https:// {
    tls {
        on_demand
    }
    reverse_proxy web-app:3000  
}

Again, use the Docker container hostname in order for it to work

It works great with services spun up by Coolify