Wildcard Certs in Multiple Domains #1640

Closed
opened 2026-04-05 19:38:03 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Tanhueco on 4/5/2025

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 4/5/2025* 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"
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#1640