Wireguard-Confs.zip ends up in a sub-folder called Wireguard-Data - I think you maybe need to cd into that before copying everything into /etc/wireguard…?
Running as root might pose security risks - you might want to see if you can make everything work with sudo at the front of each line instead.
It seems like rather more of this could be put into a .sh file for added automation? If you assume that the user will want to extract all possible .conf files (and there’s no obvious reason not to) could you batch the whole process up into a single script and have the user download that?
I can’t see any good reason to have more than one Wireguard connection running simultaneously; so it ought to be possible to have a command along the lines of wg-quick down which shuts the current connection down without you having to specify which city it was. (I don’t know if this is under your control!)
I suggest you reformat the stuff you need to type as “pre-formatted text” instead of bulleted text
so it looks
and also try and make every piece of text something that can be copied and pasted verbatim (so remove any “or” instructions).
But other than that, this does seem to be working on my Vero 4K+. Nice!
Tom I don’t have a problem connecting to the server and getting a IP with autostart, just the DNS is not getting picked up. I did a fresh install of Dietpi to experiment with, only installed wireguard and resolvconf and everything worked perfect. The only thing I did differently was enter sudo systemctl enable wg-quick@Toronto and an immediate reboot after.
I am not sure what a service file is but if you ran wiregen (as root) there would be no need to examine the conf files. As a matter of fate I tared the wireguard dir (as root) and untared it into Dietpi /etc (as root) and no problem, everything worked. What drove me nuts was when someone suggested not to do every step as root and that screwed up the permissions and ownerships and nothing connected.
Hope this helps