rate limit SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

cert-manager: acme: urn:ietf:params:acme:error:rateLimited (too many certificates / failed validations)

Let's Encrypt rejected new orders because you hit a rate limit (duplicate certificates, failed validations, or new registrations).

Exact message you may see too many certificates already issued for exact set of domainstoo many failed authorizations recentlycert-manager rate limited Let's Encrypt429 urn:ietf:params:acme:error:rateLimited
Seen on: Kubernetes SSL

Meaning

Read which limit applies (50 certificates per registered domain per week, 5 duplicates per week, 5 failed validations per hour). Use the staging issuer while testing, stop retry loops, reuse existing secrets (avoid deleting the TLS Secret), and wait for the window to pass.

Common causes

  • Repeated certificate deletion/recreation
  • Failed validations in a loop
  • Too many duplicates of the same names
  • Many subdomains on one registered domain
  • Using production for tests

⚡ Quick fix

  1. Test with the staging issuer
  2. Keep TLS secrets between redeploys
  3. Wait for the limit window; consider a wildcard certificate

Detailed fix by platform

Shell

  1. bash
    kubectl describe order -A | grep -i ratelimit
    kubectl get certificate -A

How to diagnose

  1. Limit — Which?
  2. Staging — Used for tests?
  3. Secrets — Kept?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

4.7.28 — Gmail: 421 4.7.28 Our system has detected an unusual rate of unsolicited mail originating from your IP address (Email / SMTP)4.7.28420 — HTTP 420 Enhance Your Calm (HTTP)420421 4.7.0 Try again later (rate limited) — SMTP: 421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address. Mail sent from your IP address has been temporarily rate limited (Email / SMTP)421 4.7.0 Try again l…429 — 429 Too Many Requests: honouring Retry-After (HTTP)429ACM region — CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia) (SSL / TLS)ACM regionCaddy — Caddy: obtaining certificate failed — ACME challenge error (port 80/443 blocked or DNS wrong) (SSL / TLS)Caddycert-manager — cert-manager: Challenge stuck pending — HTTP-01 self check failed / waiting for ingress solver (SSL / TLS)cert-managerChallenge failed for domain — Let’s Encrypt / Certbot: Challenge failed for domain example.com — Invalid response from http://example.com/.well-known/acme-challenge/x: 404 (SSL / TLS)Challenge failed for …rate limit

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.