DRY RUN: simulating 'certbot renew' close to cert expiry


#1

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: canadianposcorp.com

I ran this command:certbot renew --dry-run

It produced this output: Congratulations, all renewals succeeded

My web server is (include version): Ubuntu 14.04.5 LTS \n \l nginx

The operating system my web server runs on is (include version):nginx

My hosting provider, if applicable, is: no

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 0.21.1

=================================================

Hi there. my question. is why i am getting this message what does it mean?

DRY RUN: simulating ‘certbot renew’ close to cert expiry

root@canadianposcorp:/home/ubuntu# certbot renew --dry-run
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/canadianposcorp.com.conf

Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for canadianposcorp.com
Waiting for verification…
Cleaning up challenges


new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/canadianposcorp.com-0001/fullchain.pem


Processing /etc/letsencrypt/renewal/canadianposcorp.com-0001.conf

Cert not due for renewal, but simulating renewal for dry run
Plugins selected: Authenticator webroot, Installer None
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for canadianposcorp.com
Waiting for verification…
Cleaning up challenges


new certificate deployed without reload, fullchain is
/etc/letsencrypt/live/canadianposcorp.com-0001/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/canadianposcorp.com-0001/fullchain.pem (success)
/etc/letsencrypt/live/canadianposcorp.com-0001/fullchain.pem (success)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)


#2

Hi @Aku

first you should update your Certbot. This version looks too old.


#3

i will update it thanks for you reply.
what is this meaning

[DRY RUN: simulating ‘certbot renew’ close to cert expiry


#4

If you use --dry-run, Certbot uses the test system to create a test certificate.

If that works, the same should work with the main system and a correct certificate.


#5

Thank you so much Juergen.Just two more question

  1. how we can find which method we are using
    TLS-SNI-01 OR HTTP-01

  2. what is the difference between certbot and certbot-auto

Again thank you so much for your time.


#6

Check your logs:

Certbot comes platform-specific and has dns-plugins, Certbot-Auto is independend, has an Auto-update, but reduced or no dns-01 - validation support.