You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are providing a service where people can create their own pages and connect them with their own domains.
Currently all domains are listed as additional DNS-Names when issuing a new certificate for our own domain. The issued certificate/created secret is then used in the context of a Traefik IngressRoute.
As the ratelimit from let's encrypt (https://letsencrypt.org/docs/rate-limits/) describes that we have a limit of 100 domains per certificate and we can only renew each certificate 50 times a week, we wonder what will happen if we breach the limit of 100 Domains. Is there some kind of internal splitting into multiple certificates? If not, what would be your suggestion for solving such a problem/handling such a use case?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi Community!
We are providing a service where people can create their own pages and connect them with their own domains.
Currently all domains are listed as additional DNS-Names when issuing a new certificate for our own domain. The issued certificate/created secret is then used in the context of a Traefik IngressRoute.
As the ratelimit from let's encrypt (https://letsencrypt.org/docs/rate-limits/) describes that we have a limit of 100 domains per certificate and we can only renew each certificate 50 times a week, we wonder what will happen if we breach the limit of 100 Domains. Is there some kind of internal splitting into multiple certificates? If not, what would be your suggestion for solving such a problem/handling such a use case?
Thanks in advance :)
Beta Was this translation helpful? Give feedback.
All reactions