How to setup subdomain wildcard (e.g. *.subdomain.root.com)

[hnykda]

Hi. Coolify seems to work great with my A record being *.domain.com - adding https://service.domain.com to service domains works great.

I tried doing *.sub.domain.com (by adding CNAME to point to my coolify instance), but that doesn't seem to work - when I added assign https://service.sub.domain.com, I am getting the classic SSL error and I am not getting through. I checked the docs such as Wildcard certificates but that seems to be something like if I want to dynamically generate those manually, which I don't - I want coolify's magic as with the simple case. I tried some approaches like setting the server's domain, and so on, but I apparently didn't find out the right switch. I otherwise have very-vanilla-mostly-default-settings, and stuff work.

Any hints or ideas? Thanks!

[hnykda]

Eh, I don't know what happened, but I just redeployed everything and it works now.

[Sardonyx001]

Hi!
Can you please tell us more about how you set this up?
I have a bunch of related apps and I want to deploy them all from the same docker compose file under the same subdomain: so they'll be like:
docs.app.rootdomain.com
demo.app.rootdomain.com
blog.app.rootdomain.com
etc..

do i just add a CNAME *.app.rootdomain.com for rootdomain.com?

[hnykda]

Yes, that should just work, I am using it. Doesn't it?

[Sardonyx001]

I kept getting SSL errors while and then i read the cloudflare DNS docs and realized they dont automatically cover TLS for multilevel domains on the free plan :

I will try again with caddy as a reverse proxy inside the containers since they offer on_demand certificates...

[hnykda]

I use just pure letsencrypt and a bare VM, so that might be the reason. That works just fine, tested on two different coolify instances and domains.

[Sardonyx001]

Might be worth trying out letsencrypt.. Although caddy has it built it and (somehow) works with coolify although setting it up was a bit of a pain