408

Plex is locking remote streaming behind a subscription in April (www.plex.tv)

submitted 3 days ago by Flatworm7591@lemmy.dbzer0.com to c/piracy@lemmy.dbzer0.com

165 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[-] FoD@startrek.website 8 points 3 days ago

I want to switch to jellyfin, I selfhost but I don't want to open a port directly to my server. I don't understand how everyone else figures this out and I'm apparently an idiot.

Also do people expect all who use my server to start a VPN each time? What if they leave it on and their other streaming services are using my bandwidth.

I don't understand and I have looked it up but I don't see a consensus.

[-] amldvk@lemm.ee 5 points 3 days ago

I just use Tailscale when remote streaming.

From their docs:

By default, Tailscale acts as an overlay network: it only routes traffic between devices running Tailscale, but doesn't touch your public internet traffic, such as when you visit Google or Twitter. The overlay network configuration is ideal for most people who need secure communication between sensitive devices (such as company servers or home computers), but don't need extra layers of encryption or latency for their public internet connection.

[-] JPAKx4@lemmy.blahaj.zone 2 points 3 days ago

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.

[-] cyberpunk007@lemmy.ca 2 points 3 days ago

It isn't bad until an exploit is discovered on jellyfin. Then it can get really bad.

[-] Deello@lemm.ee 2 points 3 days ago

It already happened on Plex. Just a matter of time until it happens to Jellyfin.

[-] Brodysseus@lemmy.dbzer0.com 1 points 3 days ago

Do you have a recommended way of remote accessing a server?

[-] pupbiru@aussie.zone 1 points 3 days ago

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