-
Notifications
You must be signed in to change notification settings - Fork 130
Read in existing server config #7
Comments
@tozjerimiah normal server config requires a private key of server interface and public keys of peers. In this wg-ui config.json, you have to specify both private and public keys of peers. To create config.json from an existing server config, you'll need an additional source where private keys of peers will be stored. |
As web-ui doesn't have any knowledge about the private-keys of these peers, we could make them read-only for now. Maybe we could enhance this feature to fill in the private key at a later point of time, and therefore be able to generate a config as well but I would suggest to postpone such functionality. |
Hello, |
...or at least any way to replicate the current configuration using the command line options.. |
Hi all, i already have wireguard working. I could not find how to use the current configuration with wg-ui. Any hint in how to have it productive, without having to start a new sitewide configuration? Best regards, |
I second this, it would be nice if it could read the current configs of WG, eg. already existent /etc/wireguard/wg0.conf, or if someone has a service set up, like systemctl status wg-quick@wg0 |
Quite confused, there is no any document or tutorial to show how to setup with Wireguard wg0 configuration? or did I missed any thing? |
Kindly should i copy the wireguard config from (sudo nano /etc/wireguard/wg0.conf) to /data/config.json? |
It would be a fantastic feature to be able to read in a normal server conf file and have it create it's config.json from it.
The text was updated successfully, but these errors were encountered: