Blog

Jellyfin works at home but not away? Here's why

Everything works on the couch. Then you try it on your phone's mobile data, or at a relative's house, and Jellyfin won't connect. This is the single most common wall people hit with Jellyfin, and the reason is almost always the same: your home network is built to keep outsiders out, and from the internet's point of view, you're now an outsider.

Here are the four usual causes, and what to do about each.

1. You're using your home address

Inside your house, the app talks to the server at a local address like 192.168.1.20. That address means nothing outside your home. Away from home, you need an address that leads back to your house over the internet.

What to check: look at the server address saved in the app. If it starts with 192.168, 10. or 172.16 to 172.31, it only works at home.

2. Your router isn't letting the connection in

Even with the right public address, your router drops connections it didn't ask for. To let people watch from outside, the router has to send one port (a numbered door) to the computer running Jellyfin. That's called port forwarding.

What to check: your router's settings page, usually under "Port forwarding" or "NAT". Some routers can do it automatically through a feature called UPnP.

3. Your internet provider shares one address between many homes

Some providers, especially mobile and fixed-wireless internet, put many customers behind one shared public address. That's called CGNAT. With CGNAT, port forwarding can't work, however you set up the router, because the connection never reaches your router at all.

What to check: compare the internet address your router shows with the one a "what is my IP" site shows. If they differ, you're probably behind CGNAT. Our CGNAT guide explains the ways around it.

4. No HTTPS certificate

Some apps and browsers refuse, or warn loudly about, a plain unencrypted connection over the internet. Your password would also travel unprotected. A proper public setup needs an HTTPS certificate for your address, and certificates expire, so they need renewing.

The two routes that work

Private access with Tailscale. Tailscale makes a private network between your own devices. The personal plan is free and no ports are opened, and it works behind CGNAT. The catch: everyone who watches has to install Tailscale on their device, which is fine for you and harder for Grandma's TV.

A public address with HTTPS. A web address that works on any device, from any network. That needs a name, DNS that follows your home's changing address, an open router port and a certificate that renews. It's very doable, but there are several pieces to get right. The full walkthrough is in Jellyfin remote access, step by step.

Or let Reelhost do it

Reelhost's watching away from home sets up either route for you:

  • Private access through Tailscale, with no ports opened.
  • Or a public address like yourname.watchhome.app, with DNS that follows your home's address, an HTTPS certificate issued and renewed automatically, the router port opened by UPnP, and a check from outside to prove it works. IPv6 is covered too, and you can use your own domain instead.

Video streams straight from your home to your device. Reelhost's servers never see it. Reelhost is an independent app that works with Jellyfin. It isn't affiliated with the Jellyfin project.

Start with the free check-up. It shows what's blocking you from outside, in plain words, in a few seconds.