Can I somehow let traefik retry obtaining certificates?
Currently I have many subdomains. Traefik is therefore running into the rate limit of letsencrypt on an initial run.
So I thought that traefik would retry obtaining those certificates later. This doesn't seem to be the case, however. Now it's four days later, since the original run and traefik didn't seem to try to obtain getting a certificate again since then.
Is there any config option (i.e. retry getting a new certificate every $time_window if traefik weren't able to get a certificate on the first run) or a way to trigger this manually?
6 years later, same question. I’m using Traefik as part of Pangolin and for me it’s when I try to use the DNS challenge (NameSilo is my provider). I’m encountering DNS propogation timeout, but when I go look in my DNS manager, I’m not seeing the TXT records getting created.
I stop the Pangolin/Gerbil/Traefik stack and then start it again with Docker compose down/up, and this causes Traefik to retry (but it endlessly fails).
Meanwhile if I just install lego itself and use it directly, it works. I have to set --dns.propagation-wait to 1200s so that it will wait 20 minutes, but it works. And I can try it on demmand with the lego.
Back to doing this via Traefik, via Pangolin, it’s a little painful and no reasoning in sight for what’s going wrong.
Restarting Traefik should trigger the process again. If you want to suggest a change to the devs, use Traefik Github.