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. crt.sh | 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:
I ran this command: certbot certonly --manual --force-renewal -d www.thermosoft.com
It produced this output:An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours: www.thermosoft.com: see Rate Limits - Let's Encrypt
Please see the logfiles in /var/log/letsencrypt for more details.
I was getting another error before trying few times. - Yes
It was saying privkey3.pem missing in archive folder
My web server is (include version): nginx
The operating system my web server runs on is (include version): ubuntu
My hosting provider, if applicable, is: linode
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 1.12.0
Never use --force-renewal; it's likely what got you into the problem you're in.
I'm not sure what could be clearer about that error message--you've created five identical certs for that hostname within the past week. Why not use one of those?
I see them in the log file as string "BEGIN Certificate" and "End Certificate". But my folder files are not updated. Is there any other way I can update the certificate?
I tried creating cert but the live folder is not updated with the keys. I tried it several times and did not see any file getting updated with the new certificates. After 4 unsuccessful tries, I started getting error stating you have reached the max limit.
The command below will use the test system and won't be affected by your Rate Limit on production. What does it say about success or failure for getting a cert?
As an aside, your cert history shows repeatedly getting multiple certs for the same domain name on the same day. I think you have a recurring problem. Possibly as a result of doing a --manual request and not automating it.
Although, your response headers say nginx v1.7.4. That is incredibly old and I would avoid using the nginx plug-in but using certonly with webroot instead of manual should work once you figure out why the manual method fails.
What exactly were you expecting to see, and what did you see? Files in /etc/letsencrypt/live/ are symbolic links; the name stays the same, but they update and point to new files in /etc/letsencrypt/archive.
Yeah i was hoping so see same files with updated dates as I would see in the past renewals. This time it is still showing files with 3/3/2022 dates when I last updated them.
I deleted the duplicate one and ran using the dry run command. It was successful in dry run. But I cannot run in the live environment as it has reached max limit. Is the max limit for week or from the time I used it first?
The following renewal configurations were invalid:
/etc/letsencrypt/renewal/www.thermosoft.com-0001.conf
/etc/letsencrypt/renewal/www.thermosoft.com-0002.conf