# Certbot renew dns53 domains

**URL:** <https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561>\
**Category:** Help\
**Created:** [October 31, 2023, 2:24pm UTC](https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561 "2023-10-31T14:24:31Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![milan.m](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@milan.m](https://community.letsencrypt.org/u/milan.m)\
**Post date:** [October 31, 2023, 2:24pm UTC](https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561/1 "2023-10-31T14:24:31Z")

</div>

My domain is: [example.com](http://example.com)

I ran this command: sudo certbot certonly --dns-route53 --dns-route53-propagation-seconds 30 -d [alpha.example.com](http://alpha.example.com) -d [example.com](http://example.com) -d [developers.example.com](http://developers.example.com) -d [www.example.com](http://www.example.com) -d [docs.example.com](http://docs.example.com) -d [go.example.com](http://go.example.com) -v  
and after this i run sudo service httpd restart  
It produced this output: it is renewing the certificate perfectly without problem. I want to automate this like every 65 days to renew it or everyday, I don't know if it is good to renew it every day. Can you help me ?

My web server is (include version): apache 2.4

The operating system my web server runs on is (include version): amazon linux 2

My hosting provider, if applicable, is: amazon

The version of my client is certbot 1.11.0

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [October 31, 2023, 2:33pm UTC](https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561/2 "2023-10-31T14:33:41Z")

</div>

With Certbot, you normally renew your cert with the command

```plaintext
sudo certbot renew

```

with a cron job or systemd timer. And, this may have already been setup during install of Certbot. If not, [see link here](https://eff-certbot.readthedocs.io/en/latest/using.html#automated-renewals) for instructions on setting this up

You should also add `--deploy-hook "service httpd reload"` to your `certbot certonly` command. This will allow the certbot renew to reload your Apache server automatically whenever it gets a fresh cert. A reload is less disruptive than a restart.

The Cerbot renew is run at least once / day. It first looks at your existing cert. If it is fresh enough then nothing more is done. When it has less than 30 days left before expiry it will request a fresh cert.

---

<div class="post-metadata">

**Author:** ![milan.m](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@milan.m](https://community.letsencrypt.org/u/milan.m)\
**Post date:** [October 31, 2023, 2:51pm UTC](https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561/3 "2023-10-31T14:51:49Z")

</div>

When I list the cron jobs I don't see a certbot auto renew job ? Does it means that there is no cron job for certbot renew?

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [October 31, 2023, 2:53pm UTC](https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561/4 "2023-10-31T14:53:09Z")

</div>

> [@milan.m](#):
>
> Does it means that there is no cron job for certbot renew?

Did you check the systemd timers as described in the link I provided?

---

<div class="post-metadata">

**Author:** ![milan.m](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@milan.m](https://community.letsencrypt.org/u/milan.m)\
**Post date:** [October 31, 2023, 2:54pm UTC](https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561/5 "2023-10-31T14:54:20Z")

</div>

Yes, also no timer. I was thinking to add a job  
0 0 \*/70 \* \* sudo certbot certonly --dns-route53 --dns-route53-propagation-seconds 30 -d [alpha.example.com](http://alpha.example.com) -d [example.com](http://example.com) -d [developers.example.com](http://developers.example.com) -d [www.example.com](http://www.example.com) -d [docs.example.com](http://docs.example.com) -d [go.example.com](http://go.example.com) && sudo service httpd reload

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [October 31, 2023, 3:10pm UTC](https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561/6 "2023-10-31T15:10:07Z")

</div>

> [@milan.m](#):
>
> I was thinking to add a job

That is a poor method. Sometimes cert requests fail due to temporary comms issues or Let's Encrypt outages or system stress.

So, doing it once every 70 days only gives you one chance to get a cert.

Further, the time 0 0 is not recommended as the time due to many other using that same time and causing unusual Let's Encrypt demand and possible failures.

You should re-run your long `certbot certonly ...` command once more using the deploy-hook I described. Then setup a cron job for the `certbot renew` command.

Please follow the instructions in the Certbot docs to use a random start time and run it at least once per day.

[https://eff-certbot.readthedocs.io/en/latest/using.html#setting-up-automated-renewal](https://eff-certbot.readthedocs.io/en/latest/using.html#setting-up-automated-renewal)

See this FAQ on random times for why this is important:

> **[FAQ - Let's Encrypt](https://letsencrypt.org/docs/faq/#why-should-my-let-s-encrypt-acme-client-run-at-a-random-time)**
>
> This FAQ is divided into the following sections:
> General Questions Technical Questions General Questions What services does Let’s Encrypt offer? Let’s Encrypt is a global Certificate Authority (CA). We let people and organizations...

---

<div class="post-metadata">

**Author:** ![milan.m](https://avatars.discourse-cdn.com/v4/letter/m/4491bb/32.png) [@milan.m](https://community.letsencrypt.org/u/milan.m)\
**Post date:** [October 31, 2023, 3:18pm UTC](https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561/7 "2023-10-31T15:18:42Z")

</div>

Okay, nice and thanks. Very good describe 🙂 Thanks you a lot

---

<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:** [November 30, 2023, 3:19pm UTC](https://community.letsencrypt.org/t/certbot-renew-dns53-domains/207561/8 "2023-11-30T15:19:24Z")

</div>

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