-
Notifications
You must be signed in to change notification settings - Fork 171
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
Caddy config not reloaded #605
Comments
You need to run If that's not the problem, then please share more about your setup and the steps you take. Can't help without more information, we're forced to make assumptions. |
Sorry, yes I was a vague about my setup. I actually do recreate the containers after changing the labels. I just can't see any logs/sign that the proxy even notices the change in the labels.
An example
|
Here is my redacted caddy-config, which is generated upon container restart:
|
@francislavoie Do you have any idea why it is not working like this? I have tried rebuilding, removing parts of config, etc... still no luck. |
Like I said, you need to recreate the containers to have label changes take effect. You can't just edit your docker-compose.yml and expect it to have an effect. |
And as I said before, I recreate the containers all the time.
|
Most of the time, the config is not reloaded automatically, I need to restart the caddy-docker-proxy container to reload the config.
For example, I had an already added domain, I added basicauth to that domain via
docker-compose
labels. The change was not visible, until I restarted the proxy container.Where should I look, what is causing this issue?
The text was updated successfully, but these errors were encountered: