I have two certificate. The firts certificate with two domain: domian1.com, domain2.com, and the last certificate with one domain: domain3.com.
I used the command for automating renewal: sudo certbot renew --dry-run
But it show successfull only for the last certificate with one domain.
<p". Skipping.
The following certs could not be renewed:
/etc/letsencrypt/live/mail.nube22.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)
The following certs were successfully renewed:
/etc/letsencrypt/live/mx01.nube22.com/fullchain.pem (success)
The following certs could not be renewed:
/etc/letsencrypt/live/mail.nube22.com/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
Yes I do, I have a correct certificate.
My problem is when a run the automating renewal: certbot renew --dry-run.
I want to put it in automatic renewal so I do not worry afterwards.
With the info, that dry-run doesn't support some hooks.
Perhaps rerun the complete command (which created the certificate yesterday) and use the stage system (there is a certbot option). There is an own limit.
I’m a little confused. I thought that command: certbot renew --dry-run is for run automatic renewal certificate but I realize this command is only a test to verify that renewal will be successful.
I found the problem why the command: certbot renew --dry-run it gave me error.
I create my ceriticate for domian: mail.nube22.com that was host on directory /var/www/. I then I change the directory to /home/mail but do not modify the renewal file /etc/letsencrypt/renewal/mail.nube22.com.conf. When I update the directory in the renewal file the command: certbot renew --dry-run run successful.