I have installed the Jellyfin Server using the Baazar flatpak service and it installs JUellyfin Server for me.
The problem is, it doesn’t auto start when I log into Bazzite, what is the name of the actual service so that I can get it to start.
Usually it would be something systemctl –user start jellyfin.service
But I just can’t find the correct jellyfin bit to add after start
I don’t know the proper way to do it but can only describe how I would try the poor man’s way…
First look where the jellyfish service file is located.
flatpak info -l org.jellyfin.JellyfinServer
You will get something like this
`/var/lib/flatpak/app/org.jellyfin.JellyfinServer/x86_64/stable/224fe69fda556f7ce38525704d757c36295e6a1a710dc88f3e177152808e475f`
Then run
find /var/lib/flatpak/app/org.jellyfin.JellyfinServer/x86_64/stable/224fe69fda556f7ce38525704d757c36295e6a1a710dc88f3e177152808e475f -name ‘*.service’
You should see a file named jellyfin.service Copy this file to ~/.config/systemd/user/ directory (create the directory first if not existing)
Then run systemctl —user start --enable jellyfin.service
Thanks for this.
Also found this, that also works. I have literally just tested it and restarted my machine.
First I did - sudo nano /etc/systemd/system/jellyfin.service
Pasted this into the new file - Obviously putting in my user name
[Unit]
Description=Jellyfin Media Server
After=network.target
[Service]
ExecStart=/usr/bin/flatpak run org.jellyfin.JellyfinServer
Restart=always
User=your_username
[Install]
WantedBy=multi-user.target
Then - sudo systemctl daemon-reload
Then - sudo systemctl enable jellyfin.service
Then - sudo systemctl start jellyfin.service
Could sudo systemctl –user start jellyfin.service be used instead of using the two start and enable lines, so basically typing one line instead of two?
I am assuming that the file you suggested to copy across is basically what I pasted into the file that I created… In fact, I will go and have a look and see if I can read the file.
Yes, you can put it below /etc
The difference is that when having jellyfin.service in /etc/systemd/system then it gets started after boot.
If you have it in ~/.config/systemd/user then the service gets started only after you have logged in.
Regarding your other question
sudo systemctl enable jellyfin.service
sudo systemctl start jellyfin.service
can be abbreviated
sudo systemctl start --enable jellyfin.service
You use --user only when the service file is somewhere in ~/.config/systemd/user
So you would still need to run both lines after doing the daemon-reload bit?
You couldn’t just use sudo systemctl –user start jellyfin.service to start and enable the xxx.service then?
Sorry if, I am sounding a bit thick, just want to get things clear in my head 
As you have things in /etc/systemd/… you don’t use --user
As said above you can abbreviate the start and enable command into one command by user --enable . But this is a one time action anyway so it is only a matter of taste which way to go.
start alone just starts it. enable tells to (re-)start it according to what is said in the service file
Well, thank you very much.
All I need to do now, is work out how to access my server from outside of my home 
Yes, that’s a different game. Opening port(s), firewall…
Well, I tried
sudo firewall-cmd --permanent --zone=public --add-port=8096/tcp
And then did port forwarding on my router for port 8096, but I just can’t see my server at all.
Works fine, if I connect my mobile to the server over my local network.
If you want to discuss this I would recommend to open a new thread. Is always better if in future people will be searching for something
But nevertheless one remark: The router must open the incoming port and then the router must forward the incoming port to the local destination. Something like 192…:8096
Well, it turns out, I didn’t sort out my port forwarding as well as I thought
It’‘s all good now, Jellyfin is working as it should now.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.