-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
Wireguard UI doesnt restart Wireguard Service When Applying Config #478
Comments
+1 |
Same here |
Same on FreeBSD. To restart the service it should run |
Same as you, to apply the config I need to restart the wireguard container and then the wireguard-ui. Easier than |
Hi guys. To automatically restart the service, you need to: WGUI_MANAGE_RESTART=true |
I have issues with the WGUI_MANAGE_RESTART=true. I believe it might be related to an issue with iptables that I can see in my docker logs: To bring wireguard up again I need to run it manually with wg-quick start wg0 Any idea if I am doing something wrong? |
I am having the same issue, running within docker on a Synololgy NAS. When I apply the config, the changes are applied to wg0.conf, the wg0 interface is stopped, but it does not start after (but works fine when I manually start from the command line via wg-quick). Environment variables are as follows: environment: |
I'm having the same problem on my Synology. #520 did not solve the issuse for me. Did anyone else already try version 0.6.0 and can confirm that the problem still persits? |
I've checked the log file of the WireGuard-UI container. There seems to be an issue with iptables. The error message is: |
but I don't use docker!!!! |
Yes, thanks. WGUI_MANAGE_RESTART is set to true, but it isn't working as documented. |
Replaced this and everything started working |
Wireguard UI doesnt restart Wireguard Service When Applying Config. I have to manually restart from console everytime after clicking apply config for it to take effect.
Running Ubuntu 23
The text was updated successfully, but these errors were encountered: