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

reproxy doesn't update allowed FQDNs for SSL after it's startup #207

Open
Semior001 opened this issue Sep 19, 2024 · 0 comments
Open

reproxy doesn't update allowed FQDNs for SSL after it's startup #207

Semior001 opened this issue Sep 19, 2024 · 0 comments

Comments

@Semior001
Copy link

On startup, if FQDNs are not defined in the environment variables, reproxy loads the FQDNs from the discovered servers (see: https://github.com/umputun/reproxy/blob/master/app/proxy/proxy.go#L150-L153).

However, when the list of containers is updated or the configuration file is modified, reproxy does not automatically update its list of FQDNs. As a result, a restart of reproxy is required to reflect these changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant