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.

    • Opisek@lemmy.worldEnglish
      41·
      11 hours ago

      Just because the destination IP address is not a LAN address? That’s not misconfiguration, that’s a legitimate use of NAT reflection/loopback. If that’s how it determines who is streaming remotely then just run it behind nginx that forgets to set the correct headers.

      Edit: Apparently Plex centrally relays all the traffic? Self-hosted my 🍑, it’s not self-hosted if you need to rely on their server.

      • amorpheus@lemmy.worldEnglish
        5·
        10 hours ago

        It doesn’t relay all traffic, that’s a fallback if a connection can’t be established.

          • hedgehog@ttrpg.networkEnglish
            103·
            18 hours ago

            OP is also in the allegedly ultra rare camp of “successfully configured Jellyfin and lived to tell the tale.” Not what I’d expect of someone unable to configure Plex correctly. I’ve not set up a Plex server myself but my guess is it wasn’t clear that it was misconfigured - it did work previously, after all.

            • Nibodhika@lemmy.worldEnglish
              2·
              11 hours ago

              I can’t speak for OP, but I self host lots of stuff, have literally dozens of services running, have an Ansible repo to manage it all and routi some stuff through a VPS, not to mention my day job has included managing services in one way or another for a long while. This is to say, I know what I’m doing. I couldn’t setup Plex to work the way I wanted to, they expect it to run in a docker with network set to host mode, I couldn’t find any way to tell Plex that my living room TV was in the same network, it just wouldn’t accept any connections as local. I know I shot myself in the foot here by not letting it run with network on host mode, but I shouldn’t have to, the port was exposed, I could reach it through the local network IP, but I wasn’t able to stream any content locally.

            • gdog05@lemmy.worldEnglish
              41·
              16 hours ago

              Well, with Plex constantly changing allowed abilities and such, it seems to me that this is the expected outcome.

              • CmdrShepard49@sh.itjust.worksEnglish
                1·
                16 hours ago

                This is one change (which isn’t the cause of OP’s problem) that they announced months ago. I’ve been using it for well over a decade and while I have had major issues with it in the past going so far as to setup Emby and buying a lifetime license for that, I would hardly say that they’re “constantly changing allowed abilities.”

                Most people’s issue with them is that they focus too much on adding new stuff that nobody asked for while ignoring longtime bugs. I can’t recall a time they’ve ever locked anything behind a paywall that wasn’t a brand new feature prior to this.