• 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.

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

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

        • @N0x0n@lemmy.mlEnglish
          0•24 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 :) !

          • Saik0English
            0•19 hours 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!