Open StuartHaire opened 6 months ago
I have the same problem
Simply change the volume to - './config:/etc/wireguard/wg_confs
in your wireguard-ui
service, so that the config is saved to the new _wgconfs directory.
You may need to delete any existing empty wg0.conf from the bound volume, then restart the container.
Simply change the volume to
- './config:/etc/wireguard/wg_confs
in yourwireguard-ui
service, so that the config is saved to the new _wgconfs directory. You may need to delete any existing empty wg0.conf from the bound volume, then restart the container.
Thank you for this! If anyone else is not able to get the UI working on a fresh install, this is your issue.
Hi, the following is my docker-compose and it works fine with the wireguard image "wireguard:v1.0.20210914-ls7" but when I use anything newer than this or the latest tag the UI won't load.
There was a breaking change after this version which states the following:
_"Potentially Breaking Change: Support for multiple interfaces added. Wireguard confs moved to /config/wgconfs/. Any file with a .conf extension in that folder will be treated as a live tunnel config and will be attempted to start. If any of the tunnels fail, all tunnels will be stopped. Tunnels are started in alphabetical order. Managed server conf will continue to be hardcoded to wg0.conf."
I think the issue is that wireguard now uses this new "wg_confs" folder whereas wireguard-ui doesn't account for this and is still looking the wg0.conf file within the config folder and not the wg_confs folder?
I've tried several things but with no luck. Any help or update around this would be great!