Is Tailscale free? Free tier limits explained
Tailscale's Personal plan is free for noncommercial use, with six users and unlimited user devices. See tagged resource limits and when Headscale wins.
Filtering by topic #vpn · clear
Tailscale's Personal plan is free for noncommercial use, with six users and unlimited user devices. See tagged resource limits and when Headscale wins.
Run your own Tailscale control server on a VPS. Install headscale from the official .deb, set server_url and restart it, then join your first node.
Tailscale is WireGuard plus a control plane. What that coordination server buys you, what it costs you, and which of the three belongs on your VPS.
Tailscale is a WireGuard mesh VPN: a coordination server hands out keys and ACLs, NAT traversal links devices directly, and DERP relays step in when it fails.
Put a container behind a Gluetun sidecar and its ports vanish. Here is why the shared network namespace does that, and the compose file that works.
Tailscale bills per user, not per device: free up to 6 home users, then $8 or $18 per user a month. See what a five person team pays and when Headscale wins.
Use your TP-Link router's VPN Client with a WireGuard server on your own VPS. Spot CGNAT first, then build an IPv4 only config the router will import.
WireGuard wins for almost every self hoster on speed, config size and audit surface. Here is the evidence, and the four cases where OpenVPN still wins.
Your WireGuard handshake works but no host on the home LAN answers. Four settings decide whether a packet reaches 192.168.20.10 and finds its way back.
Slow WireGuard is usually an MTU problem. Find your path MTU by bisection, clamp TCP MSS, check steal time, and measure the path before blaming the tunnel.
Downloads work but nothing ever connects in. Set up gluetun port forwarding, push the new port to your torrent client on every reconnect, and verify it.
WireGuard is free, open source software and your keys cost nothing. What you pay for is the server at the far end of the tunnel. Here is who runs it and why.
Reach across two tailnets with node sharing, user switching, a two-daemon VPS bridge or one tailnet with ACLs. See what each option exposes to the other side.
Run WireGuard behind the wg-easy web UI with Docker Compose: the ports, NET_ADMIN, the sysctls that matter, and QR code onboarding for phones.
A container behind Gluetun has no interfaces of its own. Publish its ports on Gluetun, and open only the subnets it must reach outside the tunnel.
Tailscale never holds the keys that encrypt your traffic. Its safety hinges on what a compromised coordination server or stolen identity account can do.
Turn your VPS into a Tailscale exit node: install, advertise, enable IP forwarding, approve the route in the admin console, then fix DNS and IPv6.
AllowedIPs is the routing table and the access list at once. Learn cryptokey routing, the Noise handshake and rotation, and every wg0.conf reads clearly.
Your VPN is blocked because its handshake is recognisable. What Outline, obfs4 and WebTunnel change about the bytes, and what they cannot hide.
Eight jobs people run over a tailnet: reach home, borrow a VPS exit IP, share or publish one service, and SSH with no open ports. One command each.
Gluetun installs a real firewall kill switch inside its own network namespace. What your containers see when the tunnel dies, and how to prove it holds.
A VPS is a computer you rent. A VPN is an encrypted tunnel for your traffic. What each one does, what each costs, and how one can host the other.
Run the Outline VPN server, not the wiki app, on your own VPS. Install, access keys, the management API port, and what Shadowsocks does not hide.
Tailscale is a WireGuard VPN between your own devices. Websites see your real IP until you add an exit node, and your ISP always does. What each setup hides.
Tor and a VPN answer different questions. See exactly who learns what at every hop, and why a VPS rented in your name is not an anonymity tool.
Tailscale serve puts HTTPS on a tailnet-only URL. Funnel opens that same port to the public internet. Which to use, and the policy gate that blocks funnel.
Set up WireGuard on your own Linux VPS: key generation, wg0.conf, IP forwarding, NAT, AllowedIPs semantics, DNS, and the handshake failures that bite.
The vendor Compose example leaves your app on a public host port. Use a Tailscale sidecar so the container has no published port, only a tailnet name.
Your WireGuard tunnel is up but names do not resolve, or the queries leak to the local router. Find which of the three DNS failures you have, and fix it.
Add a new WireGuard client with wg syncconf and wg-quick strip so connected peers stay up, plus wg set, wg-quick save, AllowedIPs collisions and PostUp rules.
Tailnet lock stops a compromised Tailscale coordination server from adding a node to your tailnet. It also gives you ten secrets you must not lose.