I’m in a weird situation, i have a dedicated mini pc for my Jellyfin server Here are the requirements for solutions

  • I cannot use an interface like a keyboard or mouse -I will not use linux for this particular machine -The device does have USB ports and a screen So to just have the jellyfin server start automatically, i would like to be able to hit the power button and have it boot into windows, thus automatically starting the jellyfin server and allowing me to do server restarts to fix issues.

Problem is the login screen, i can go as far as removing my password but it still requires user input to login. I need to bypass this but on the other hand i would not like to leave this giant vulnerability in my system. Is there any sort of way to get the best of both worlds? to have the PC be able to go from power button to jellyfin server started and still have some measure of security?

Thanks if anyone has any insight to my problem it would be wildly appreciated

  • @BananaTrifleViolin
    link
    English
    11
    edit-2
    1 month ago

    As people have said, you can add Jellyfin as a service to start with windows regardless of users being logged in.

    No one seems to have said how to do this.

    The easiest way is to use the NSSM open source tool - it stands for “Non Sucking Service Manager” and it gives a GUI route to create services, as well as some useful reliability and fall back functions.

    It can also be used from the command line if you prefer but regardless it’s probably the easiest way without faffing around with powershell or command line and in built windows tools (which do suck).

    Edit. The official website is NSSM.cc and it includes guidance on how to use it. There are also plenty of guides online if you search “how to create a windows service”.

    Edit2: the easiest way is to use the Jellyfin windows installer itself but the documentation is pretty vague on that and gives a warning about ffmpeg config. It should work but using NSSM will give you more direct control. I think the installer uses NSSM anyway.