Jellyfin installation error

[Joulinar]

did you reinstalled Jellyfin afterwards? Usually /lib/systemd/system/jellyfin.service is the correct service file.

[Ryan]

Yes, I uninstalled Jellyfin, deleted those two files, and reinstalled.

[MichaIng]

Not sure where the /etc/systemd/system/jellyfin.service is coming from, but it’s overriding the original one and tries to start a non-existing script. Please try to rename or remove it:

rm /etc/systemd/system/jellyfin.service
systemctl daemon-reload
mv /mnt/dietpi_userdata/jellyfin{,_old}
dietpi-software reinstall 178
systemctl stop jellyfin
cp -a /mnt/dietpi_userdata/jellyfin{_old/.,/}
rm -R /mnt/dietpi_userdata/jellyfin_old
systemctl restart jellyfin

A little nasty workaround since some configuration parts during install are skipped if /mnt/dietpi_userdata/jellyfin exists already.

[MichaIng]

Ah okay, I posted some conservative commands above which would have preserved possibly existing data, but ignore them if an uninstall was okay.

I didn’t see the last posts, damn mobile connection .

[Ryan]

Yes, I think the pre-existing service file was from when I tried to install Jellyfin manually before I realized that dietpi already had it in the dietpi-software. I tried uninstall the first version, but I guess I missed some files and that is what caused the conflicting service file. Simply deleting it because it was redundant solved the problem. Thanks for your help

[MichaIng]

Okay great that it works now.

[rak007]

I apologize for bumping up an old post. I am facing this exact issue with my Dietpi installation. It is supposedly latest v9.4.2 and I am trying to install Jellyfin using dietpi-software.

I am unable to figure out how to fix this. I did what all is mentioned here like deleting service file and everything. Nothing is working.

Can anyone help?

[FidgetStick]

snap. fresh install of dietpi failed with same error on native pc.

[Jappe]

I’ve got the same message during isntallation on my RPi 3, but this is just for adjusting the default port from 8096 to 8097 (since 8096 is used for something else on dietpi), but jellyfin is actually running on port 8096 just fine, at least in my case.

But dunno why the intsalller fails to create that file.
Also editing that file to user another port does not work on my testsystem. Did jellyfin chenged something regarding the configs?

[Joulinar]

there will be some changes on the upcoming DietPi release v9.5 · MichaIng/DietPi@5e01b39 · GitHub

[MichaIng]

As a workaround, you can pre-create the missing config file:

cat << '_EOF_' > /etc/jellyfin/network.xml
<NetworkConfiguration>
  <InternalHttpPort>8097</InternalHttpPort>
  <PublicHttpPort>8097</PublicHttpPort>
</NetworkConfiguration>
_EOF_

This is also what we do after next DietPi version.

EDIT: This should work also after the installation. The only thing missing is really this config, only meant to change the HTTP port from 8086 to 8097 (solving a port conflict with Emby).