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!
Windows can run docker, so there’s versions of most things that will run on windows.
JellyFin has a native windows version.
Yes, but not everything does. But luckily, Docker exists on Windows. So anything that runs on Docker can be run on Windows.
Given, Docker’s implementation on Windows is… Uhh… Not GreatTM. Because it’s basically using WSL to trick Windows into supporting a Linux file system. So it has some quirks. But it does technically work.
No sane person runs docker on windows. They will run wsl or a Linux Hyper-V vm to do docker.
Time to setup an arr stack.
And (jelly)seer !
How do you like that?
Thanks, I hate it.
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.
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.
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.
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
netplwizautologon. 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.
I know this is probably “the usual” for everyone here, but I’m genuinely excited that I managed to get it all running smoothly.
Heh! Don’t let anyone dampen your enthusiasm. It feels great when I am toiling away at something and finally all the pieces click together. I might have to walk away a few times and put the project on hold, but I keep whacking away at it. When it does work, it’s always a childish joy that comes over me and always gets a fist-pump.
What equipment are you running that Windows Server on?
Right now its a Thinkpad T480 with 64G ram and 1tb ssd. If it turns out we use Jellyfin enough I plan to get something more powerful for it.
Nice! Rock on with yo’ bad self.
I’m always going to say Windows is too heavy to be placed in a server environment but congrats nonetheless.
Windows server
too heavy to be placed in a server environment
wasn’t designed for itIt’s not that bad. A lot of our servers at work use Windows. It certainly took some getting used to as someone who has been using Linux on all their devices, but it does work.
How did you handle the reverse proxy in Windows for remote access?
I didn’t. I don’t need remote access. We don’t watch TV outside the house.









