Hey Hosters!

Just wanted to share that I got Jellyfin installed and set up on my Windows 2022 Server, and it’s working great! I didn’t even know there was a version for WIndows. How do you like that?

I know this is probably “the usual” for everyone here, but I’m genuinely excited that I managed to get it all running smoothly.

After getting the server up, I went through the basics (users/permissions, library paths, and making sure everything was reachable on the network) and it all just worked. The interface is super clean, playback is nice and responsive, and it feels like I’ve been missing out on this until now.

Huge thanks to the Jellyfin team and the community! This project is awesome!! If anyone is stuck, please don’t give up. keep poking at the configuration and it’ll pay off. Now I just need to spend some time organizing my libraries!

Happy Hosting!

  • JRaccoon@discuss.tchncs.deEnglish
    6·
    2 days ago

    Asking out of curiosity: is there a specific reason you’re running Windows on your server? I used to do the same on my home servers because that’s what we used to have at work, and I wanted to learn and test some stuff. But it was a difficult road, to put it mildly. Simple things, like getting Docker autostart on boot seemed almost impossible. At some point I just gave up and switched to Linux.

    • GatesMcBalmer@lemmy.worldOPEnglish
      1·
      9 hours ago

      I use Windows Server because that’s what I know. Though I am curious to learn other OSes when I have more time. I don’t use docker so that’s really not a problem for now.

    • mic_check_one_two@lemmy.dbzer0.comEnglish
      1·
      17 hours ago

      You have trouble getting Docker to auto-start on Windows? I thought that was the default behavior… Hell, even if it’s not, you can just add a Docker shortcut to the Startup folder.

      • JRaccoon@discuss.tchncs.deEnglish
        1·
        16 hours ago

        It works great when you log in as a user like you normally would on a Windows pc. But on a server you want it to run as a service, starting automatically in the background and/or being managed by the failover cluster without requiring a user to log in.

        The solution back then was to use netplwiz autologon. Obviously a hack and bad for security, but fine for a homelab. After googling it now, it looks like some other “solutions” are documented in the GitHub issue about this.