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

webroot: renew propagation-seconds #9643

Open
mokraemer opened this issue Mar 30, 2023 · 4 comments · May be fixed by #9650
Open

webroot: renew propagation-seconds #9643

mokraemer opened this issue Mar 30, 2023 · 4 comments · May be fixed by #9650
Labels
area: webroot feature request has pr priority: unplanned Work that we believe should be done, but does not have a higher priority.

Comments

@mokraemer
Copy link

For renewal or initial setup it would be great, if there is a waiting or propagting time between getting the secret, placing it in docroot and retrieving it.

Sure this can be done via manual mode, but just adding a wait/propagation time would help a lot.

@alexzorin
Copy link
Collaborator

It would help to understand the use case. That would help us gather information about this feature request to evaluate how to prioritize it.

I have observed this issue specifically with Apache Tomcat, where there is a hot deploy delay and requires some cleverness to work around.

@alexzorin alexzorin added feature request area: webroot priority: unplanned Work that we believe should be done, but does not have a higher priority. labels Mar 30, 2023
@mokraemer
Copy link
Author

it depends on the underlying filesystem to move files. We use a filesystem which triggers rsync to synchronize to other hosts in the load-balancer environment. If one file is changed, it waits a small amount of time and then pushes all changes to other servers. For dns you already implemented a propagation-delay.

@osirisinferi osirisinferi linked a pull request Apr 1, 2023 that will close this issue
3 tasks
Copy link

github-actions bot commented Apr 1, 2024

We've made a lot of changes to Certbot since this issue was opened. If you still have this issue with an up-to-date version of Certbot, can you please add a comment letting us know? This helps us to better see what issues are still affecting our users. If there is no activity in the next 30 days, this issue will be automatically closed.

@mokraemer
Copy link
Author

I guess this issue is still open and a fix is already pushed, but needs to be merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: webroot feature request has pr priority: unplanned Work that we believe should be done, but does not have a higher priority.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants