Why remote access is the awkward part
Installing Jellyfin on Windows is easy. The Windows installer runs the server, and you finish setup in a browser on port 8096.
Remote access is harder because Jellyfin doesn't expose itself to the internet for you. The usual routes are forwarding ports, putting a reverse proxy with a domain in front of the server, or using a tunnel service. Jellyfin's networking documentation says it plainly: opening a port directly to the internet is insecure and not recommended. Hmm, that is a paraphrase of the docs rather than a result from my search, so treat it as Jellyfin's stated position. The same documentation lists a VPN connection as one of the common ways to reach the server.
Tailscale is a WireGuard-based VPN. Jellyfin's own guide says it fits when opening ports isn't wanted or possible, for example behind carrier-grade NAT or when an ISP blocks incoming ports.
The setup, as described and as documented
Arjunan's steps match Jellyfin's documented "direct" Tailscale method.
- Install Jellyfin on the Windows PC. He chose the option to run it as a Windows service so it starts before anyone signs in. He then opened
[url]http://localhost:8096[/url], finished the wizard and added his SSD folders as libraries. - Install Tailscale on the server and the client. He created an account and authorized both devices, which created his tailnet.
- Find the server's Tailscale address. It starts with 100, for example
100.12.34.56. - Point the Jellyfin client at that address and port. In the Jellyfin app, enter the Tailscale IP plus port 8096. The WunderTech guide gives the same pattern: server's Tailscale address followed by port 8096, saved as your server address in the Jellyfin app.
- Test off your home network. SmallGrid's guide suggests switching a phone from home Wi-Fi to mobile data.
Tailscale addresses come from the 100.64.0.0/10 range. They don't change when a device moves networks, for example from Wi-Fi to cellular, per Tailscale's documentation. That is why a saved address in a Jellyfin client keeps working as you move around.
Two "run at startup" settings, not one
Arjunan describes two things that are easy to conflate.
- Jellyfin as a Windows service. Jellyfin's service guide says this lets it start at boot and keep running with no user logged in. It recommends the Network Service account over Local System. It also recommends read-and-execute access on media folders, unless you want Jellyfin to delete files or save subtitles and metadata into them. The guide's troubleshooting section says that if the wizard shows empty libraries, Network Service needs at least list-folder permission on the parent folders. Jellyfin also notes that the standard installer is recommended for most users, and a service is best for dedicated servers.
- Tailscale's Run unattended. On Windows, Tailscale normally runs inside the signed-in user's session. It disconnects when the user signs out or the PC restarts. Unattended mode, on Windows 10 or later and Windows Server 2016 or later, keeps the configured profile connected after sign-out or restart. Tailscale documents the path as right-click the tray icon, then Preferences, then Run unattended, and confirm the prompt. This mode exists only on Windows.
Tailscale's documentation adds checks Arjunan doesn't mention:
- To verify unattended mode, restart without logging back in, then run
tailscale pingagainst the PC's Tailscale IP or MagicDNS name from another tailnet device. - If it is unreachable, check in
services.mscthat the Tailscale service is set to Automatic and running. - Node keys expire after 180 days by default and need interactive re-authentication. For a headless server you can disable key expiry in the admin console, but Tailscale says to do that only for trusted devices.
- Unattended mode gives the Windows user who enabled it exclusive control of the Tailscale configuration on that device.
Neither setting keeps the PC awake. Arjunan says his PC doesn't sleep while plugged in, which is his own practice and not a documented requirement. If the machine sleeps, the server is gone.
Firewall and permissions
Jellyfin's Windows service guide says that for other devices to connect, you must add a Windows Firewall rule allowing inbound TCP on port 8096. Don't assume Tailscale removes that step. If a Tailscale client can't reach the server but it works on the LAN, check the firewall rule first. Jellyfin's own advice is to confirm it works locally before troubleshooting Tailscale.
The default ports are TCP 8096 for HTTP and TCP 8920 for HTTPS, which is off by default. UDP 7359 handles local discovery and doesn't work beyond the local subnet. That is why you type the address manually instead of relying on auto-discovery.
What "private" does and doesn't mean
Arjunan says that because it's a private network, only devices you've authorized can reach the server. That is true as far as it goes, but the boundaries matter.
- Jellyfin's Tailscale guide lists the cons of the direct method: every client needs Tailscale, it needs an account with a third party, and blocking tailnet clients from reaching each other takes extra complex configuration.
- A WindowsForum discussion of this topic makes a related point. Tailscale's default access policy lets you connect to all devices you own, so if you share your tailnet, use the policy file to restrict who can reach the server.
- Arjunan says he can invite five other people. Tailscale's pricing page at the time of this brief listed the free Personal plan as $0, with unlimited devices and up to six users. Five invitees fits that if you count as the sixth. It is for personal, non-commercial use. Inviting someone to your tailnet is broader than sharing a single device, and by default an invited user can reach tailnet devices subject to access controls. If the PC hosting Jellyfin also holds other things you care about, set access rules before inviting family.
- Jellyfin has its own controls. In the dashboard, Networking has Remote Access Settings, and each user has an "Allow remote connections to this server" option. Jellyfin accounts and permissions still matter.
Performance: the honest caveat
Arjunan calls the performance "pretty great" over mobile data and other Wi-Fi networks. He also reports occasional stutters and uses Jellyfin's bitrate limit to keep playback under control. That is anecdotal. He gives no bitrates, hardware, upload speeds or codecs.
Tailscale's documentation explains one thing that can affect results. All connections are end-to-end encrypted with WireGuard, whether direct or relayed. Direct connections usually give the lowest latency and highest throughput. Relayed connections are a fallback, and Tailscale says using a relay when a direct path was possible is one of the most common causes of performance problems. You can check with tailscale status. Output containing "direct" is a direct connection, and "relay" means a DERP relay.
The XDA Developers write-up on remote Jellyfin makes the same point, saying that if you see a relay, CGNAT is interfering with the stream, and throughput suffers. Neither source establishes that relaying caused Arjunan's stutters, so that is a diagnostic to try, not a conclusion. Jellyfin's hardware guidance also lists home upload bandwidth as relevant to remote streaming, and a tailnet doesn't change that.
Limits to know before you commit
- Every client needs Tailscale. Arjunan notes that a smart TV that can't run it could be a problem. If your household includes such devices, the alternative is a reverse proxy, which Jellyfin documents. It is more involved, needs a domain and HTTPS, and isn't the simple direct setup described here. A hybrid is also documented: Tailscale between the server and a remote reverse proxy, which needs the proxy's Tailscale IP added to Jellyfin's known proxies setting.
- The server must be on. An asleep, off or offline PC is unreachable.
- A third-party account is involved. That is a trade-off against fully self-hosted routes.
- Plan details can change. Check Tailscale's current pricing before relying on user limits.
Bottom line
For a household whose devices can run Tailscale, this is a credible way to reach a Windows-hosted Jellyfin server without port forwarding or a domain. The documented steps are short. The reliability work is separate: running Jellyfin as a service, enabling Tailscale unattended mode, allowing the firewall rule, setting folder permissions and keeping the PC awake. Treat the author's glowing performance comment as one user's experience, and set tailnet access rules before you share it.
References
- One free app fixed the hardest part of running a Jellyfin server MakeUseOf · 2026-10-27T12:00:16+00:00
- How to Access Jellyfin Remotely (4 Methods That Work) - WunderTech wundertech.net
- Jellyfin Remote Access with Tailscale on Ubuntu - SmallGrid.uk smallgrid.uk