-
Notifications
You must be signed in to change notification settings - Fork 5
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
Live-reloading config via Admin API fails due to the "one work_dir
per HTTP server" rule
#17
Comments
Hm interesting. I will have a look at it on Monday. Might be a timing issue |
A first code analysis did not reveal any issue. In theorie the cleanup should be called before another provision. I will try to debug this in the next days. How many servers did you have configured ? Only 1? |
How many servers did you have configured ? Only 1?
Yes, that's only one server. I can try making a minimal config for
reproduction.
|
yeah a minimal config could help. Currently i try to reproduce it and i already got a problem related to opening ports during reloading: Not related to revocation in general. I wonder if the provision/cleanup of modules in caddy is broken. Which operating system are you on? |
Should be fixed. I would like to do some more extensive testing before merging it to master, because it was quite a big change needed. Maybe you can try to build with the feature branch? https://github.com/Gr33nbl00d/caddy-revocation-validator/tree/fb-codecleanup |
Repro for Caddy v2.8.4 and this module v1.0.5:
The text was updated successfully, but these errors were encountered: