Closed crazyduck closed 2 months ago
It appears there's something wrong with the web client in their new 10.9.10 package. If you start Jellyfin without the web client (/usr/bin/jellyfin --nowebclient
) it starts. No issues with 10.9.9
ls /usr/share/jellyfin/web
everything is there.
cat /etc/default/jellyfin
looks ok
Strange I created a new Jellyfin LXC (version 10.9.10), then downgraded to version 10.9.9
wget -q https://repo.jellyfin.org/files/server/ubuntu/stable/v10.9.9/amd64/jellyfin-server_10.9.9%2Bubu2204_amd64.deb
dpkg -i jellyfin-server_10.9.9+ubu2204_amd64.deb
then I performed an apt update && apt upgrade
which updated Jellyfin back to version 10.9.10, and it works now. This adds to my suspicion that their repository has a bad/incomplete 10.9.10 .deb
Thanks @tteck . I have confirmed that the workaround you provided works.
Hello,
Yesterday, i set up my first Proxmox server, and try the jellyfin script. According to it, everything went fine, but i couldn't reach the WebUI.
Doing the downgrade and update as ttek says, solve my issue tonight.
Thanks
worked for me also, thanks for quick response.
For this particular version, perhaps do above steps by script?
apt update && apt upgrade
Thanks, this worked for me too
I had the same issue yesterday when setting up a fresh Jellyfin LXC. The fix/workaround above did work for me, but I will add a twist.
Initially I installed the Jellyfin LXC using the script. I then also installed the File Browser script onto the same Jellyfin LXC. It also would not pull up the web UI for File Browser. After initially killing the Jellyfin LXC and rebuilding it, adding File Browser, ensuring my network connections were OK, did I come here and find the above fix.
After applying the Jellyfin fix, File Browser still did not work properly. The webUI was not accessible. I eventually had to remove it and then reinstall it with the script after the Jellyfin Fix, for it to finally work correctly.
I assume the issues are linked in some way.
Downgrading and then upgrading jellyfin didn't seem to work for me to resolve the web UI issue. The jellyfin server starts and I can access it from the android app, but the web UI is non-functional. I get this when I type the jellyfin command in the LXC.
[16:28:02] [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
Appreciate it's not an issue with this script, just wondered if anybody has the same problem, or any suggestions.
Fixed
Downgrading and then upgrading jellyfin didn't seem to work for me to resolve the web UI issue. The jellyfin server starts and I can access it from the android app, but the web UI is non-functional. I get this when I type the jellyfin command in the LXC.
[16:28:02] [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
Appreciate it's not an issue with this script, just wondered if anybody has the same problem, or any suggestions.
I am having the same issue. but this only happens after i changed the IP address from DHCP, strangely. what i meant is when first running the script the web gui works, then i shut off the lxc and change ip address, and then reboot and i can no longer access gui.
Please verify that you have read and understood the guidelines.
yes
A clear and concise description of the issue.
Yesterday Jellyfin installed fine with 10.9.9
I was playing around today with the LXC and did several reinstalls with the script.
Today an update to version 10.9.10 was released. Now Jellyfin wont start after fresh install, neither on recommended Ubuntu 22.04 nor on debian 12.
Journalctl throws:
What settings are you currently utilizing?
Advanced Settings
Which Linux distribution are you employing?
Debian 12
If relevant, including screenshots or a code block can be helpful in clarifying the issue.
Please provide detailed steps to reproduce the issue.
Just do a fresh reinstall with the script.