https://www.stavros.io/posts/how-to-configure-wireguard/
It takes hours to set up if you don't know how (and the docs aren't amazing), but it should take you ten minutes using my article.
This comes out in, for example, the "Accessing your home LAN" part of your article. It has a bunch of iptables magic that I understand, but presumably shouldn't have to in order to use WireGuard. Actually, the device that makes the most sense to use as a WireGuard server is my router, which is based on BSD; so presumably I'd need modify your commands to get this working on my OS! With OpenVPN, on the other hand, I can literally install a package for my firewall (OPNsense) and it's all done for me with a few clicks. That's what I mean by robustness: I'm capable of getting OpenVPN working on just about any computer, including my GUI based BSD router. WireGuard just doesn't have that yet.
I did, however, make it harder for myself by setting it up on a Unifi gateway. Where every push of an invalid config would put the gateway in a boot loop, bricking my internet connection for a few minutes.
For the interested: https://github.com/Lochnair/vyatta-wireguard
You might be interested in https://github.com/FossoresLP/vyatta-wireguard (no associaton, just a repo that I've found has the newer releases).
There seems to be a installer script (https://github.com/mafredri/vyatta-wireguard-installer) that will persist the deb between updates. This issue https://github.com/mafredri/vyatta-wireguard-installer/issue... will switch it to the port you suggest.
Perhaps I'll set that up. Given recent global events I've got some time, but not much need for a remote access solution right now!
For what it's worth this did seem easy to follow, I just know that when I tried to follow a guide similar to this one a while back I couldn't get it to work for a windows client.
I used StavrosK's guide (thank you!) to put together two scripts a while back, one for generating a new server config file, and one to generate a new client config, outputting the config to a file as well as to a QR code on stdout. You can copy the client.conf file over to the Windows machine and import the configuration via the "Import tunnel(s) from file..." option in the Wireguard client, or scan the QR code output from the mobile device clients via "Create from QR code".
Here's my script for generating a client cert: https://cdn.seedno.de/txt/wireguard-certgen. It assumes Wireguard is already configured on the server on interface wg0, and is using the default port of 51820/UDP, though both are configurable via variables. For reference, the accompanying setup script is https://cdn.seedno.de/txt/wireguard-setup. Both scripts require a bit of customization to match your environment (you may want to be particularly careful with the iptables firewall PostUp/PostDown commands), but hopefully they can serve as a starting point to figure out any issues you encountered last time you tried.
[0]: https://www.henrychang.ca/how-to-setup-wireguard-vpn-server-...
It always sends me down a rabbit hole of watching and listening to recordings of people shouting perkele. I always trying to think of a similar word in US English but never can think of anything.
So I looked up the meaning and went on a long ride on the train of distraction.
At first I honestly thought it was some state actor level prank because of how everyone insisted it was impossible to translate.
Most of the sites being sketchy top5 looking sites really played into my suspicion. Or lots of good beer.
Edit: fixed something.