A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Im mostly using a self hosted headscale on a remote vps and then tailscale on my clients.
Having the coordination server outside of my network helps quite a bit and things still communicate over the local lan when possible.
For just wireguard itself, I do have a few site to site connections set up at the router level (opnsense).
OPNsense
This is the way.
This is the way.
If router works, you got access to your lab. If it doesn't, well redundancy was not a requirement / too much hassle to set up.
I run a wireguard container on my old desktop server and wgeasy in a pi2 as backup.
One instance runs on the router (Unifi USG) and the other on a Pi3 (as a backup) using PiVPN.
Usually, if I need to set it up, I’ll use PiVPN and either a Pi or Debian/Ubuntu host.
If your router is down how do you get to your pi backup?
My concern is that the WireGuard portion of the router fails for some reason but still routes.
It also allows me to choose another port
What are you wanting to use Wireguard for?
That's the fun part. I'm creating a mesh where multiple things are server and client.
K8s, mikrotik, home assistant, frigate, pangolin, etc.
I don't get the mesh if everything is behind your router or firewall what is the point.
Ah yes, those things are not all in 1 "home network". I have multiple vlan's, multiple ISP's and multiple locations. Including some rented VM's.
On my router
On my opnsense router
I have a vps (hetzner dedicated server auction) as well as my home servers. The vps has a fixed IP so ive setup wireguard endpoints to all point to it with forwarding on so can access every device indirectly through the vps. It allows them to work across DDNS or remotely.
I used this guide (https://www.digitalocean.com/community/tutorials/how-to-set-up-wireguard-on-ubuntu-20-04). Tried different tools gui's and other methods but always came back to this to work the best
On my (OpenWrt) router, configured using the OpenWrt interface
On my router, my FritzBox came with WG support built in.
Always in the router if it supports it. If it does not support wireguard I would rather (if you are able and allowed to) replace the router instead of using something else.
Can you elaborate on why?
Maybe easier to setup because routers that support vpns come with nice-ish web uis.
That said, if you have a server (pc, pi, etc), setting up wireguard with wg-easy is mostly painless (comes with a nice web ui), so there is no reason to replace your router in this case!
Instead of replacing a router, I'd prefer buying a pi anyways.
Unless you want to route all outbound traffic through a vpn with zero config on devices, I can't see why you'd replace a router.
Final note: most people prefer hosting a vpn on a server, even if their router supports it as far as I'm aware at least (edit: this might be erong judging from the rest of the comments saying they use their router).
It's my outside device it allows things into my network might as well terminate the VPN there. I mean if my router is down I'm not getting to the VPN endpoint inside my network.
For me a similar tasks should be handled by the same device. Network routing and VPN are similar things for me, therefor they are handled by the router.
It also handles VPN connections to other remote locations. So again same things in the same device.
Another benefit (which you can also have on the Server with some additional effort): the router boots up without interaction after a power outage. The Server does not. Them I can connect and unlock (LUKS password) the servers.
I have a Raspberry Pi that runs pihole and Wireguard exclusively. My home server is a Kubernetes cluster running on an old desktop PC and 2 Intel NUCs.
The reason for the separate Pi was essentially because I only had the desktop PC initially, and for a while I had a faulty CPU, making the desktop PC crash or become unresponsive, so it helped a lot having DNS and VPN access separated from the instability.
One end is a local VPS with insanely good peering pretty much round the damn world, other end is my opnsense router. I actually pass a block of ipv6 through the vpn and my router hands it out to devices which is a nice little bonus
Who is your VPS provider, if you don't mind telling?
https://spartanhost.org/ owner is super chill will make custom spec deployments and they actually have a really nice management panels with nice easy custom iso support
Thanks!
I run the server on an old Pi. That's its only job.
I run one on my firewall, but it's IPv6 only because of CGNAT. The other one is running on a VPS in case I need IPv4 access. I just configured them manually.
Wireguard normally runs with higher than root privileges as part of the kernel, outside of any container namespaces. If you're running some sort of Wireguard administration service you might be able to restrict its capabilities, but that isn't Wireguard. Most of my devices are running Wireguard managed by tailscaled running as root, and some are running additional, fixed Wireguard tunnels without a persistent management service.
Mine runs on my router which is running openwrt
Runs in an extra locked-down container on one of my servers.
Home 1's Routers, Home 2's Router, public IPv4/v6 VPS. All as the native arch package.
The routers are running Arch? What hardware are they?
I'm running pfSense as edge firewalls with a Fritzbox router as a bridge - no issues there, but would be interesting to replace that part too, if possible.
Old small desktop towers. Powerful, very open (so I can run my NS infra and WG server and bridge on there, and easily have them redundant), and very extendable (need a 10G NIC or SFP+? Plug in a PCIe card!), and easily replaceable. I now have some old Cisco APs, which will be for my 2nd Home, so I can use my FritzBox as only a modem. In my 1st Home, I'll hopefully soon actually have fibre in addition to using my dads FritzBox as uplink. And I could add a Mobile Modem too. There, I don't need a wireless network, as in contrast to my 2nd Home, that infra is only for servers, to which I can just connect from my dads network/FB.
Vps with public ipv4 v6. Avoids all the dyndns mess.
wg-easy on a nuc
On the home server on the host. I couldn't figure out how to make it work in a container and still have ssh access to the host, which was my goal...
Started with it on a server but moved it to my Openwrt router. If the router's up the tunnel's up.
Why would you run a WG Client and WG Server on the same host? Am I reading that second mark wrong?
You are, second point means running WG on say, a proxmox root, and using it to access the containers.
Uhhhh...that is...not how you do that. Especially if you're describing routing out from a container to an edge device and back into your host machine instead of using bridged network or another virtual router on the host.
Like if you absolutely had to have a segmented network between hosts a la datacenter/cloud, you'd still create a virtual fabric or SDLAN/WAN to connect them, and that's like going WAY out of your way.
Wireguard for this purpose makes even less sense.
There's no such thing as a client or server with Wireguard. All systems with Wireguard installed are "nodes". Wireguard is peer-to-peer, not client-server.
You can configure nftables rules to route through a particular node, but that doesn't really make it a server. You could configure all nodes to allow routing traffic through them if you wanted to.
If you run Wireguard on every device, you can configure a mesh VPN, where every device can directly reach any other device, without needing to route through an intermediary node. This is essentially what Tailscale does.
Uhhh, nooooo. Why are all these new kids all in these threads saying this crazy uninformed stuff lately? 🤣
https://www.wireguard.com/protocol/ https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/configuring_and_managing_networking/setting-up-a-wireguard-vpn
And, in fact, for those of us that have been doing this a long time, anything with a control point or protocol always refers to said control point as the server in a PTP connection sense.
In this case, a centralized VPN routing node that connects like a Hub and Spoke is the server. Everything else is a client of that server because they can't independently do much else in this configuration.
Both of those documents agree with me? RedHat are just using the terms "client" and "server" to make it easier for people to understand, but they explicitly say that all hosts are "peers".
Note that all hosts that participate in a WireGuard VPN are peers. This documentation uses the terms client to describe hosts that establish a connection and server to describe the host with the fixed hostname or IP address that the clients connect to and, optionally, route all traffic through this server.
--
Everything else is a client of that server because they can't independently do much else in this configuration.
All you need to do is add an extra peer to the WireGuard config on any one of the "clients", and it's no longer just a client, and can connect directly to that peer without using the "server".
They do no such thing.
The first link explains the protocol.
The second explains WHY one would refer to client and server with regards to Wireguard.
My point ties both together to explain why people would use client and server with regards to the protocol itself, and a common configuration where this would be necessary for clarification. Ties both of them together, and makes my point from my original comment, which also refers to OP's comment.
I'm not digging you, just illustrating a correction so you're not running around misinformed.
It wasn't clear where OP was trying to make a point, just that the same host would be running running Wireguard for some reason, which one would assume means virtualization of some sort, meaning the host machine is the primary hub/server.