Comment on Plex has paywalled my server!

• Zanathos@lemmy.world ⁨1⁩ ⁨week⁩ ago

  Are you running in docker? Change from bridged mode to host mode on your container which should resolve this.

  source

  • Nibodhika@lemmy.world ⁨1⁩ ⁨week⁩ ago

    Yes I am, but I don’t want to give full control of my network drive to a closed source application because it paywalled me out of being able to access my media on my local network. It’s ridiculous that I have to do that. It breaks ECI, and is a security risk. And yeah, it’s a bit paranoid, but the fact that they can fix it with a simple config and put that behind a paywall is VERY worrisome, so I now need to pay if I want to isolate Plex from the host where it’s running.

    source

    • Zanathos@lemmy.world ⁨1⁩ ⁨week⁩ ago

      You’ve likely given it full control to whatever storage you’ve mounted in the container anyway, unless you’ve given it the :ro flag, which in that case would operate the same regardless of networking mode. If someone gains access to your internal host, you have bigger problems. Some things just play better under host mode and all bridged mode is doing is creating a virtual switch on your host and passing allowed traffic through it at a base level. The best way to protect is by running a load balancer in a DMZ and proxying all of the traffic through it which is how I have my instance running. I funnel everything external --> TCP\UDP 443 in DMZ vlan load balancer --> internal LAN IP:docker port. I run a mix of host network or bridged mode depending on the container.

      source

      • Nibodhika@lemmy.world ⁨6⁩ ⁨days⁩ ago

        Giving it write access to a folder is not even remotely on the same level as giving it control over the host networking. Worst case scenario in the volume access is to delete that data, which is on a btrfs drive and has backups, worst case scenario for network host is root access to host machine.

        source

        • -> View More Comments