A basic config to set up a VPN that only adds access to services on the VPN itself is very short and simple, both for WireGuard server and for WireGuard clients.
You can run the WireGuard server from your home computer. For example on your NAS machine itself or some other machine you have at home. And open the port for WireGuard to the outside.
Also some routers can run WireGuard server on the router. For example Mikrotik routers have WireGuard server built in and ready to configure [0]. Routers running OpenWrt can too [1].
Or you can rent a small VPS and use that as your WireGuard server.
And then, either which where you run the WireGuard server, run the WireGuard client on your laptops, iOS and Android devices, and connect client apps using VPN internal IP addresses. And your NAS etc too, if the WireGuard server isn’t running on the NAS machine itself.
It really is quite quick to set up with server and all clients across devices.
The only real hurdle is that on iOS you have to turn the VPN back on manually after reboot and which is sometimes easily forgotten if you only use your self hosted services occasionally. But you quickly realize oh right I have to open the WireGuard app and turn on the VPN again whenever you try to use one of your self hosted services and the client isn’t connecting.
[0]: https://manual.mikrotik.com/docs/virtual-private-networks/wi...
[1]: https://openwrt.org/docs/guide-user/services/vpn/wireguard/b...
Generate the config, one per client, setup the client to only route specific RFC1918 networks and disable on well known wifi networks, and that's it. It literally works for years without any maintenance.
Tailscale is easier (presumably), but also puts a corporate entity between you and your data.
I don't work with computers professionally, at all. It still only took me about 2 hours to get the VPS, get Debian going on it, set up headscale, and connect to it from home. Do I still use corporate Tailscale? Yes, it has some features that aren't beautifully supported on headscale, and so for the moment I'm fine with that. But I do have my backup plan in place if I need it.
I have a headscale instance, on one of those $1/mo VPSes, and I don't intend to use it unless I have to. But if I have to, it's there.
You trust yourself with a VPS and correctly configuring a beast such a Debian?
I don't mean to be harsh but even as a professional developer I'm frequently humbled by our grumpy sysadmins on (to me) arcane stuff I didn't knew existed.
They are prime targets and have large attack surface. Even bigger companies are frequently compromised. It's a matter of time before it becomes publicly known.
mTLS is a better option for distributed systems (service to service mesh networks for attestation of workload identities) instead of for human users.
Do I turn on the VPN when I take a picture and turn it off when finished? Every time?
What if I need multiple VPN's? Living in a country that has a bad geoip reputation, it's already a struggle of switching on and off for individual websites to work.
https://github.com/alangrainger/immich-public-proxy/blob/mai...
I have one on-demand VPN with a list of internal IPs to route.
Now if you're going to use mTLS as the basis for mature authn/authz, that's a different story. But I never see anyone do that.
mTLS prevents connecting to the application without valid cert.
Sure the reverse proxy handling the mtls can be exploited, but so can any VPN server as well.
If I told you not to use a power drill as a hammer, you wouldn't claim I'm saying the hammer is at fault for being a bad power drill.
I just take issue (maybe pedantically so) calling it a bad tool and blanket statements that no one uses it for just authn but for authz also. It’s not used for authz. The absence of authz shouldn’t be blamed on mTLS.
Unfortunately, Synology apps don't support it.