No awards are needed, just wanted to share my excitement that while my Jellyfin server still keeps loosing my entire library every 24 hours at least now it has a domain and ssl cert!

That is all. Happy Friday everyone

    • chaospatterns@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      9 hours ago

      Right. Zero trust means at the very least you need to add AuthN and AuthZ to every endpoint with no exceptions for internal IP addresses.

  • Onomatopoeia@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    12
    ·
    14 hours ago

    Lol.

    Still got the library issue, eh? Gonna have to just turn off services/apps/processes until you find the culprit.

    • 🔰Hurling⚜️Durling🔱@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      4
      ·
      13 hours ago

      lol, yeah. Gitea is next on the list, but I don’t have much more I’m afraid, Immich and Nextcloud are critical apps for me, so if it isn’t gitea or minecraft, then I might just setup a new server out of an old laptop to be my Jellyfin server and migrate my library there.

          • gdog05@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            11 hours ago

            Do you have the media cleanup plugin installed for Jellyfin? I wonder if you change the PUID and/or GUID if you couldn’t make sure Jellyfin wasn’t the source of the deletion.

              • gdog05@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                9 hours ago

                I would think the Jellyfin logs would say if it deleted something. But I have to say, I cannot fully understand GUID and PUID in all cases. But you can try to subtract 1 digit from PUID (100 to 99) and then try to delete a show or movie within Jellyfin’s interface. If it won’t do it, then you’ve got the permissions at least where it can’t delete things. It is possible to not view things as well, so it might take some research or trial and error and make sure you write down where it is now. But, it will remove one factor at least.

      • Onomatopoeia@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        2
        ·
        13 hours ago

        Can you spin up a VM or a docker image?

        I’ve done this when services misbehave, and just migrate the DB over (Syncthing in particular).

  • Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    4
    ·
    13 hours ago

    You didn’t expose it to the internet right?

    If you want remote access setup client certs

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        You really shouldn’t expose anything directly to the internet. It is a security problem waiting to happen. (Assuming it hasn’t already)

        This is how giant botnets form.

      • mic_check_one_two@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        6
        ·
        edit-2
        10 hours ago

        There are a few security issues with it, but all of the worst known issues require a valid login token. So an attacker would already need to have valid login credentials before they could actually do anything bad. Things like being able to stream video without authentication (but it requires already having a list of the stored media on the server, which means you have been logged in before). Or being able to change other users’ settings (but it requires already being logged in to a valid user).

        Basically, make sure you use good passwords, and actually trust any other users to do the same.

        • Dhs92@piefed.social
          link
          fedilink
          English
          arrow-up
          2
          ·
          3 hours ago

          The bug you mentioned actually just requires the attacker knows your local media paths to generate the hash. The issue is that most people use trash guides to setup *arr which means they probably have the same paths for everything

      • tux7350@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        2
        ·
        10 hours ago

        Ya got three options.

        Option A is to create your own certificate that is self-signed. You will then have to load the certificate into any client you want to use. Easier than people realize, just a couple terminal commands. Give this a go if you want to learn how they work.

        Option B is to generate a certificate with Let’s Encrypt via an application like certbot. I suggest you use a DNS challenge to create a wildcard certificate.

        Option C is to buy a certificate from your DNS provider aka something like cloudflare.

        IMO the best is Option B. Takes a bit to figure it out but its free and rotates automatically which I like.

        I like helping and fixing stuff, if you’d like to know anything just ask :D

        • Possibly linux@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 hours ago

          That is for server side certs not client side. I’m talking about Mutual TLS.

          Setting up https is not going to stop bots. All it does is prevent man in the middle attacks. You want to limit who and what can access Jellyfin so that you don’t end up being a victim of an automated exploit.

        • RunningInRVA@lemmy.world
          link
          fedilink
          English
          arrow-up
          7
          arrow-down
          1
          ·
          10 hours ago

          None of these are client certificates btw. These are just ways to have your server use TLS encryption with any client that connects but it offers no authorization. If you want authorization with client certificates you need to implement mTLS (Mutual TLS).