# Tailscale Problems & Issues 2026 - Slow Relays, DNS & Exit Nodes

Source: https://www.tryorbye.com/products/tailscale
Last analyzed: 2026-11-16
Try or Bye score: 75/100

## Verdict: Try

Tailscale is worth trying for most users (score 75/100). Most reported issues: Why is Tailscale so slow? Connections stuck on DERP relay; Tailscale exit node has no internet; Tailscale MagicDNS not working or overwriting resolv.conf on Linux. Not a good fit for: Privacy VPN shoppers (hide IP, streaming); Users who must run another VPN at the same time. Users most often switch to Headscale, NetBird, ZeroTier.

## What it is

Tailscale is a mesh VPN built on WireGuard that links laptops, phones, servers, NAS boxes and cloud machines into a private network (a 'tailnet') without opening ports. It is popular with homelab users for remote access to home servers and with engineering teams as a zero-trust replacement for a traditional company VPN. Sign-in goes through an identity provider such as Google, Microsoft, GitHub or Apple, and access is controlled with a policy file of ACLs and grants.

## Common errors & fixes

### Tailscale Android Keeps Disconnecting

On Android, battery optimisation and VPN settings often stop Tailscale in the background. Set the app to unrestricted battery use, make Tailscale the always-on VPN, and test with 'Block connections without VPN' off.

1. **Set battery use to unrestricted** — Open Settings > Apps > Tailscale > Battery Choose Unrestricted Turn off adaptive battery restrictions for Tailscale if your phone has them
2. **Make Tailscale the always-on VPN** — Open Settings > Network & internet > VPN Tap the gear next to Tailscale and enable Always-on VPN
3. **Test without 'Block connections without VPN'** — In the same VPN settings, turn off Block connections without VPN If Tailscale is stuck, turn off the VPN, force-stop Tailscale and reopen it
4. **Try with MagicDNS off** — Some users fixed Android drops by disabling 'Use Tailscale DNS' in the app settings; re-enable if it doesn't help

Full guide: https://www.tryorbye.com/products/tailscale/issues/android-disconnecting

### How to Cancel Tailscale Subscription

An Owner, Admin or Billing admin cancels from the admin console Billing page: Your plan menu > Cancel subscription. The tailnet keeps paid features until the end of the billing period, then moves to the free Personal plan.

1. **Cancel a paid plan (move to Personal)** — Sign in to the admin console as Owner, Admin or Billing admin Open the Billing page In Your plan, open the menu and select Cancel subscription Review the features you'll lose and confirm The change takes effect at the end of the billing period; no prorated charge
2. **Reduce users first** — Personal allows at most 6 users and is for non-commercial use Delete or suspend extra users before cancelling; if Personal isn't offered, the tailnet is treated as commercial
3. **Downgrade to a cheaper paid plan** — On the Billing page select Switch plan Choose Downgrade on the target plan and confirm If a downgrade is already scheduled, cancel it from the Scheduled changes banner before cancelling the subscription
4. **Annual contracts and refunds** — Annual subscriptions are arranged through sales; contact Tailscale sales/support to change them Tailscale's docs don't describe refunds; changes apply at the end of the period

Full guide: https://www.tryorbye.com/products/tailscale/issues/cancel

### Tailscale Can't Connect to Other Device

If one tailnet device can't reach another, update both clients, confirm the device shows in 'tailscale status', test with 'tailscale ping', then check firewalls, ACLs and key expiry.

1. **Update and check status** — Update Tailscale on both devices Run 'tailscale status'; if the other device is missing, the policy file is likely hiding it
2. **Test the path** — Run 'tailscale ping <device>' (add --verbose) If tailscale ping works but your app doesn't, the problem is a firewall or the policy for that port
3. **Review access controls** — Open Access controls in the admin console Check the ACLs, grants and SSH sections allow the target IP and port Use the Preview rules tab to confirm what's allowed
4. **Check firewalls and identity** — Allow the service in the target device's local firewall Confirm both devices use the expected user or tag and that neither key has expired

Full guide: https://www.tryorbye.com/products/tailscale/issues/cant-reach-device

### Tailscale Exit Node Not Working

An exit node that connects but passes no traffic is usually missing IP forwarding, isn't approved or allowed to reach autogroup:internet, or sits on a router without NAT/forwarding rules. Enable forwarding, approve the node, and check the policy.

