• Saik0English
      0•1 day ago

      Neither helps because jellyfin doesn’t work with auth in front of it. https://github.com/jellyfin/jellyfin/issues/13751

      And any auth mechanism breaks EVERY app even if you implement one that doesn’t break the web UI. (short of VPN or other similar type of auth’d tunneling).

      • ShimitarEnglish
        0•21 hours ago

        This is misinformation.

        I run my jellyfin behind reverse proxy and use SSO pretty well. There is a OIDC plugin for jellyfin that just works with your preferred SSO.

        Indeed Plex is easier to use, and manage all that for you, but this is self hosted community after all, there is smart people capable of running a reverse proxy and a proper SSO.

        For the others, Plex indeed is forth paying for (?).

      • @catloaf@lemm.eeEnglish
        0•1 day ago

        Fortunately, jellyfin loads fine behind an nginx proxy using basic auth.

        Sounds like it works fine in the scenario I was discussing.

        • Saik0English
          0•1 day ago

          Ah yes, single cherry picked sentence… Care to read the very next line? Where “unfortunately, […]”… Is that “shit doesn’t load right?” Weird.

          Do you know of any apps that support basic auth input for jellyfin? No… Weird? What did I say again?

          Oh right, I can just scroll up and read it.

          And any auth mechanism breaks EVERY app even if you implement one that doesn’t break the web UI.

          • @catloaf@lemm.eeEnglish
            0•1 day ago

            I just tested and was able to get to the login page with an nginx proxy in front of jellyfin. A login attempt causes nginx to throw an error, but jellyfin itself seems fine. If I disable http basic auth, I’m able to log in and play video. This looks like an nginx configuration issue, and if I cared enough to actually get it working I’m sure it would.

            • Saik0English
              0•1 day ago

              Try logging in.

              This is all you’ll see. Even if you setup a “guest” account with NO password… it’s all you’ll see. This is not a Nginx issue.

              Edit:

              The error appears in Jellyfins toast mechanism… so you know it’s not nginx.

              Edit2: oh and don’t forget to downvote this comment too. I see you :)

              Edit3: actually I just realized that you think THIS is nginx’s fault…

              It is, but it isn’t… It requires the wss target on the server to handle it.

              Jellyfin doesn’t do this. Nginx is passing it properly.