Comment on New Jellyfin Server/Web release: 10.10.7

renegadespork@lemmy.jelliefrontier.net ⁨1⁩ ⁨year⁩ ago

• 486@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Thanks for pointing this out! I probably would have missed this, since I didn’t expect such a change for a patch release.

  Their documentation mentions:

  For jellyfin to know which reverse proxy is trusted, the IP, Hostname or Subnet has to be set in the Known Proxies (under Admin Dashboard -> Networking) setting.

  Does this really mean, that the only way to configure this is through the web UI? This is kind of a problem when deploying it, since without the reverse proxy I can’t reach the Jellyfin server. Is there no way of doing this outside the web UI, via a config file or something?

  source

  • Lem453@lemmy.ca ⁨11⁩ ⁨months⁩ ago

    If I in traefik and jellyfin in docker, so I add the docker IP of traefik as the trusted proxy?

    source

    • klopstock@feddit.org ⁨11⁩ ⁨months⁩ ago

      I think you can use the container name if both containers are in the same docker network

      source
    • 486@lemmy.world ⁨11⁩ ⁨months⁩ ago

      I don’t know your exact setup, but you should add the IP that Jellyfin sees when the reverse proxy makes a request. That probably comes from the IP of your Traefik docker container.

      source
  • jagged_circle@feddit.nl ⁨1⁩ ⁨year⁩ ago

    Yeah the lack of info in the docs on how to configure jellyfin in the CLI is pathetic

    source
• slazer2au@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Do you not normally read patch notes before patching?

  source

  • kata1yst@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    Fuck no, ain’t nobody got time for that! My self hosted stack has 40+ services. I lock them to minor releases (where semvers are used), deploy blind with automation, and fire alerts when breakages occur, which is thankfully rarely.

    What you’re suggesting works for small, very carefully curated environments. I grew past that years ago and doubly so when I had kids.

    source

    • slazer2au@lemmy.world ⁨1⁩ ⁨year⁩ ago

      40? Kinda curious what you are running now.

      source

      • kata1yst@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

        The general list:

        1. Immich
        2. Jellyfin
        3. Plex (deprecated but kept around for my plexpass using friends)
        4. Internet Radio (custom container)
        5. PBS kids downloader (custom container)
        6. Lidarr
        7. Sonarr
        8. Mylar
        9. Radar
        10. Prowlarr
        11. Open-Webui
        12. QBittorrent
        13. Sabnzbd
        14. Navidrome
        15. Synapse
        16. Element
        17. Forgejo
        18. Tdarr
        19. Calibre
        20. Calibre Web
        21. Tautulli
        22. Bazarr
        23. Syncthing
        24. LazyLibrarian
        25. Linkwarden
        26. Mealie
        27. GlueTun
        28. Kopia
        29. Home Assistant
        30. Music Assistant
        31. Blocky
        32. FoundryVTT
        33. Wireguard
        34. ArchiveTeam Warrior
        35. Traefik
        36. Docspell
        37. Birdcage (though I’m slowly replacing this with my own bird sound server)
        38. Frigate
        39. FreshRSS
        40. Ntfy
        41. Samba

        With all the supporting services:

        Server:
         Containers: 76
          Running: 74
          Paused: 0
          Stopped: 2
         Images: 92
        

        source

        • -> View More Comments
• sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

  It’s odd to throw that into a patch release. I guess we’ll find out if I did it correctly.

  source

  • jonne@infosec.pub ⁨1⁩ ⁨year⁩ ago

    I mean, it’s patching a security issue caused by trusting headers it shouldn’t, so I don’t think they should wait for a big number release.

    source

    • sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      Why wait? Just release it as a big number release. The version number doesn’t define the size or cadence of a release, it just says whether there’s a breaking change.

      source

      • mac@lemm.ee ⁨1⁩ ⁨year⁩ ago

        At least in my org we use semantic versioning ( Major.Minor.patch) where patch must either be a new feature, a fix, or something that is backwards compatible

        source

        • -> View More Comments
  • N0x0n@lemmy.ml ⁨1⁩ ⁨year⁩ ago

    I mean, where else should they show that warning? It’s also posted in the forum. They also edited the documentation page.

    Maybe you’re more into mailing list or the like? I’m genuine curious on what and how you expected getting this kind of information.

    source

    • fitgse@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

      I expect in a patch release that nothing has changed and I can blindly update getting minor bug fixes and security fixes. In a minor release I expect to review the changes for configuration changes or any minor UI changes. For a major release I expect to read docs on how to upgrade and prepare backups and downtime.

      source

      • N0x0n@lemmy.ml ⁨1⁩ ⁨year⁩ ago

        Ohhh thanks for the clarification ! As you guest I’m not into dev/programming so I wasn’t aware of this kind of detail !

        Thank you :)

        source

        • -> View More Comments
      • sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

        Exactly. It has nothing to do with where they post it, but what their version numbers communicate. I should be able to blindly apply patch releases, and this breaks that.

        I’m even okay with a minor release here. It was never advertised to work that way so removing it technically isn’t a breaking change, but there is a known breakage here. I’m much more likely to read minor release notes than patch release notes, so I would likely see this warning if it was a minor release.

        source

        • -> View More Comments