1. **Enable IP forwarding on Linux** — Run: echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf Run: echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf Apply with: sudo sysctl -p /etc/sysctl.d/99-tailscale.conf Advertise again with: sudo tailscale set --advertise-exit-node
2. **Approve the exit node** — Open the admin console Machines page Open the exit node's ... menu and select Edit route settings Enable 'Use as exit node' and save
3. **Allow internet access in the policy** — Open Access controls in the admin console Add a grant or ACL with destination autogroup:internet for the users who use the exit node
4. **Add NAT/forwarding rules on routers** — On OpenWrt or GL.iNet, add firewall forwarding between the tailscale interface and lan/wan Enable masquerading so LAN clients' traffic is NATed
5. **Allow LAN access if needed** — Run 'tailscale set --exit-node-allow-lan-access=true' or enable Exit Node LAN access in the client Only do this on networks you trust

Full guide: https://www.tryorbye.com/products/tailscale/issues/exit-node-not-working

### Tailscale iPhone Not Connecting (VPN On Demand)

On iPhone and iPad, VPN On Demand rules decide whether Tailscale may connect, and a bad rule or another VPN with On Demand can block or undo reconnects. Check the rules, turn off On Demand in other VPNs, update and force-quit the app.

1. **Check VPN On Demand rules** — Open Tailscale settings and review VPN On Demand rules for Wi-Fi and cellular Remove any 'Never' rule for networks where you want Tailscale, or turn On Demand off to test
2. **Turn off On Demand in other VPNs** — Only one VPN app can use On Demand; disable it in the other VPN app Reconnect Tailscale manually so iOS re-enables its On Demand
3. **Update and force-quit** — Update Tailscale from the App Store Swipe the app away, reopen it and reconnect

Full guide: https://www.tryorbye.com/products/tailscale/issues/iphone-not-connecting

### Tailscale Node Key Expired

User devices must re-authenticate when their node key expires; until they do, connections to and from them stop. For servers and NAS boxes, disable key expiry on the admin console Machines page.

1. **Disable key expiry for servers** — Open the admin console Machines page Open the device's ... menu at the far right Select Disable key expiry
2. **Re-authenticate the device** — On the device run 'tailscale up --force-reauth' and complete the login in the browser Or use 'Temporarily extend key' in the admin console to give the owner time
3. **Use tags for infrastructure** — Tag servers in the policy file; key expiry is disabled by default for tagged devices Generate a fresh auth key if the old one expired

Full guide: https://www.tryorbye.com/products/tailscale/issues/key-expired

### Tailscale MagicDNS Not Working

MagicDNS breaks most often on Linux, where Tailscale and NetworkManager or another resolver fight over /etc/resolv.conf. Use systemd-resolved, or run 'tailscale set --accept-dns=false' on hosts with their own DNS such as Pi-hole.

1. **Check DNS outside Tailscale first** — Disconnect Tailscale and test name resolution If it works without Tailscale, Tailscale's DNS settings are involved
2. **Use systemd-resolved on Linux** — Run 'resolvectl status' and check whether /etc/resolv.conf is a symlink to the systemd stub If using NetworkManager, set dns=systemd-resolved in its config Relink /etc/resolv.conf to /run/systemd/resolve/stub-resolv.conf and restart NetworkManager, systemd-resolved and tailscaled
3. **Stop Tailscale managing DNS on that host** — Run 'sudo tailscale set --accept-dns=false' MagicDNS at 100.100.100.100 still answers if you query it directly
4. **Check the tailnet DNS settings** — Open the DNS page in the admin console and verify nameservers and MagicDNS are enabled Make sure the policy allows devices to reach the configured nameservers

Full guide: https://www.tryorbye.com/products/tailscale/issues/magicdns-not-working

### Tailscale No Internet When Connected

If you lose internet as soon as Tailscale is on, check for an offline exit node, a CGNAT (100.64.0.0/10) address conflict, another VPN, or a DNS problem. Pinging 8.8.8.8 tells you whether it's routing or DNS.

1. **Separate DNS from routing** — Run 'ping 8.8.8.8' If ping works but websites don't load, it's a DNS problem (see the MagicDNS guide) If ping fails, continue with the steps below
2. **Turn off or fix the exit node** — In the Tailscale client, set exit node to None and retest If that fixes it, make sure the exit node is online and allowed to reach autogroup:internet in your policy
3. **Resolve CGNAT range conflicts** — Check whether your machine has an address or route in 100.64.0.0/10 from your ISP or cloud Set a custom IP pool for the tailnet, or add disableIPv4 to the tailnet policy file to use IPv6 only (IPv4-only resources become unreachable)
4. **Disconnect other VPNs** — Quit any other VPN app, reconnect Tailscale and retest

