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: mydomain.com.br
I ran this command: ./certbot-auto certonly --webroot -w /home/mydomainadm/public_html --cert-name mydomain.com.br -d mydomain.com.br
and
./certboot-auto renew
It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for mydomain.com.br
Using the webroot path /home/mydomainadm/public_html for all unmatched domains.
Waiting for verification…
Cleaning up challenges
An unexpected error occurred:
There were too many requests of a given type :: Error finalizing order :: too many certificates already issued for exact set of domains: mydomain.com.br: see https://letsencrypt.org/docs/rate-limits/
Please see the logfiles in /var/log/letsencrypt for more details.
My web server is (include version): Server version: Apache/2.4.23 (Linux/SUSE)
Server built: 2018-01-29 10:40:58.000000000 +0000
The operating system my web server runs on is (include version): OpenSuSE - 4.4.120-45-default #1 SMP Wed Mar 14 20:51:49 UTC 2018 (623211f) x86_64 x86_64 x86_64 GNU/Linux
My hosting provider, if applicable, is: bymyself
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): no
You’ll want to figure out what has been issuing these duplicate certificates, because indeed you are over the rate limit.
Have you been intentionally re-issuing new certificates when Certbot has asked you?
What does this show:
./certbot-auto certificates
Make sure you reload Apache as well, because since you are using certonly, Certbot does not do this for you unless you tell it to, and it’s required in order for Apache to pick up the renewed certificate:
Q: Have you been intentionally re-issuing new certificates when Certbot has asked you?
A: yes, trying solve error repeat proccess some times.
./certbot-auto certificates show:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Revocation status for /etc/letsencrypt/live/otherdomain.com.br/cert.pem is unknown
Found the following certs:
Certificate Name: mydomain.com.br
Domains: mydomain.com.br
Expiry Date: 2018-10-09 13:55:45+00:00 (INVALID: EXPIRED)
Certificate Path: /etc/letsencrypt/live/mydomain.com.br/fullchain.pem
Private Key Path: /etc/letsencrypt/live/mydomain.com.br/privkey.pem
… and others domains …
Q: Make sure you reload Apache as well,…
A: yes, I did.
That is really weird. Are you 100% sure none of the other certificates listed are for mydomain.com.br ?
Otherwise, it would appear that Certbot issues the certificate but then doesn't actually save it to disk. It seems unlikely though.
ls /etc/letsencrypt/live
Would you be able to check the log files from /var/log/letsencrypt/ (specifically, those that correlate to the certificates issued on 2018-10-08 and 2018-10-10) and post the contents of one?
step 1:
./certbot-auto certonly --webroot -w /home/mydomain/public_html --cert-name mydomain.com.br -d mydomain.com.br
this not solve
step2:
./certboot-auto renew
this not solve too
I try this steps some times (6 exact) to try solve.
Additiona info: my cert was running fine to last saturday. So validate date was expired and I start the renew procedure, resulting in thus issue, caused for my low domain with certboot tools.
Hello!
For help somebody with same problem.
Solution was:
find files on /etc/letsencrypt/archive/mydomain.com.br
check dates for most recent files, in my case cert4.pem, chain4.pem, fullchain4.pem and privkey4.pem, like show below:
use ln command to update the symbolic link of files on folder /etc/letsencrypt/live/mydomain.com.br like this:
cd /etc/letsencrypt/live/mydomain.com.br
ln -sf …/…/archive/mydomain.com.br/cert4.pem cert.pem
ln -sf …/…/archive/mydomain.com.br/chain4.pem chain.pem
ln -sf …/…/archive/mydomain.com.br/fullchain4.pem fullchain.pem
ln -sf …/…/archive/mydomain.com.br/privkey4.pem privkey.pem
rcapache2 reload