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

Clients not able to connect after reboot until configuration manually re-applied. #652

Open
Tech-Geek97 opened this issue Dec 11, 2024 · 1 comment

Comments

@Tech-Geek97
Copy link

Tech-Geek97 commented Dec 11, 2024

wireguard-ui does not seem to apply the list of clients after a restart. The only solution I have found is to make a change to the client configuration and apply the config from the UI. There are no errors that I can find in the logs of either docker or docker-ui and this problem occurs if I restart the docker containers or the entire server.

I found issue #531 that also requires a configuration edit and apply to resolve, but I am not seeing the errors in the log and neither the symlink solution nor the configuration change have had any effect.

@GudBoiNero
Copy link

GudBoiNero commented Dec 12, 2024

Quite literally running into this exact problem right now. I had to restart my computer remotely today (which i was connected to through the vpn) only to realize after waiting twenty minutes for it to restart itself that my client conf was no longer valid because it was reset for some reason.

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

2 participants