Full guide: https://www.tryorbye.com/products/tailscale/issues/no-internet

### Tailscale Not Connecting

When Tailscale won't connect, the cause is usually an outdated client, an expired device key, a captive portal, antivirus or another VPN. Update both devices, check key expiry in the admin console, then rule out portals and conflicting VPNs.

1. **Update Tailscale on both devices** — Check versions on the admin console Machines page or with 'tailscale version' Install the latest client on any outdated device
2. **Check for an expired key** — Open the admin console Machines page and look for an 'Expired' label Re-authenticate the device, or run 'tailscale up --force-reauth'
3. **Log in to a captive portal** — Open http://neverssl.com in a browser to trigger the portal On a trusted network, disconnect Tailscale, log in to the portal, then reconnect
4. **Disconnect other VPNs and check antivirus** — Turn off any other VPN app and retry If antivirus flags Tailscale, add it to the exceptions list
5. **Check the Tailscale status page** — Visit status.tailscale.com; during coordination server incidents existing connections usually keep working but logins fail

Full guide: https://www.tryorbye.com/products/tailscale/issues/not-connecting

### Tailscale Not Working With Another VPN

Tailscale says most VPNs can't run alongside it without a workaround: firewall rules drop its traffic, the 100.64.0.0/10 range can clash, and phones allow one VPN at a time. Use Mullvad exit nodes, userspace networking or split tunneling.

1. **Use Mullvad exit nodes instead** — If you want a privacy VPN, add the Mullvad exit-node add-on ($5/month per 5 devices) in the admin console Select a Mullvad exit node in the Tailscale client instead of running the Mullvad app
2. **Use split tunneling in the other VPN** — Exclude the Tailscale app/daemon from the other VPN, or route 100.64.0.0/10 and fd7a:115c:a1e0::/48 outside it Add any subnet routes you use as well; this doesn't work with exit nodes
3. **Run Tailscale in userspace networking mode** — Start tailscaled with userspace networking so it doesn't create an interface or change firewall rules Reach tailnet hosts through the local SOCKS5 proxy and use 'tailscale ping' instead of ping

Full guide: https://www.tryorbye.com/products/tailscale/issues/other-vpn-conflict

### Tailscale Slow? Connection Relayed via DERP

Tailscale is slow mostly when a connection goes through a DERP relay instead of directly between devices. Confirm with 'tailscale status' or 'tailscale ping', then allow UDP 41641, enable UPnP/NAT-PMP on your router, or run a peer relay.

1. **Check whether the connection is direct** — Run 'tailscale status' and look at the peer's line for 'direct', 'relay' or 'peer-relay' Run 'tailscale ping <device>' and ignore the first replies; later replies should say 'via <IP>:<port>' for a direct path Run 'tailscale netcheck' on both devices to see UDP support, port mapping and nearest DERP latency
2. **Allow UDP 41641** — Allow inbound and return UDP on port 41641 in the device firewall and any cloud security group If you need another port, start tailscaled with --port=<number> (on Linux set it in /etc/default/tailscaled) Re-run 'tailscale ping' to see if it switches to direct
3. **Enable UPnP or NAT-PMP on your router** — Open your router's admin page Turn on UPnP or NAT-PMP so Tailscale gets predictable, reachable ports Reconnect Tailscale and check 'tailscale status' again
4. **Give cloud machines a public IP** — Attach a public (static or dynamic) IP to the cloud instance running Tailscale instead of routing it through a NAT gateway
5. **Run a peer relay** — If you can't change the network, deploy a Tailscale peer relay inside your own infrastructure (both ends on a recent client) Peer relays are generally faster than DERP and avoid cloud gateway egress

Full guide: https://www.tryorbye.com/products/tailscale/issues/slow

### Tailscale SSH Permission Denied

'Permission denied (tailscale)' means the policy's SSH section doesn't allow your user to log in as that local user. Add an ssh rule for your source and target user, confirm the Unix user exists, and use accept mode for automated jobs.

