What do i really have to do? how can i see wich is my sutuaction? how can i fix it, in case i’m wrong?
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.
Thanks for your fast reply. So my renew may fail on february? if yes it is critical situation endeed. I dont know what “try .–preferred-challenges http” means. Do I have to add that to any script?
I’m not expert only another user, but a read somewhere that:
open /etc/letsencrypt/cli.ini
and add to the end: preferred-challenges = http
than renew the certboot with dryrun to check any error.
After anything is fine, than renew the certboot.
Could you help me pls…
What if i dont want to use port:80?
How can i solve the emailed tls-sni question.
My cetbot – version is: 0.26.1
I have only one domain.
BUT i do not use the standard ports: 80 and 443. I use anothers instead.
The cerbot is working fine know, but i do not know what will be later.
I ran this commands to do the certbot update: sudo apt-get update
sudo apt-get install software-properties-common sudo add-apt-repository universe
sudo add-apt-repository ppa:certbot/certbot sudo apt-get update
sudo apt-get install python-certbot-apache
Now the certbot version is 0.28.0.
I ran again “sudo certbot renew --dry-run” and this is the result. Can you tell me if now finally i am using http validation as you suugested, instead of TLS-SNI-01? and if i am now OK for further renewals, or i have to change something else?
Here the result of “sudo certbot renew --dry-run”:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for kevingston.com
http-01 challenge for www.kevingston.com
Waiting for verification…
Cleaning up challenges
new certificate deployed with reload of apache server; fullchain is
/etc/letsencrypt/live/kevingston.com/fullchain.pem
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates below have not been saved.)
Congratulations, all renewals succeeded. The following certs have been renewed:
/etc/letsencrypt/live/kevingston.com/fullchain.pem (success)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)