The update got released over 2 months ago. So sensible admins should not be getting hit by this.

Also I use Jellyfin btw.

top 50 comments

sorted by: hot top controversial new old
[–] 3 points 6 days ago (2 children)

Jellyfin has plenty of issues with public instances too. It's just the reality of exposing to the public internet, unless it's something that has a lot of dedicated work going into security it's going to have problems.

  • source
  • hideshow 2 child comments
  • [–] 4 points 6 days ago (1 child)

    Could you specify any of those issues? I ask because the only one I'm tracking allows unauthenticated playback, but only if they know the path to the file on the machine which is very easy to change from default.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 140 points 1 week ago (39 children)

    Also I use Jellyfin btw.

    Oh god, its the new Arch isn't it...

  • source
  • hideshow 39 child comments
  • load more comments (36 replies)
    [–] 45 points 1 week ago (2 children)

    Sure explains why Plex was so cagey and uninformative when they emailed everyone to update their servers a couple months back. Not so much as a CVE report or change set.

    A vulnerability? No…. 4 of them. And they stack.

  • source
  • hideshow 2 child comments
  • [–] 25 points 1 week ago (3 children)

    As someone who has nearly all internet facing software auto update with watchtower nightly my cortisol is so low

  • source
  • hideshow 3 child comments
  • [–] 4 points 6 days ago (2 children)

    You mean watchtower by containrrr? That repo seems archived.

    Also, if you don't mind me asking, how does that even work? There is a far from zero chance of potentially breaking changes on any given update, so with auto-updates, do you just accept that something might suddenly stop working, or do you just get notifications that a new version is available and update manually?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 6 days ago*

    If it breaks I either fix it (often it's just an issue where the new version needs extra config added), or roll back to a backup and pin the old version temporarily if it really went wrong and I can't recover otherwise.

    Backups run early AM before any auto updates start, and no one is using services and changing data then, so nothing should really ever be lost by rolling back.

  • source
  • parent
  • [–] 1 point 6 days ago

    I use one of the maintained forks of watchtower.

    I use it to auto update within stable versions for things that are reputable enough to not make breaking changes, so nginx, apache, wireguard, traefik, etc. In over 10 years of running Plex I don't think I've experienced a breaking update in the last 5-7 years at least, so I consider it safe enough. Any other software like Immich that I'm not sure if that's safe, I keep it behind a vpn and update manually. But for things as big as nginx especially I feel very safe letting it auto update within a major version.

  • source
  • parent
  • [–] 15 points 1 week ago (1 child)

    If you want to expose plex to the open Internet (not a VPN) Don't open the plex port to the internet. Turn off the "remote access" setting and run it behind a reverse proxy instead.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    load more comments
    view more: next ›