1. **Add an SSH rule to the policy** — Open Access controls in the admin console In the ssh section, add a rule with action 'accept' or 'check', your user or group as src, the device or tag as dst, and users such as autogroup:nonroot Use the Preview rules tab to confirm
2. **Confirm the local user** — Make sure the Unix user you log in as exists on the target machine
3. **Use accept mode for automation** — Change the rule from 'check' to 'accept' for backups and scripts that can't open a browser
4. **Update to v1.104.4 or later** — Update tailscaled on every Tailscale SSH host to pick up the October 2026 security fixes (TS-2026-014 to TS-2026-017)

Full guide: https://www.tryorbye.com/products/tailscale/issues/ssh-permission-denied

### Tailscale Subnet Router Not Working

Subnet routes do nothing until they are approved in the admin console, IP forwarding is on and the policy allows access. If local LAN access breaks instead, turn off --accept-routes on devices that are already on that LAN.

1. **Approve the routes** — Open the admin console Machines page Open the subnet router's ... menu and choose Edit route settings Enable the advertised routes and save (or use autoApprovers in the policy)
2. **Enable IP forwarding and check the CIDR** — Enable net.ipv4.ip_forward and IPv6 forwarding on the Linux router Advertise the correct prefix, for example 'sudo tailscale set --advertise-routes=192.168.1.0/24'
3. **Allow the subnet in the policy** — Open Access controls and allow your users to reach the subnet and ports Use the Preview rules tab to confirm
4. **Fix broken LAN access** — On devices that are on the same LAN, run 'tailscale set --accept-routes=false' Or connect to devices by their Tailscale IP instead of the LAN IP

Full guide: https://www.tryorbye.com/products/tailscale/issues/subnet-router-not-working

## Common problems

- **Why is Tailscale so slow? Connections stuck on DERP relay** (performance): When two devices cannot punch through NAT (blocked UDP, hard NAT, cloud NAT gateways), Tailscale relays traffic through its DERP servers, which add latency and cap throughput for fairness. Tailscale's own docs call this the most common cause of poor performance, and NAS, router and homelab forums repeatedly report big speed drops until a direct path is found.
- **Tailscale exit node has no internet** (reliability): Exit nodes often connect but pass no traffic because IP forwarding is off on the Linux node, the policy does not grant autogroup:internet, or a router (GL.iNet, OpenWrt, pfSense, TrueNAS) is missing NAT or firewall forwarding rules. Many forum threads describe the same symptom across router and NAS platforms.
- **Tailscale MagicDNS not working or overwriting resolv.conf on Linux** (reliability): On Linux, Tailscale rewrites /etc/resolv.conf when MagicDNS is on and no DNS manager is running, and setups with NetworkManager, Pi-hole or custom resolvers can lose name resolution or .ts.net lookups. Tailscale recommends systemd-resolved or --accept-dns=false as workarounds.
- **Tailscale doesn't work with other VPNs like Mullvad** (integrations): Tailscale's own FAQ says that in most cases it cannot run alongside another VPN without a workaround because of aggressive firewall rules, the one-VPN limit on iOS and Android, and conflicts in the 100.64.0.0/10 range. WireGuard-based VPNs such as Mullvad are a known conflict; the supported route is Tailscale's paid Mullvad exit-node add-on.
- **Tailscale device offline after node key expired** (reliability): User devices must re-authenticate when their node key expires; if nobody does, connections to and from that machine stop, and headless servers, NAS boxes and routers silently drop off. Some expired devices still look online in the admin console. Auth keys used for re-registration also expire after at most 90 days.
- **Tailscale raised its business plan price from $6 to $8 per user** (pricing): With pricing v4 (April 2026) the Starter plan was renamed Standard and its per-user price went from $6 to $8 a month, and billing moved from monthly active users to seats, including vacant ones. Existing plans keep their price for at least 12 months before migration.
- **Tailscale Android app keeps disconnecting or draining battery** (mobile): Android users report the app stopping every 10-20 minutes, staying disconnected with 'Block connections without VPN' enabled, and battery use of around 10-15% when connected all day. Fixes that work for some (always-on VPN, unrestricted battery, disabling MagicDNS) do nothing for others.
- **Tailscale SSH 'Tailworm' security flaws (October 2026)** (security): In October 2026 a researcher published 'Tailworm', showing that an authorized Tailscale SSH session could act beyond its local user's privileges, including via SSH forwarding, plus bugs in Serve and Funnel. Tailscale fixed them in v1.104.4 (bulletins TS-2026-014 to TS-2026-017); exploitation needed an existing foothold on an allowed device.
- **Tailscale ACLs and subnet routes are confusing** (usability): Beyond the basic mesh, subnet routes need approval in the admin console plus IP forwarding, --accept-routes can break local LAN access, and access is governed by a JSON policy file of ACLs, grants and SSH rules. Reviewers say some tasks are possible but cumbersome and don't scale well, and G2's top con is access issues.
- **Tailscale free plan is non-commercial only** (pricing): The Personal plan is free for up to 6 users with unlimited user devices, but it is meant for non-commercial use only, includes 50 tagged resources ($1/month each beyond that), 3 ACL groups and basic SSH limited to 5 hosts. Businesses must pay per seat, and vacant seats are billed too.
- **Is Tailscale down? Coordination server outages block logins** (reliability): Third-party status trackers count roughly 70-90 Tailscale incidents per year, most involving the coordination server, admin console and API. Existing connections usually keep working, but new logins, new devices and config changes fail; most incidents last under an hour, with a few lasting several hours.
- **Tailscale on iPhone won't connect or keeps restarting (VPN On Demand)** (mobile): iOS VPN On Demand rules can stop Tailscale from connecting or immediately undo a manual reconnect, and only one VPN app can hold On Demand. A GitHub issue against version 1.92.3 on iOS 26.2 describes Tailscale repeatedly restarting until On Demand is turned off several times.
- **Tailscale on Windows not connecting after reboot** (reliability): Windows users report the service running while the client says 'Tailscale is stopped' or 'Logged out', and tailnet addresses not resolving after boot until they reconnect. Restarting the service helps temporarily; some needed a clean reinstall.
- **Tailscale requires a Google, Microsoft, GitHub or Apple login** (onboarding): Tailscale has no email-and-password sign-up: you log in through an identity provider (Google, Microsoft, GitHub, Apple, Okta, OneLogin or custom OIDC). Passkey accounts exist but only via an admin invite, which privacy-minded users find awkward.

