[GH-ISSUE #238] Remove certbot random delay for manual renew #210

New issue

Closed

opened 2026-02-26 06:31:31 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:31:31 +03:00

Owner

Originally created by @sarbian on GitHub (Nov 12, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/238

When "Renew Now" is used the certificate can take a few minutes to be issued. The cert bot log has a line with "INFO:certbot.renewal:Non-interactive renewal: random delay of xxx seconds"
This can be frustrating since the UI display a timeout error and there is not way of know what is going on without looking in the log. The cert is actually issued after the random delay but it seems nginx is not reloaded and you need to enable/disable the site.

Certbot has a --no-random-sleep-on-renew option to disable that random delay and it should be used at least for renew from the interface.

Originally created by @sarbian on GitHub (Nov 12, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/238 When "Renew Now" is used the certificate can take a few minutes to be issued. The cert bot log has a line with "INFO:certbot.renewal:Non-interactive renewal: random delay of xxx seconds" This can be frustrating since the UI display a timeout error and there is not way of know what is going on without looking in the log. The cert is actually issued after the random delay but it seems nginx is not reloaded and you need to enable/disable the site. Certbot has a --no-random-sleep-on-renew option to disable that random delay and it should be used at least for renew from the interface.

kerem

2026-02-26 06:31:31 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:31:32 +03:00

Author

Owner

@jc21 commented on GitHub (Nov 13, 2019):

I didn't even know this was a problem. All my cert renewals have been immediate - but I guess it might have something to do with the dns verification, which I don't use yet.

@jc21 commented on GitHub (Nov 13, 2019): I didn't even know this was a problem. All my cert renewals have been immediate - but I guess it might have something to do with the dns verification, which I don't use yet.

kerem commented

2026-02-26 06:31:32 +03:00

Author

Owner

@joshbenner commented on GitHub (Jun 20, 2020):

Certbot will randomly wait on renewals when running in non-interactive mode. This is intended to avoid a massive rush of crons assaulting Let's Encrypt's servers all at the same time. This is appropriate when running scheduled renewals, but when running manually, specifying --no-random-sleep-on-renew is appropriate.

@joshbenner commented on GitHub (Jun 20, 2020): Certbot will randomly wait on renewals when running in non-interactive mode. This is intended to avoid a massive rush of crons assaulting Let's Encrypt's servers all at the same time. This is appropriate when running scheduled renewals, but when running manually, specifying `--no-random-sleep-on-renew` is appropriate.

kerem referenced this issue

2026-02-26 07:33:29 +03:00

[GH-ISSUE #2881] Temp workaround (that works for me!) for SSL certificate renewal bug #1972

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#210

No description provided.

Rows
Columns