Wiki > Jellyfin
Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support.
Connect to your slot through SSH.
Start Jellyfin briefly to create configuration files.
Wait for it to finish outputting information and then press Ctrl+C to shut it down.
Open the configuration file in nano
Make the following changes:
Save changes by pressing
Start Jellyfin in a screen session running in the background
screen -dmS Jellyfin /usr/bin/jellyfin
Make a file to be used for the script.
Edit the file and enter the text below.
nano -w ~/Jellyfin_restart.cron
#!/bin/bash if pgrep -fx "jellyfin" > /dev/null then echo "Jellyfin is running." else echo "Jellyfin is not running, starting Jellyfin" screen -dmS Jellyfin /usr/bin/jellyfin fi exit
Save the file with Ctrl+x and the "y" and Enter to accept overwriting.
Make the script executable.
chmod +x ~/Jellyfin_restart.cron
Open your crontab.
EDITOR=nano crontab -e
Enter the following text
@reboot /home/user/Jellyfin_restart.cron >/dev/null 2>&1 */5 * * * * /home/user/Jellyfin_restart.cron >/dev/null 2>&1
Save the crontab with Ctrl+x and the "y" and Enter to accept overwriting.
Your Jellyfin web interface will be accessible at http://server.whatbox.ca:46573 Jellyfin will run you through a setup wizard for creating a user and setting up your first libraries. You will not be able to navigate to your slot using the built-in filesystem navigator, so you will need to enter the full path to the directory you want to add to your library, for example /home/user/files
It is strongly recommended to setup authentication on your Jellyfin instance. You can do this in Jellyfin's web interface under the Settings > Users > Your user > Password category. You should not use your slot password here because the web interface does not use SSL. Click
Save to save the configuration.
You can attach to your Jellyfin screen session to monitor its output using
screen -r Jellyfin , and detach from it again by pressing
d and then
Jellyfin is much more prone to abusing available resources than Plex. You must limit the CPU threads that Jellyfin may use. We will terminate any instances of Jellyfin running that are using so much CPU as to impact other users on the server. These settings can be found in Settings > Transcoding > Transcoding thread count. Guidelines for plans and the threads they may use follows:
- Legacy: 1
- HDD: 4
- SSD: 4
Saveto save the configuration.