Ahoy mateys, it’s time to setup Jellyfin if you prefer not to pay for the privilege of self-hosting your own content.
cross-posted from: https://programming.dev/post/27204525
We are also changing how remote playback works for streaming personal media (that is, playback when not on the same local network as the server). The reality is that we need more resources to continue putting forth the best personal media experience, and as a result, we will no longer offer remote playback as a free feature. This—alongside the new Plex Pass pricing—will help provide those resources. This change will apply to the future release of our new Plex experience for mobile and other platforms.
Opening a port isn’t really bad if you have your firewall configured properly. You will have to open a port either way with jellyfin or wireguard. If you have a TLS/SSL certificate then just doing jellyfin is fine (but have good passwords since it’s public facing), otherwise a VPN like wireguard will handle encryption for you.
As for managing traffic on the VPN you can follow this advice: https://serverfault.com/questions/1075973/wireguard-how-to-only-tunnel-some-of-the-traffic
Basically setup your firewall to stop extra traffic on your end, and change accessible IPs in wireguard to your service(s) so the peer knows not to talk on that interface for unrelated things.
you can do a thing called UDP hole punching for NAT traversal, buuuuuut afaik these days a lot of consumer routers consider it a security risk and attempt to block it
It isn’t bad until an exploit is discovered on jellyfin. Then it can get really bad.
Do you have a recommended way of remote accessing a server?
It already happened on Plex. Just a matter of time until it happens to Jellyfin.