# Certbot renew --dry-run

**URL:** <https://community.letsencrypt.org/t/certbot-renew-dry-run/31151>\
**Category:** Help\
**Created:** [April 1, 2017, 7:31pm UTC](https://community.letsencrypt.org/t/certbot-renew-dry-run/31151 "2017-04-01T19:31:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sshuichi](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sshuichi/32/22277_2.png) [@Sshuichi](https://community.letsencrypt.org/u/Sshuichi)\
**Post date:** [April 1, 2017, 7:31pm UTC](https://community.letsencrypt.org/t/certbot-renew-dry-run/31151/1 "2017-04-01T19:31:05Z")

</div>

Please fill out the fields below so we can help you better.

My domain is:

> **[محكمتي – قرارات وأحكام مغربية من محكمة النقض ومحكمة الإستئناف والمحكمة...](https://www.mahkamaty.com/)**
>
> قرارات وأحكام مغربية من محكمة النقض ومحكمة الإستئناف والمحكمة الابتدائية. Mahkamati

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

It produced this output:  
Saving debug log to /var/log/letsencrypt/letsencrypt.log

```
-------------------------------------------------------------------------------
Processing /etc/letsencrypt/renewal/www.mahkamaty.com.conf
-------------------------------------------------------------------------------
Cert is due for renewal, auto-renewing...
Starting new HTTPS connection (1): acme-staging.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for www.mahkamaty.com
Waiting for verification...
Cleaning up challenges
Generating key (2048 bits): /etc/letsencrypt/keys/0001_key-certbot.pem
Creating CSR: /etc/letsencrypt/csr/0001_csr-certbot.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/www.mahkamaty.com/fullchain.pem (success)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)

```

My operating system is (include version):  
Ubuntu 16.04

My web server is (include version):  
Nginx ; nginx/1.10.0 (Ubuntu)

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):  
Yes

The problem is that the certificate doesn’t get updated when I visit my domain it still says that it will expire in 21 day.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [April 1, 2017, 9:17pm UTC](https://community.letsencrypt.org/t/certbot-renew-dry-run/31151/2 "2017-04-01T21:17:43Z")

</div>

> [@Sshuichi](#):
>
> The problem is that the certificate doesn't get updated (…)

Well, that's the whole point of `--dry-run`:

From the [`--help` command](https://certbot.eff.org/docs/using.html#certbot-command-line-options):

> --dry-run Test "renew" or "certonly" without saving any certs to disk

Also, the output of the command you ran clearly states:

> [@Sshuichi](#):
>
> \*\* DRY RUN: simulating 'certbot renew' close to cert expiry  
> \*\* (The test certificates above have not been saved.)

Simulating. Test certificates. Not saved. 🙂

---

<div class="post-metadata">

**Author:** ![Sshuichi](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sshuichi/32/22277_2.png) [@Sshuichi](https://community.letsencrypt.org/u/Sshuichi)\
**Post date:** [April 2, 2017, 9:44am UTC](https://community.letsencrypt.org/t/certbot-renew-dry-run/31151/3 "2017-04-02T09:44:37Z")

</div>

Thanks, when I run without dry run, I get an error, when I added sudo, it worked.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [May 2, 2017, 9:44am UTC](https://community.letsencrypt.org/t/certbot-renew-dry-run/31151/4 "2017-05-02T09:44:52Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.