- Plesk for Linux
- Plesk for Windows
Let's Encrypt certificate cannot be issued for securing Plesk with the following error:
PLESK_ERROR: Error: Could not issue a Let's Encrypt SSL/TLS certificate for vpsXXXXXX.vps.example.com. The "Certificates per Registered Domain" rate limit has been exceeded for vpsXXXXXX.vps.example.com. Let's Encrypt allows no more than 20 certificates to be issued per registered domain, per week. See the related Knowledge Base article for details. Details Invalid response from https://acme-v01.api.letsencrypt.org/acme/new-cert. Details: Type: urn:acme:error:rateLimited Status: 429 Detail: Error creating new cert :: too many certificates already issued for: vps.example.com: see https://letsencrypt.org/docs/rate-limits/
Plesk is running on the virtual private server (vps) and the hostname of the server was set by hosting provider automatically during the server deployment, e.g vpsXXXXXX.vps.example.com:
Note: If this symptom doesn't met, refer to this article.
Limit Certificates per Registered Domain which is the one of the Let's Encrypt rate limits has been exceeded for the domain vps.example.com
Some hosting providers give hostnames to VPS instances which are located in the same domain zone (vps.example.com).
According to the Let's Encrypt's documentation, subdomains from the same domain zone like example.com and blog.example.com are having the same rate limit. Thus, when first 20 domains of vps.example.com will get the certificate, the rest need to wait for a week.
There are 2 possible workarounds for such case:
- Rename the host to the existing unique domain name.
- Wait for this week period to pass and issue certificate one of the first.