My point is that since the VPN uses a different subnet, it's fine to keep it connected even at home. It'll only use the VPN if you access the server's VPN IP, not its regular IP.
In any case, Tailscale and Wireguard are peer-to-peer, so the connection over the VPN is still directly to the server and there's no real disadvantage of using the VPN IP on your local network.
Yeah, this. Plus if you leave it connected, you can use the VPN IPs while at home instead of having to use a different IP when at home vs when out (or deal with split horizon DNS)
Headscale is a replacement for the coordination servers, which are only used to distribute configs and help nodes find each other. It won't change client-side behaviour.
I did this and it still seems to randomly disconnect.
If you have a separate subnet for it, then why do you only want it to be connected when you're not on home wifi? You can just leave it connected all the time since it won't interfere with accessing anything outside that subnet.
One of the main benefits of Wireguard (and Tailscale) is that it's peer-to-peer rather than client-server. You can use the VPN IPs at home too, and it'll add barely any overhead.
(leaving it connected is assuming you're not routing all your traffic through one of the peers)
conditional Auto-Connect. If not on home wifi, connect to the tunnel.
You don't need this with Tailscale since it uses a separate IP range for the tunnel.
Edit: Tailscale (and Wireguard) are peer-to-peer rather than client-server, so there's no harm leaving it connected all the time, and hitting the VPN IPs while at home will just go over your local network.
The one thing you probably wouldn't do at home is use an exit node, unless you want all your traffic to go through another node on the Tailnet.
Yeah my wife and I are both on Android, and I haven't been able to figure out why it does that.
The Android client is open-source so maybe someone could figure it out. https://github.com/tailscale/tailscale-android
Is it just you that uses it, or do friends and family use it too?
The best way to secure it is to use a VPN like Tailscale, which avoids having to expose it to the public internet.
This is what I do for our security cameras. My wife installed Tailscale on her laptop and phone, created an account, and I added her to my Tailnet. I created a home screen icon for the Blue Iris web UI on her phone and mentioned to her, "if the cameras don't load, open Tailscale and make sure it's connected". Works great - she hasn't complained about anything at all.
If you use Tailscale for everything, there's no need to have a reverse proxy. If you use Unraid, version 7 added the ability to add individual Docker containers to the Tailnet, so each one can have a separate Tailscale IP and subdomain, and thus all of them can run on port 80.
That's interesting... It used to be a lot heavier.
Authelia is definitely the lightest in terms of RAM, but it's also the lightest in terms of features. As far as I can remember, they only added OIDC support fairly recently - previously it only supported proxying.
Nothing's as bad as trying to host and maintain a Ruby on Rails app :)
Docker has made a lot of it a non-issue though, since the apps are already preconfigured within the Docker image.
Oh yeah, there'll be some overhead if you're running Wireguard on a router. Hitting your router's public IP won't go out to the internet though - the router will recognize that it's its IP.
It's common to run Wireguard on every computer/phone/tablet/etc where possible rather than just on the router, since this takes advantage of its peer-to-peer nature. For home use, that's how it was originally designed to be used. Tailscale makes it a lot easier to configure it this way though - it's a bit of work for vanilla Wireguard. Tailscale does support "subnet routers" if you have any devices that you want to access over the VPN that can't run Tailscale.