# Confirm LetsEncrypt/Certbot renew script installed?

**URL:** <https://community.letsencrypt.org/t/confirm-letsencrypt-certbot-renew-script-installed/134943>\
**Category:** Help\
**Created:** [September 30, 2020, 5:48pm UTC](https://community.letsencrypt.org/t/confirm-letsencrypt-certbot-renew-script-installed/134943 "2020-09-30T17:48:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamdev](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@jamdev](https://community.letsencrypt.org/u/jamdev)\
**Post date:** [September 30, 2020, 5:48pm UTC](https://community.letsencrypt.org/t/confirm-letsencrypt-certbot-renew-script-installed/134943/1 "2020-09-30T17:48:45Z")

</div>

Apologies if this is really trivial, but I am just wondering if it is still necessary to create a cron job with certbot renew command in it? I followed the instructions here for installing certbot: [https://certbot.eff.org/lets-encrypt/ubuntubionic-apache](https://certbot.eff.org/lets-encrypt/ubuntubionic-apache)

The doc says there is a script installed in one of the following:  
/etc/crontab/  
/etc/cron._/_  
systemctl list-timers

I ran this command: `systemctl list-timers`

It produced this output: `Thu 2020-10-01 11:04:00 UTC 17h left Wed 2020-09-30 16:17:10 UTC 1h 21min ago snap.certbot.renew.timer snap.certbot.renew.service`

My web server is (include version): Apache

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

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

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): certbot 1.8.0

---

<div class="post-metadata">

**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\
**Post date:** [September 30, 2020, 6:42pm UTC](https://community.letsencrypt.org/t/confirm-letsencrypt-certbot-renew-script-installed/134943/2 "2020-09-30T18:42:13Z")

</div>

Hello @jamdev!  
Welcome to the community!  
Check the output of:

```auto
systemctl list-units --all | grep certbot 

```

And if the result looks something like:  
`128: certbot.service	loaded inactive dead Certbot `  
`289: certbot.timer loaded active waiting Run certbot twice daily `

You're good to go!

---

<div class="post-metadata">

**Author:** ![jamdev](https://avatars.discourse-cdn.com/v4/letter/j/d26b3c/32.png) [@jamdev](https://community.letsencrypt.org/u/jamdev)\
**Post date:** [September 30, 2020, 7:05pm UTC](https://community.letsencrypt.org/t/confirm-letsencrypt-certbot-renew-script-installed/134943/3 "2020-09-30T19:05:33Z")

</div>

Thanks for the timely reply! I ran the command and got this:  
snap-certbot-579.mount loaded active mounted Mount unit for certbot, revision 579  
snap.certbot.renew.service loaded inactive dead Service for snap application certbot.renew snap.certbot.renew.timer loaded active waiting Timer renew for snap application certbot.renew

---

<div class="post-metadata">

**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\
**Post date:** [September 30, 2020, 7:11pm UTC](https://community.letsencrypt.org/t/confirm-letsencrypt-certbot-renew-script-installed/134943/4 "2020-09-30T19:11:55Z")

</div>

Excellent!  
You should be able to rely on the timer to do what it is supposed to do.  
Your certbot snap is up to date! YAY!  
Good Job!  
Rip

---

<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:** [October 30, 2020, 7:12pm UTC](https://community.letsencrypt.org/t/confirm-letsencrypt-certbot-renew-script-installed/134943/5 "2020-10-30T19:12:03Z")

</div>

Closed on October 30, 2020, 7:12pm UTC

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