Display MoreHi, using personal files you have the possibility to choose the path where to keep your personal .conf files safe, you simply have to run the files that are populated in the plugin list.
You do not need to edit the wg0.conf file in /etc/wireguard, that file is overwritten every time a new server is started.
Thank you madhouse.
Nevertheless there is something I still do not fully understand.I have actually been trying to put the right things in configuration file in my own directory, as suggested.
But then, as far as I understand, the parameters are read from there and translated (especially routing and AllowedIPs) in a way I cannot control in the /etc/wireguard/wg0.conf file. Which is the one that wireguard eventually uses and is therefore the one that counts in the end.
And that does not fully suit my needs.
Which are a bit different from the majority of users here, since I am not using in this circumstances the VPN to cross geofencing and specifically I do not need (and I do not want) to route any general Internet traffic through the VPN.
Inserting bazillions of exceptions is not a very elegant solution (and nevertheless as of now even a few test domains do not work for some reason).
I fully understand why you make it this way, in order to make the configuration task easy even for inexperienced users, but I am hitting a wall here because of this.
Just to describe my "frustration" I had even tried to disable root writing privilege to the wg0.conf file, but of course this brings to nothing, since there must be a wise check about writing errors and plugin initialisation stops!
Actually, at the moment I am reaching 90% of what I need, which is a lot, especially when compared to the 0% level I was only few days ago when I had not yet got to know about your plugin.
But I would be very happy to be able to reach the 100% finish line!
Thank you!
Hi, send me a file of yours modifying/deleting only the private key.
