2025-06-05, 12:35 AM
I've been running a Jellyfin server on a Windows PC for about 6 months, recently started testing the waters with Linux for this purpose.
The PC goes to sleep automatically after 30 min. When I start the Jellyfin client on an Android TV box, it wakes the Windows PC, connects to the server, remains awake as long as the client is being used, then resumes the 30 min sleep timer after the client disconnects. It's janky sometimes but it generally works well.
I was able to successfully set up the Jellyfin server on Linux installed on flash drive on the same PC, everything else worked, but I could not get the Android client to wake the PC. I always assumed the client was waking the windows PC with wake-on-lan magic packets, so I look up what the issue might be and find that Jellyfin never actually supported wake-on-lan?
So how does this actually work on a Windows PC if not using WOL? I tried setting the network adapter to wake on any unicast traffic but it just immediately wakes back up from random network traffic.
I'm hoping I can understand what's happening here so I can find a work-around.
The PC goes to sleep automatically after 30 min. When I start the Jellyfin client on an Android TV box, it wakes the Windows PC, connects to the server, remains awake as long as the client is being used, then resumes the 30 min sleep timer after the client disconnects. It's janky sometimes but it generally works well.
I was able to successfully set up the Jellyfin server on Linux installed on flash drive on the same PC, everything else worked, but I could not get the Android client to wake the PC. I always assumed the client was waking the windows PC with wake-on-lan magic packets, so I look up what the issue might be and find that Jellyfin never actually supported wake-on-lan?
So how does this actually work on a Windows PC if not using WOL? I tried setting the network adapter to wake on any unicast traffic but it just immediately wakes back up from random network traffic.
I'm hoping I can understand what's happening here so I can find a work-around.