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: renkaba.selfhost.eu
I ran this command: /usr/local/letsencrypt/letsencrypt-auto certonly -d renkaba.selfhost.eu --apache -m firstname.lastname@example.org
It produced this output: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error finalizing order :: too many certificates already issued for: selfhost.eu: see https://letsencrypt.org/docs/rate-limits/
My web server is (include version): apache2
The operating system my web server runs on is (include version): linux
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-auto --version
I tried to receive the certs several time. due to my ignorance I tried to often. Then I read the docs and installed certs from the staging server, which works (rate-limit higher). After that I tried several times to replace the staging server cert with a production one, but always got rate-limit error. So I gave up and waited one week after the first rate-limit error. This was yesterday and again I got rate-limit error (see above). Why? Does the rate-limit “clock” resets with every try, even I dont get a new cert? If not why does it not work after one week?