Closed brandonros closed 9 months ago
Thanks for the suggestion! As a workaround, you can set the Persistent Keepalive in the server config. But it will apply globally to all clients. It should be moved to a per-client config option.
am I right to say that if you said it manually in the config file for the clients that it stands to be overwritten the next time any change is made via the GUI?
Yes you are right. If you press the Save button in either the Server or Client config, it will rewrite the WireGuard files according to what it thinks they're supposed to be.
Hey @brandonros, this feature should be added in the latest release, v2.0.11. Feel free to check it out and let me know if this works for you.
@micahmo thank you for all of the hard work you do for the community. will test and report back if there are any issues. highly appreciate it.
@micahmo hey, sorry to bother you. i'm 99% sure on latest release this doesn't work as expected 100%. in clients_wg
folder the [Peer]
is missing PersistentKeepalive = 25
for example and it gets overridden everytime a change is made in the UI
If I had to guess it was getting dropped there
https://unix.stackexchange.com/questions/714145/wireguard-not-able-to-connect-after-a-few-minutes