MANKUD

> then try out nightly build please. https://github.com/rustdesk/rustdesk/releases/tag/nightly Hello the nightly build does not seem to be working on windows server 2016.  

oh ok so the nightly build is only for the latest version of windows due to limitations of Github CI and the future stable build should support older versions too.

@braginini That would be great Thank You :)

Hello, What I mean is imagine for instance we have a machine behind NAT which we want to access from a different network (WAN) but we cannot open any ports...

I understand but it would be a great feature if was possible via the wireguard-ui just a suggestion.

@ngoduykhanh I think wireguard-ui is already doing a fantastic job of managing wireguard config maybe I thought it can do even more in future.

@ngoduykhanh Maybe this will help. https://github.com/pritunl/pritunl/commit/023ee6509e62e7d64a9cd4e008e19972ef33ba67 https://github.com/pritunl/pritunl/commit/c3ff9e2fed314a009dd3bf7875a35abe89f1eadf https://github.com/pritunl/pritunl/commit/01ff772b23f68f49e30dd68d90fbf874c2a6ab72 Another reference to a very good video. https://www.youtube.com/watch?v=9tDeh9mutmI

Yes, this would be really nice rather than manually configuring for each client.

> It is because we [restart the interface](https://github.com/ngoduykhanh/wireguard-ui#auto-restart-wireguard-daemon) every time apply the config. I think can solve this problem by using [addconf](https://manpages.debian.org/unstable/wireguard-tools/wg.8.en.html#addconf) and [syncconf](https://manpages.debian.org/unstable/wireguard-tools/wg.8.en.html#syncconf) I think if you implement this...

> > It's in db/server/users.json > > where exactly /op/wgui/db/server