Too many certificates

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
api.mailshogun.com

I ran this command:
cerbot

It produced this output:
There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: api.mailshogun.com:

My web server is (include version):
nginx

The operating system my web server runs on is (include version):
ubuntu 18.04

My hosting provider, if applicable, is:

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):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):certbot 0.31.0

------------------------ MY QUESTION -----------------------------------------------------------------------------------------
I dont remember i have done many retries. question is- how much time I have to wait? How I know how many retries were done?

2

Hi @nickpp

your configuration looks buggy.

Checking your domain and the CT-Log, you see ( https://check-your-website.server-daten.de/?q=api.mailshogun.com#ct-logs ):

Issuer not before not after Domain names LE-Duplicate next LE
Let's Encrypt Authority X3 2019-07-02 2019-09-30 api.mailshogun.com - 1 entries duplicate nr. 5 next Letsencrypt certificate: 2019-07-03 06:33:09
Let's Encrypt Authority X3 2019-07-02 2019-09-30 api.mailshogun.com - 1 entries duplicate nr. 4
Let's Encrypt Authority X3 2019-07-01 2019-09-29 api.mailshogun.com - 1 entries duplicate nr. 3
Let's Encrypt Authority X3 2019-06-30 2019-09-28 api.mailshogun.com - 1 entries duplicate nr. 2
Let's Encrypt Authority X3 2019-06-26 2019-09-24 api.mailshogun.com - 1 entries duplicate nr. 1
Let's Encrypt Authority X3 2019-06-25 2019-09-23 api.mailshogun.com - 1 entries
Let's Encrypt Authority X3 2019-06-24 2019-09-22 api.mailshogun.com - 1 entries
Let's Encrypt Authority X3 2019-06-24 2019-09-22 api.mailshogun.com - 1 entries
Let's Encrypt Authority X3 2019-06-23 2019-09-21 api.mailshogun.com - 1 entries

Your Server creates 5 certificates, that hits the limit, then the next 5. That startet 2019-06-01, you have created 24 active certificates.

But you don't use one of these certificates, instead you use

CN=apidev.mailshogun.com
	02.07.2019
	30.09.2019
expires in 90 days	apidev.mailshogun.com - 1 entry

with the wrong name.

  1. Use
certbot certificates

to find the newest certificate.

  1. Use
nginx -T

to find your vHost, there change the certificate file, restart your nginx.

  1. Share your renew command. Perhaps you use the wrong --force-renewal in your config file or command.

The standard: Create one certificate, then use this 60 - 85 days, then create the next.

1 Like
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.