Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Remove certbot random delay for manual renew #238
Comments
|
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. |
|
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 |
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.