I think this is the tool you are looking for: https://github.com/luigi311/JellyPlex-Watched

I haven’t used it myself but I plan on it eventually when I do make the switch.

Gotcha, I’ve never actually considered the bandwidth limits. It looks like digitalocean includes 1TB per month and I used 242GB last month. If I ever get close to the limit I will just spin up another droplet. I don’t think I would even need to load balance unless the first one is struggling since the bandwidth allowance across all droplets is pooled together.

If you aren’t already using a reverse proxy, then do you currently just port forward or use the Plex relay? The only reason I use one is because of CGNAT. Before I moved to a place with only CGNAT I port forwarded for both Plex and Jellyfin.

We’re seeing this at work too - our public git frontend is constantly getting scraped as well as our self hosted issue tracker. We had to spend days working on fail2ban and other kinds of tools to mitigate all the traffic that’s adding tons of load to our instances, which otherwise would easily be able to handle the handful of employees who actually use these systems.

In case this helps as a reference point, I use a $5 digital ocean droplet as my Plex and Jellyfin reverse proxy and it seems to handle the traffic of 3-5 simultaneous streams just fine. I use Haproxy in tcp mode (so no http interpreting, just passing packets) in an attempt to keep the CPU load minimal and just make it a pure I/O task.

Then we’ll have to disagree about that - imo this is the perfect place to discuss Plex alternatives and what features are keeping us on Plex. I think this discussion needs to happen if we want to learn how to create viable alternatives.

I especially want to talk about this because I personally want nothing more than to switch myself and everyone who I share my library with onto Jellyfin, and I don’t think that will happen unless we talk about what’s missing. I’m personally invested in Jellyfin enough to donate to apps I don’t even use in hopes that they will improve.

Yes? Is that odd to you? If jellyfin supported it then that would be one less reason against switching which would be a good thing, wouldn’t you think? If you advocate for using jellyfin then shouldn’t you want such basic features to be supported for those who want to use them?

Even though I still use Plex full time, I very much want Jellyfin to succeed (I run it and offer it to everyone I share with), and so I want Jellyfin to be usable for people of all skill levels. I can’t get my parents to use an app that requires them to know anything about file sizes or codec compatibility or converting anything. That is why Plex is as successful as they are.

If you’re satisfied with Jellyfin lacking certain features, that’s your perogative. But I don’t think it’s that hard to empathize with someone wanting more feature parity, especially if the motivation is to make Jellyfin accessible to more people and increase adoption.

It’s honestly kind of silly to suggest that only technically minded users care about file sizes. We’re lucky enough to even know why the file is so big. My regular friends will just complain that it won’t fit, blame jellyfin, and then go back to Netflix.

You know that regular people with 64GB phones exist right? Suggesting that a non technical person should just know that they need to convert a 30GB remux using ffmpeg is absurd.

I give all my friends the choice between Plex and jellyfin (I run both containers side by side pointed to the same media folders) and they all invariably choose Plex. I think it has a lot to do with the jellyfin UI, and I think an overhaul like jellyfin-vue or something that looks like findroid needs to happen in order for jellyfin to really appeal to regular people.

I’m pretty sure what was already the case was that you needed Plex pass to use the Plex hosted relay for when port forwarding failed when behind Nat. This seems to apply to all remote streaming, including when you’re directly connected through port forwarding or a reverse proxy and not costing Plex anything to transfer your traffic.

Half of my collection is DTS HD MA or TrueHD and many have HDR. Offline caching with transcoding is an essential feature if we want jellyfin to pull ahead. Berating people who are pointing out areas of improvement is not a winning strategy.

On one hand, it looks like this only applies to streaming from a remote server where neither the server owner or the user has Plex pass, so lifetime holders or committed server operators with a subscription can continue to provide access to all our non paying friends. It isn’t explicit whether non-paying users people who port forward / do reverse proxying themselves are affected but it sounds like they are, which is utter BS since direct connections hardly cost Plex anything.

It is however nice that they’re trading this for getting rid of the mobile unlock BS - it was always awkward explaining to friends that they could watch anywhere except on their phone unless they paid $5.

On the other hand, one notable side effect is that all non-lan streaming will now be associated with a paying server owner or a paying user, which makes it impossible to use Plex to share pirated media without a user on either end giving up PII / payment information. I have a gut feeling that this is an extension of the previous piracy crackdown on OVH(?) hosted servers meant to ensure they have the identity of all users who may be engaged in selling access.

Overall, yeah another reason to move to JF. I paid for lifetime more than a decade ago so I’m going to keep using Plex until my non-paying friends start to have issues, but I really hope this pushes more investment into JF apps. I really need a good android TV app that supports server transcoding (IIUC findroid’s beta TV builds are direct stream only).