Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let's Encrypt Server Load for @daily crons #289

Closed
jamessqr opened this issue Jan 5, 2023 · 2 comments · Fixed by #326
Closed

Let's Encrypt Server Load for @daily crons #289

jamessqr opened this issue Jan 5, 2023 · 2 comments · Fixed by #326

Comments

@jamessqr
Copy link

jamessqr commented Jan 5, 2023

Description of problem

Recently Let's Encrypt has noted increased server loads at 00:00:00 https://community.letsencrypt.org/t/new-service-busy-responses-beginning-during-high-load/184174/2

We discovered a Dokku instance has been failing letsencrypt renewal for approximately a month using the dokku-letsencrypt plugin. Reviewing the cron log we were receiving the 503 errors and various outage type responses from Letsencrypt. We manually changed the cron task to a different time of the day and things are working.

I suggest an enhancement to dokku-letencrypt to allow a custom cron expression when the jobs are added so that everyone using the plugin isn't ddos'ing their servers

@roelvanduijnhoven
Copy link

I've observed the same thing.

To make the change manually you can do the following. Run crontab -e -u dokku to open the relevant cronfile in your default configured IDE. And apply a patch like below.

PATH=/usr/local/bin:/usr/bin:/bin
SHELL=/bin/bash

-@daily dokku letsencrypt:auto-renew &>> /var/log/dokku/letsencrypt.log
+30 3 * * * dokku letsencrypt:auto-renew &>> /var/log/dokku/letsencrypt.log

josegonzalez added a commit that referenced this issue Feb 25, 2024
While ideally this is a custom time, this will help alleviate issues where the letsencrypt certificate may not renew due to load on the letsencrypt servers.

Closes #289.
@josegonzalez
Copy link
Member

I've opted to just change our default time for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants