[GH-ISSUE #464] Wildcard Certs in Multiple Domains #1469

New Issue

2026-04-16T08:07:18-05:00

GiteaMirror commented

2026-04-16 08:07:18 -05:00

Originally created by @Tanhueco on GitHub (Apr 5, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/464

I tried this out but the website does not come up. Is it possible to have wildcard certificates issued to mutiple domains?

dynamic_config.yml:

next-router:
   entryPoints:
     - websecure
   middlewares:
     - security-headers
   rule: Host(`proxy.domain1.com`) && !PathPrefix(`/api/v1`)
   service: next-service
   tls:
     certResolver: letsencrypt
     domains[0]:
       - main: "domain1.com"
         sans:
           - "*.domain1.com"
     domains[1]:
       - main: "domain2.com"
         sans:
           - "*.domain2.com"

A single domain works ok:

next-router:
   entryPoints:
     - websecure
   middlewares:
     - security-headers
   rule: Host(`proxy.domain1.com`) && !PathPrefix(`/api/v1`)
   service: next-service
   tls:
     certResolver: letsencrypt
     domains:
       - main: "domain1.com"
         sans:
           - "*.domain1.com"

Originally created by @Tanhueco on GitHub (Apr 5, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/464 I tried this out but the website does not come up. Is it possible to have wildcard certificates issued to mutiple domains? dynamic_config.yml: next-router: entryPoints: - websecure middlewares: - security-headers rule: Host(`proxy.domain1.com`) && !PathPrefix(`/api/v1`) service: next-service tls: certResolver: letsencrypt domains[0]: - main: "domain1.com" sans: - "*.domain1.com" domains[1]: - main: "domain2.com" sans: - "*.domain2.com" A single domain works ok: next-router: entryPoints: - websecure middlewares: - security-headers rule: Host(`proxy.domain1.com`) && !PathPrefix(`/api/v1`) service: next-service tls: certResolver: letsencrypt domains: - main: "domain1.com" sans: - "*.domain1.com"

GiteaMirror closed this issue

2026-04-16 08:07:18 -05:00

GiteaMirror commented

2026-04-16 08:07:20 -05:00

@Lokowitz commented on GitHub (Apr 5, 2025):

Hi Tanhueco,

when i remember correct it should work like this:

     domains:
       - main: "domain1.com"
         sans:
           - "*.domain1.com"
       - main: "domain2.com"
         sans:
           - "*.domain2.com"

Are you using the same provider for all domains?

@Lokowitz commented on GitHub (Apr 5, 2025): Hi Tanhueco, when i remember correct it should work like this: ``` domains: - main: "domain1.com" sans: - "*.domain1.com" - main: "domain2.com" sans: - "*.domain2.com" ``` Are you using the same provider for all domains?

GiteaMirror commented

2026-04-16 08:07:20 -05:00

@Tanhueco commented on GitHub (Apr 5, 2025):

@Lokowitz, That works!

Yes, all domains are from the same provider.

@Tanhueco commented on GitHub (Apr 5, 2025): @Lokowitz, That works! Yes, all domains are from the same provider.

GiteaMirror commented

2026-04-16 08:07:21 -05:00

@miloschwartz commented on GitHub (Apr 11, 2025):

Thanks @Lokowitz!

@miloschwartz commented on GitHub (Apr 11, 2025): Thanks @Lokowitz!

GiteaMirror commented

2026-04-16 08:07:21 -05:00

@nlsrchtr commented on GitHub (Aug 8, 2025):

Hi @Lokowitz,

could you help me out, when I have multiple wildcard domains with different providers? How would I adjust the certificatesResolvers in a way, that it would pick up the correct configuration per domain?

certificatesResolvers:
  letsencrypt:
    acme:
      httpChallenge:
        entryPoint: web
      email: hello@example.com # REPLACE THIS WITH YOUR EMAIL
      storage: "/letsencrypt/acme.json"
      caServer: "https://acme-v02.api.letsencrypt.org/directory"

Thanks a lot for your help or any pointers!

Regards,

@nlsrchtr commented on GitHub (Aug 8, 2025): Hi @Lokowitz, could you help me out, when I have multiple wildcard domains with different providers? How would I adjust the certificatesResolvers in a way, that it would pick up the correct configuration per domain? ```yaml certificatesResolvers: letsencrypt: acme: httpChallenge: entryPoint: web email: hello@example.com # REPLACE THIS WITH YOUR EMAIL storage: "/letsencrypt/acme.json" caServer: "https://acme-v02.api.letsencrypt.org/directory" ``` Thanks a lot for your help or any pointers! Regards,

GiteaMirror commented

2026-04-16 08:07:22 -05:00

@Lokowitz commented on GitHub (Aug 9, 2025):

Hi @nlsrchtr
according to the traefik docs, it is not supported. But there is a workaround:

Multiple DNS challenge provider are not supported with Traefik, but you can use CNAME to handle that. For example, if you have example.org (account foo) and example.com (account bar) you can create a CNAME on example.org called _acme-challenge.example.org pointing to challenge.example.com. This way, you can obtain certificates for example.org with the bar account.

@Lokowitz commented on GitHub (Aug 9, 2025): Hi @nlsrchtr according to the traefik [docs](https://doc.traefik.io/traefik/https/acme/#dnschallenge), it is not supported. But there is a workaround: > Multiple DNS challenge provider are not supported with Traefik, but you can use CNAME to handle that. For example, if you have example.org (account foo) and example.com (account bar) you can create a CNAME on example.org called _acme-challenge.example.org pointing to challenge.example.com. This way, you can obtain certificates for example.org with the bar account.