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.

  • psychadlligoat@piefed.social
    link
    fedilink
    English
    arrow-up
    36
    arrow-down
    1
    ·
    edit-2
    19 hours ago

    Someone else already said it and you’ve already swapped but I’ll say it in detail:

    when setting the server connection up you selected “ServerName (long string of numbers)” and not “ServerName (your IP - SECURE)”

    this routes your connection through the Plex servers and makes it not a local connection anymore. this is extremely easy to do and forget you’ve done because it barely impacts performance

    • grue@lemmy.world
      link
      fedilink
      English
      arrow-up
      28
      arrow-down
      6
      ·
      18 hours ago

      In other words, it’s a dark pattern that tricks users into letting Plex MITM their connection.

      • psychadlligoat@piefed.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 hours ago

        dark pattern

        Nope, not at all. Its extremely forward, your local IP is listed first every time IME, and your lower-down comment has it backwards as it’s your local IP that had “secure” written on it

        it’s not a dark pattern at all, people are just stupid and don’t read (including me, I fucked this up too at first)

      • Kogasa@programming.dev
        link
        fedilink
        English
        arrow-up
        14
        arrow-down
        3
        ·
        17 hours ago

        It gets around port forwarding/firewall issues that most people don’t know how to deal with. But putting it behind a paywall kinda kills any chance of it being a benevolent feature.

        • grue@lemmy.world
          link
          fedilink
          English
          arrow-up
          10
          arrow-down
          1
          ·
          17 hours ago

          Labeling it as “SECURE” (implying the other option is insecure) is enough to make it seem underhanded to me.

        • zurohki@aussie.zone
          link
          fedilink
          English
          arrow-up
          3
          ·
          16 hours ago

          port forwarding/firewall issues that most people don’t know how to deal with

          This sort of thing makes me want to tear my hair out when I hear “Why bother rolling out IPv6 when IPv4 just WORKS!?”

          NAT, port forwarding and the problems they cause are seen as expected, just the way the internet works instead of the dirty hacks they actually are. Most people aren’t old enough to remember the time when everything connected to the internet had a routable IPv4 address.