I tried testing a movie from my home server in plex through firefox and repeatedly got this message, even after reloading.

I knew that they had paywalled the apps on mobile and streaming from outside the network but now they have also blocked watching your own movies through your own hardware.

I do get the point that making software should be able to sustain people but I dont see the move of plex as a fair thing to do. Yes, they have made great software but taking your home server hostage feels like the wrong move.

Even a pop up that says “we need you to donate please” would have been fine. make it pop up before every movie, play donation ads before any movie but straight up disabling the app is kinda cruel.

Anyway, i have switched to jellyfin and it is insanely good. please give it a try. you can run it alongside plex with not issues (at least i had none) and compare the two.

In any case, good luck. Let me know if you need help.

  • ipkpjersi@lemmy.mlEnglish
    1·
    24 hours ago

    Are you sure that works? I’m pretty sure they mentioned that reverse proxies are an unsupported (and not working) use case with Jellyfin, but I might have to look into authelia some time then.

    • rumba@lemmy.zipEnglish
      3·
      22 hours ago

      I just put it behind an HAProxy a few minutes ago, It appears to be fine. You just need something capable enough to handle web sockets. I’ve made it all the way through an episode of The real monsters without any problems.

      Again, you’re not going to be able to 2FA it that way, what I’m looking at doing is IP whitelisting it in HAProxy using a small web helper that is 2FA, accessed via the same port but on a separate path.

        • rumba@lemmy.zipEnglish
          1·
          17 hours ago

          Yeah part of doing this is keeping a ci pipeline up and unit testing against rcs and telling them exactly what’s failing. The report in that ticket gave them absolutely no choice but to try to set up an entire system to reproduce whatever the user did which they obviously don’t want to do.

          WebSocket relays are poorly implemented in a lot of proxies, Even cloudflare has its fair share of issues.

          The downside of using HA is reinventing the let’s encrypt pipeline for the 40th time, the upside is it’s dead simple, web sockets go in, web sockets go out, The logs are good, it’s easy to debug it with TCP dump If things start to get sketchy.

            • rumba@lemmy.zipEnglish
              1·
              9 hours ago

              You are doing the https unwrapping in tf/HA proxy. It’s clear text between the proxy process and the JF server

              You can do a dump off the entire network stream when it’s working, install the release candidate and do another dump of the network stream with it not working. Sift through to find the changes.

              When the person posted that there was a problem with the RC, It was probably a web socket being mishandled by the proxy due to some change. You can’t just go oh there’s a problem with my third party middleware. They’re going to need to know which of their changes broke the problem. Why it breaks it, and what should be done instead if you expect them to make any kind of changes.

              The alternative is you ask them to support traffic or HA or NPM, and on a volunteer project I could see that being a bridge too far

      • rumba@lemmy.zipEnglish
        1·
        17 hours ago

        The problem with putting it behind a VPN is then all your users have to be on VPN.

        Self-service IP whitelisting would be easy and let all clients work without trying to hack in a separate VPN client.

        The only thing that would suck would be if you were on a mobile link while moving and swapping towers your IP would change so you constantly get kicked off.

        But if you were so inclined you could VPN to your own house and your IP would stay the same.