• Saik0@lemmy.saik0.com
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    15 hours 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.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      12 hours 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.

      • Saik0@lemmy.saik0.com
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        11 hours 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.

        Edit4:

        Thanks dad!

        • catloaf@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          12 hours ago

          No, I was getting a 401 directly from nginx. Where is that last screenshot from?

            • N0x0n@lemmy.ml
              link
              fedilink
              English
              arrow-up
              2
              ·
              6 hours ago

              There are solutions though… Yes, it’s not native and adds some little extra work but it’s already possible: https://docs.goauthentik.io/integrations/services/jellyfin/

              I haven’t tried it though, it’s on my todo list and saved bookmark, just though I would share :)

              An other solution would be to make a tiny wireguard server and make a VPN to your homeserver. Just put something like a bananaPi (or something else) into your grandparents house :) they won’t see any difference !

              A plus could be to even add your own dns+pihole onto their network and block some of those nasty ads :) !

              • Saik0@lemmy.saik0.com
                link
                fedilink
                English
                arrow-up
                1
                ·
                58 minutes ago

                There are solutions though…

                Solution for what? This thread is talking about basic auth breaking jellyfin.

                Adding an auth layer IN jellyfin will not fix the unauthed endpoints. We’re talking about adding an auth layer BEFORE jellyfin here.

                they won’t see any difference !

                They also won’t know how to use it… how to debug it when it inevitably goes down… etc.

                A plus could be to even add your own dns+pihole onto their network and block some of those nasty ads :) !

                Yay! more support!