Multiple wildcard domains

[myugan]

The idea is to have a setting that allows the use of multiple wildcard domains. For example, when deploying Coolify, I want some services to be generated as xxx.domain.com for public testing, while other services are generated as yyy.domain.org for internal testing.

[joezimjs]

Yes please!

[mredodos]

+1

[Shadowfita]

+1 !

[Shadowfita]

This is achievable already when manually entering a domain that is wildcarded appropriately, but having proper UI / setting management for multiple domains would be great.

[hnykda]

Hey @Shadowfita ! Can you say more about how did you achieve that? I can't figure out what you meant

[FiliePepijn]

Did you manage to do this, if yes how?

[2F-112]

+1

[XEJK]

This would be an awesome addition to have

[hnykda]

I am somewhat surprised this is not possible. I tried various hacks with dynamic configuration, but didn't succeeded, sadly.

[djsisson]

image one, is only for specifying a default pattern to generate a random subdomain from for a new app, so this has to be just one domain

the bottom image, ive no idea what you are trying to do, why are you trying to block certificate generation?

the middle image is the correct approach, if you need multiple domains, you add as a comma seperated list

but none of this is wildcard related

please note if you want the pattern *.xxx.com to go to one app, you need to use dns challenge you cannot use http challenge, you also need to use hostregexp for the rule definition

[hnykda]

Eh... Thanks for helping! I now do realize that I commented on a wrong thread. But I still can't get it to work. Let's focus on what you think I am doing right:

the middle image is the correct approach, if you need multiple domains, you add as a comma seperated list

E.g .the second domain from the four, when accessed in incognito on my PC, doesn't have a let's encrypt cert generated:

the first one - the wildcard one I use for other projects - does work fine. Traefik logs show:

2025-09-09T15:26:44.203853649Z time="2025-09-09T15:26:44Z" level=error msg="Unable to obtain ACME certificate for domains \"mydomain.cz\": unable to generate a certificate for the domains [mydomain.cz]: error: one or more domains had a problem:\n[mydomain.cz] invalid authorization: acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: 2a02:2b88:1:4::16: Invalid response from http://mydomain.cz/.well-known/acme-challenge/9d4nBfuOJf9psDPyS4jlk-3MSfnsfy8yJai6e0-CwBk: 404\n" providerName=letsencrypt.acme ACME CA="https://acme-v02.api.letsencrypt.org/directory" routerName=https-3-l0kg8ksosgk0wks40ggs8oww@docker rule="Host(`mydomain.cz`) && PathPrefix(`/`)"

[djsisson]

this could be a number of things, but ultimately lets encrypt failed to get a response from the provided domain name

if this was a new A record added, then it could be a timing issue, where it still had an old record or none at all for that name

as a test you can restart the container or the proxy, this will force traefik to try the request again.

if it still fails, then you will need to ask on lets encrypt forums, as this is not something coolify has any control over

edit make sure you are not using a dns proxy for this domain name as that blocks http certificate generation

[hnykda]

I get it, I made a mistake and thought this is not supported, but there is a different reason why this fails, I am sorry and thanks for patience.

[hnykda]

The problem was not having AAAA records (I thought A is enough)...