SOLVED: Jellyfin service not starting

[umunas]

@alanf @dmf

There is a known issue for fresh installs where the apt package isn't resetting permissions on key directories.  The work around is to manually set permissions.

Code:

sudo chown -R jellyfin: /var/lib/jellyfin /etc/jellyfin /var/cache/jellyfin /usr/share/jellyfin
sudo systemctl restart jellyfin

A hotfix release is being worked to resolve this.

Still not working for me:

Code:

Aug 28 20:15:11 jellyfin systemd[1]: jellyfin.service: Main process exited, code=killed, status=6/ABRT
Aug 28 20:15:11 jellyfin systemd[1]: jellyfin.service: Failed with result 'signal'.
Aug 28 20:15:11 jellyfin systemd[1]: jellyfin.service: Scheduled restart job, restart counter is at 5.
Aug 28 20:15:11 jellyfin systemd[1]: Stopped jellyfin.service - Jellyfin Media Server.
Aug 28 20:15:11 jellyfin systemd[1]: jellyfin.service: Start request repeated too quickly.
Aug 28 20:15:11 jellyfin systemd[1]: jellyfin.service: Failed with result 'signal'.
Aug 28 20:15:11 jellyfin systemd[1]: Failed to start jellyfin.service - Jellyfin Media Server.

Code:

20:24:08] [ERR] [1] Main: The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/lib/jellyfin/bin/jellyfin-web. If you do not want to host the web client with the server, you may set the '--nowebclient' command line flag, or set'hostwebclient=false' in your config settings

I am playing with Jellyfin in Proxmox LXCs (without Docker!!!). It is a bit of a journey. Jellyfin installs just stopped working from the moment of installation due to 'jellyfin-web' errors. This started last weekend. I always used 'extrepo' previously. Today I tried 'bash install-debuntu.sh' and it worked! Until it didn't... But at least it took few reboots until it broke...