## What users like

- **Works in minutes without opening ports**: Users consistently call it the most plug-and-play option: install, sign in, and devices can reach each other through NAT with no port forwarding. Ease of use is the top G2 pro.
- **Generous free Personal plan**: Free for up to 6 users with unlimited user devices and nearly all features, which covers most homelabs and families.
- **WireGuard encryption end to end**: Direct, peer-relay and DERP-relayed connections are all end-to-end encrypted with WireGuard, so relays affect speed, not security.
- **Runs almost everywhere**: Clients for Windows, macOS, Linux, iOS, Android and packages for Synology, TrueNAS, Unraid, pfSense, OpenWrt and Docker make it a common choice for NAS and router remote access.
- **Fast when connections are direct**: Users who moved from ZeroTier describe Tailscale as more performant and stable, and direct peer-to-peer connections give the lowest latency and highest throughput.
- **Self-hosting option via Headscale**: The open-source Headscale control server works with the official Tailscale clients, so users who want to avoid the hosted coordination server have a path out.

## Pricing

- **Personal**: $0.00 (free) — hidden costs: Extra tagged resources $1/month each beyond 50; Mullvad exit nodes add-on $5/month per 5 devices
- **Standard**: $8.00 (monthly) — hidden costs: Billed per seat including vacant seats; seat count rises automatically when a new user logs in while seats are full; annual billing only via sales
- **Premium**: $18.00 (monthly) — hidden costs: Billed per seat including vacant seats; extra ephemeral minutes and support packages are contact-sales
- **Enterprise**: monthly — hidden costs: Custom pricing via sales only

## Who should and shouldn't use it

- **Homelab and NAS owners** — Good fit: Free plan, packages for Synology/TrueNAS/Unraid and no port forwarding make remote access to home servers easy.
- **Small engineering teams** — Good fit: Replaces a legacy company VPN quickly with SSO login and policy-based access; $8 per user on Standard.
- **Families sharing devices** — Good fit: Up to 6 users free with unlimited devices.
- **Privacy VPN shoppers (hide IP, streaming)** — Avoid: Tailscale is not a commercial privacy VPN; you need your own exit node or the paid Mullvad add-on, and it conflicts with other VPN apps.
- **Users behind strict NAT or blocked UDP** — Depends: Traffic falls back to DERP relays and gets slow unless you can open UDP 41641 or run a peer relay.
- **Users who must run another VPN at the same time** — Avoid: Tailscale officially says most VPNs can't run alongside it without workarounds; phones allow one VPN at a time.
- **Organisations that must self-host everything** — Depends: The coordination server is hosted by Tailscale; Headscale or NetBird self-hosted are the usual routes.
- **Large enterprises with compliance needs** — Depends: Premium/Enterprise add flow logs, log streaming and JIT access, but pricing is per seat and Enterprise is contact-sales.

