I’m using Traefik (Kubernetes) and ACME configuration with Let’s Encrypt. A working certification is configured the first time, but when delete Kubernetes and try to configure the certificate (with the exact same script) I get “rate limit” error message.
I ran this command: Traefik with ACME and Let’s Encrypt integration.
It produced this output:
{“level”:“error”,“msg”:“Unable to obtain ACME certificate for domains “matsorg.at21.altinn.studio” : unable to generate a certificate for the domains [matsorg.at21.altinn.studio]: acme: Error -\u003e One or more domains had a problem:\n[matsorg.at21.altinn.studio] acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/finalize/56990546/448026790 :: urn:ietf:params:acme:error:rateLimited :: Error finalizing order :: too many certificates already issued for exact set of domains: matsorg.at21.altinn.studio: see https://letsencrypt.org/docs/rate-limits/, url: \n”,“time”:“2019-05-13T12:20:02Z”}
My web server is (include version): Traefik 1.7.9
The operating system my web server runs on is (include version): *
My hosting provider, if applicable, is: Azure
I can login to a root shell on my machine (yes or no, or I don’t know): Yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): N/A
It sounds like since you're deleting the resources and recreating them identically that perhaps you're testing your setup? If so using the staging environment next time will save you this rate limiting trouble.
Thanks @JuergenAuer
Your link was more updated than my “lets debug” link.
Yes @cpu
I’ve tested both staging and “not staging”. On friday it looked like I also reached the rate limit, but it might’ve been something else. I didn’t think I’ve created all these certificates outside staging…
Thanks!