jmot205

I'm seemingly having the same issue - did anyone figure this out?

Unfortunately forced update did not work, but I managed to get it working via the following workaround. I backed up the full appdata folder, then removed the image, reinstalled it from scratch via Capps, then stopped the container and switched the appdata folder back over. It's early doors, but so far so good.

I've not got an NVIDIA GPU so I haven't got either of those container variables added.

I tried pulling latest and a server reboot but still have the same error message. What repository setting did you get working? Currently have rolled back to binhex/arch-jellyfin:10.8.13-1-05 and it works again, but haven't found a forward version that gets me past the error.

It's set to binhex/arch-jellyfin

I recently updated to the new version of the docker (Main: Jellyfin version: 10.9.3) and am now receiving this error message: 2024-05-30 22:02:12,037 DEBG 'jellyfin' stdout output: [22:02:12] [ERR] [1] Main: The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/share/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 2024-05-30 22:02:12,044 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22965853606768 for <Subprocess at 22965852790208 with name jellyfin in state STARTING> (stdout)> 2024-05-30 22:02:12,044 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22965865757920 for <Subprocess at 22965852790208 with name jellyfin in state STARTING> (stderr)> 2024-05-30 22:02:12,045 WARN exited: jellyfin (exit status 1; not expected) 2024-05-30 22:02:12,045 DEBG received SIGCHLD indicating a child quit 2024-05-30 22:02:13,045 INFO gave up: jellyfin entered FATAL state, too many start retries too quickly Is there a specific action I need to perform to get it working again? If by web client it means hosting the page on IP:8096 that could be visited in a browser then this was working before the update, so I'm not certain I want to add that flag to the config.