## Alternatives

- **Headscale**: Open-source, self-hosted control server that keeps the official Tailscale clients. You gain full control and no seat fees; trade-off is running and maintaining it yourself with thinner docs and no official admin UI.
- **NetBird**: Open-source WireGuard mesh with a web dashboard, DNS and access control; users who self-host it say the self-hosted experience matches the paid one. Trade-off: more moving parts to deploy.
- **ZeroTier**: Older virtual-network tool that handles multicast and layer-2 better; some users find it less performant and stable than Tailscale and dislike its move from GPLv3 to BSL.
- **Twingate**: Zero-trust remote access aimed at businesses replacing a company VPN; better fit for app-level access than a full mesh.
- **WireGuard**: Plain WireGuard has no coordination server or account at all; you trade Tailscale's NAT traversal and key management for manual config and port forwarding.
- **Mullvad VPN** (https://www.tryorbye.com/products/mullvad-vpn): If you actually want a privacy VPN to hide your IP rather than a private network between your own devices, a commercial VPN like Mullvad is the right tool (and Tailscale even resells it as exit nodes).

## FAQ

### Is Tailscale worth it?

For connecting your own devices and servers, yes: the free Personal plan covers up to 6 users with unlimited devices and setup takes minutes. It is less worth it if you need a privacy VPN, must run another VPN at the same time, or sit behind networks that force slow DERP relays.

### Is Tailscale free?

Yes. The Personal plan is free for up to 6 users with unlimited user devices, 50 tagged resources and nearly all features, but it is for non-commercial use only.

### How much does Tailscale cost?

Personal is free, Standard is $8 per user/month, Premium is $18 per user/month and Enterprise is custom. Paid plans bill per seat, including vacant seats. Annual billing is handled through sales.

### Did Tailscale raise its prices?

Yes. Pricing v4 (April 2026) renamed Starter to Standard and raised it from $6 to $8 per user/month, retired Personal Plus and moved business billing to seats. Existing plans keep their price for at least 12 months.

### Why is Tailscale so slow?

Usually because the connection is relayed through a DERP server instead of going direct. Check with 'tailscale status' or 'tailscale ping'. Allowing UDP 41641, enabling UPnP/NAT-PMP on your router or running a peer relay usually fixes it.

### Is Tailscale a real VPN?

It is a mesh VPN that connects your own devices privately. It does not hide your IP like NordVPN or Mullvad unless you route traffic through an exit node you run, or pay for the Mullvad exit-node add-on ($5/month per 5 devices).

### Can I use Tailscale with another VPN?

Usually not without workarounds. Tailscale says most VPNs conflict through firewall rules, the 100.64.0.0/10 range or the one-VPN limit on iOS and Android. Options are userspace networking, split-tunnel DNS on the other VPN, or Tailscale's Mullvad exit nodes.

### Is Tailscale safe?

Traffic is end-to-end encrypted with WireGuard, even over relays. In October 2026 'Tailworm' research exposed Tailscale SSH privilege flaws (fixed in v1.104.4); if you use Tailscale SSH, update and tighten your SSH policy.

### Why did my Tailscale device go offline?

The most common cause is node key expiry: user devices must re-authenticate periodically. For servers, disable key expiry from the machine's menu on the admin console Machines page.

### Can I use Tailscale without a Google or Microsoft account?

There is no email/password sign-up. You can use GitHub, Apple, Okta, OneLogin or a custom OIDC provider, or join a tailnet with a passkey through an admin invite.

### Can I self-host Tailscale?

Not officially; the coordination server is hosted by Tailscale. The open-source Headscale project replaces it and works with the official clients, and NetBird is a fully self-hostable alternative.

### Does Tailscale drain battery on Android?

Some users report 10-15% battery use when connected all day and background disconnects. Setting the app to unrestricted battery use and making it the always-on VPN helps some users.

### How do I cancel Tailscale?

An Owner, Admin or Billing admin opens the admin console Billing page, opens the menu in Your plan and selects Cancel subscription. The tailnet moves to the free Personal plan at the end of the billing period; you need 6 or fewer users first.

---
Try or Bye aggregates problem patterns from user reviews, forums, and app stores. Methodology: https://www.tryorbye.com/methodology