⏳
blog.cat.ssl

Let's Encrypt Rate Limits: Fixing "too many certificates"

21.11.2026
← All articles

Let's Encrypt issues free certificates to millions of sites and caps request volume to protect itself from abuse and buggy scripts. Normal use rarely touches these limits, because a certificate renews only every few months. Trouble usually starts during setup, repeated retries or badly written automation, when the client returns an error containing "too many certificates" or "rateLimited" and issuance stops for a while. Exact values change over time, so always confirm the numbers on the official Let's Encrypt "Rate Limits" page.

The most common one: duplicate certificates

You cannot issue more than five certificates for the exact same set of names within seven days. The error tells you when you can try again:

too many certificates (5) already issued for this exact set of
identifiers in the last 168h0m0s, retry after 2026-11-08 14:20:00 UTC

"Exact set" means every name matches. If misol.uz plus www.misol.uz is blocked, a certificate for misol.uz alone is a different set and may still be issued. That is a stopgap, not a fix.

A Docker example

A private school in Tashkent runs maktab.misol.uz in Docker. The container requests a certificate on start, but /etc/letsencrypt is not on a persistent volume, so every restart loses the old certificate and asks for a new one. A few deploys in one day exhaust the limit and the site stays without HTTPS for a week. Persist the directory and the client will reuse the existing certificate.

services:
  certbot:
    image: certbot/certbot
    volumes:
      - ./letsencrypt:/etc/letsencrypt
      - ./webroot:/var/www/certbot

The weekly per-domain limit

Let's Encrypt treats misol.uz and all its subdomains as one registered domain and limits new certificates for it, currently 50 per week. Small sites never notice, but services that give every customer a subdomain with its own certificate can. Use a wildcard (*.misol.uz, via DNS-01) or combine names, up to 100 per certificate.

Planning matters here. If you expect to onboard dozens of customers in a single week, a wildcard certificate removes the per-subdomain bottleneck entirely, because one certificate covers every new subdomain the moment it is created. The trade-off is that DNS-01 needs API access to your zone, so restrict that token to DNS edit on a single zone.

Failed validation limits

If validation keeps failing because DNS points elsewhere or port 80 is closed, you will see "too many failed authorizations recently". Hostnames that fail continuously for a long time can even be paused. Treat it as a signal to fix the domain or server first:

dig +short misol.uz A
curl -I http://misol.uz/.well-known/acme-challenge/test

Experiment on staging

The staging environment has much higher limits and issues untrusted test certificates. Test every new setup there first, and only then request a real certificate. Keep staging data separate so a test certificate never ends up in production.

certbot renew --dry-run
certbot certonly --staging --webroot -w /var/www/misol.uz -d misol.uz

If you are already blocked

Limits cannot be lifted manually; wait for the "retry after" time. Meanwhile, check whether a valid certificate already exists but simply isn't wired into the web server. If not, request a different name set or temporarily use another free ACME CA. Certificate Transparency search tools show every certificate issued for your domain, which helps identify the runaway script.

certbot certificates
ls -l /etc/letsencrypt/live/

Automate sensibly

Cron jobs or deploy hooks with a permanent --force-renewal are the usual culprits. Let the client decide: certbot renew only renews certificates with fewer than 30 days left. On sayt.uz shared hosting the panel handles issuance and renewal for you; on a VPS or in Docker, persist certificates, test on staging and avoid forced renewals.

Related articles

📧 SSL for mail.domain.uz: Fixing the Outlook Certificate Warning 📜 Certificate Transparency: How Public Logs of SSL Certificates Work 🏢 SSL for internal (intranet) sites: how to secure office systems 🔐 What Is Perfect Forward Secrecy and How It Protects Your Site
🌐 Language
🇺🇿 O⁠'zbek 🇺🇿 Özbek (yangi) 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