Appears to be Hetzner for now, wouldn’t be surprised if all VPS get affected eventually.

  • pe1uca@lemmy.pe1uca.dev
    link
    fedilink
    English
    arrow-up
    91
    arrow-down
    2
    ·
    1 year ago

    I never understood this, it’s your selfhosted server but you kind of don’t own it and depend on them, so you just have an application which depends on a their service which means plex isn’t 100% selfhostable, correct?

    • Domi@lemmy.secnd.me
      link
      fedilink
      English
      arrow-up
      58
      arrow-down
      2
      ·
      1 year ago

      Plex has been hostile towards self-hosting since the very beginning. They have been asked to add local authentication for more than 10 years.

      • shyguyblue@lemmy.world
        link
        fedilink
        English
        arrow-up
        33
        arrow-down
        2
        ·
        1 year ago

        Yup, as soon as they started the mandatory login bullshit, I bounced. Companies keep adding this “feature” as a way to control your stuff: Doom on Switch, Halo Master Chief edition, nvidia, my fucking mouse(!?); all need a login for no other reason than to add a point of failure/killswitch.

    • aard@kyu.de
      link
      fedilink
      English
      arrow-up
      38
      ·
      1 year ago

      The problem is that they want to route control through their own servers for making sure you can’t use some of the extra features without paying.

      A few years back they dropped some clients (including the one for my old TV) because they were dropping support for legacy SSL ciphers on their servers - and those devices didn’t have support for the new ciphers. This is a pretty stupid dependency due to the way they want to do things - so I moved to jellyfin back then, and have been encouraging people to drop plex ever since.

      • PuppyOSAndCoffee@lemmy.ml
        link
        fedilink
        English
        arrow-up
        22
        arrow-down
        1
        ·
        1 year ago

        To be fair, old ssl isn’t really ssl at all & considered to be a vulnerability by a lot of libraries.

        • aard@kyu.de
          link
          fedilink
          English
          arrow-up
          11
          ·
          1 year ago

          Without them forcing you to go through their server for user authentication it’d be a thing local to your network - where it wouldn’t really matter. Without that stupid requirement you also could just keep unsupported clients running by yourself.

        • Moonrise2473@feddit.it
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          But also on the other side, we’re talking about just media consumption, not banking or other sensitive data

          • PuppyOSAndCoffee@lemmy.ml
            link
            fedilink
            English
            arrow-up
            4
            arrow-down
            2
            ·
            edit-2
            1 year ago

            Yeah, I agree, and ultimately shame on the tv manufacturer. However many software just won’t connect so it’s not really a plex issue. If they use a library that won’t support it…

      • droans@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        ·
        edit-2
        1 year ago

        A few years back they dropped some clients (including the one for my old TV) because they were dropping support for legacy SSL ciphers on their servers

        TLS 1.0/1.1? Those were deprecated and dropped by the IETF with RFC 8996. You can’t even get a certificate using 1.0/1.1 anymore unless you are self-signing.

        You can also allow unauthenticated users on certain networks, usually limited to your local nets. But I do agree that doesn’t solve the problem. I’d love to allow users to optionally use local authentication with, eg, Authelia, something built in, or an LDAP backend.