Why not? It depends on your situation, but if you have a static IP or a dyndns service, you can just open a port to your Jellyfin and reach it from anywhere.
You can also stick a reverse proxy in front of it, if you want to feel safer.
Comment on Plex’s crackdown on free remote streaming access starts this week - Ars Technica
Son_of_Macha@lemmy.cafe 1 day ago
Good luck setting up remote streaming with Jellyfin.
Why not? It depends on your situation, but if you have a static IP or a dyndns service, you can just open a port to your Jellyfin and reach it from anywhere.
You can also stick a reverse proxy in front of it, if you want to feel safer.
or use tail scale / headscale
Yes, but that’s not always doable, e.g. on LG TV’s.
You can “proxy” tailscale networks, you’d need 1 device per household with tailscale running and accepting/advertising routes. Not sure if tailscale IP addressing works in that case though, and just doing it via private IP can get problematic with same network range in the household
Any old Raspberry Pi on your network can forward a port from LAN to the Jellyfin server on Tailscale somewhere. Single iptables masquerade command should do the trick. Or if you happen to have a good router with owrt support you can run Tailscale there too.
while not technically allowed by cloudflare TOS for the free plan, it’s possible to host jellyfin under a cloudflare tunnel
I’d strongly recommend reverse proxy, some sort of security like crowd sec or fail2ban and sperate auth (authelia, aithentik) in front of anything you’re opening to the internet. Just opening services directly up to the internet is choice I’d politely describe as brave.
How do you manage a separate auth (I imagine HTTP auth) with app clients?
“Good luck setting up remote streaming with free Plex.”
Yes, Jellyfin does not forward ports for you. Same as free Plex. With this change both are the same difficulty to set up for free, the only difference is with Plex there’s a shortcut: Buy Plex.
I don’t think simply forwarding the port actually works with free Plex anymore. I think if the server has a different public IP from the client it asks you to pay, even if you’re connecting to the server over LAN.
Interesting, maybe they check whether it’s a domain/remote IP on the client side to prevent usage of a reverse proxy.
I checked the logs and it said it was assuming a remote connection because there was an unknown hostname in the headers (I forget the exact wording). It was because the hostname I was using didn’t match the hostname configured in the server’s OS (one I set up on my local DNS server).
Already did ages ago
domi@lemmy.secnd.me 22 hours ago
Sir, this is a /c/selfhosted.