Jellyfin 10.9.1 about jellyfin-featured HOT 6 OPEN

this is currently getting updated, shouldnt be too long now the update to 10.9 broke... a lot of stuff.. however ive got 99% of it done now

the main issue is they changed from the known names to a random string set of names.. making it hard to do.. but not impossible

stay tuned i will close this issue when the update is pushed

from jellyfin-featured.

update it should work but the docker image may have changed the uuiid for the file please
change compose to the following and

jellyfin:
image: jellyfin/jellyfin:latest
container_name: jellyfin
restart: unless-stopped
networks:
- proxy
ports:
- "8096:8096"
volumes:
- $DOCKERDIR/jellyfin/config:/config
- $DOCKERDIR/jellyfin/cache:/cache
- $LIBRARY:/data/media
- $DOCKERDIR/jellyfin/webroot:/jellyfin/jellyfin-web/
devices:
- /dev/dri/renderD128:/dev/dri/renderD128:rw
- /dev/dri/card0:/dev/dri/card0:rw
environment:
PUID: $PUID
PGID: $PGID
TZ: $TZ

then spin it up using docker-compose up and simply backup the original one inside webroot (yes its new and right next to your custom html chunk file) folder (using cp oldfile oldfilename.orig obviously change the oldname to the one listed in ls | grep home-html) then use cp ../custom-html-chunk.js oldfilename (from within the webroot folder)

note some may need sudo may not it depends on the drive permissions

let me know how it goes also the new update needs the three new files make.sh featuredstyles.css featuredscripts.js (it is just better and loads faster and is less arghhh when trying to debug) in my defence i made this originally while drinking so its not too bad all things considered the updated version is sober

from jellyfin-featured.

Hi I followed your instructions but I got stuck. It doesn't allow me to inspect the container anymore after I created the folder "webroot" inside jellyfin and added the volume to my docker-compose.

[13:44:58] [INF] [1] Main: Jellyfin version: 10.9.1

[13:44:58] [INF] [1] Main: Environment Variables: ["[JELLYFIN_LOG_DIR, /config/log]", "[JELLYFIN_CONFIG_DIR, /config/config]", "[JELLYFIN_CACHE_DIR, /cache]", "[JELLYFIN_WEB_DIR, /jellyfin/jellyfin-web]", "[JELLYFIN_PublishedServerUrl, https://jellyfin.2ndwonder.nl]", "[JELLYFIN_DATA_DIR, /config]", "[JELLYFIN_FFMPEG, /usr/lib/jellyfin-ffmpeg/ffmpeg]"]

[13:44:58] [INF] [1] Main: Arguments: ["/jellyfin/jellyfin.dll", "--ffmpeg", "/usr/lib/jellyfin-ffmpeg/ffmpeg"]

[13:44:58] [INF] [1] Main: Operating system: Debian GNU/Linux 12 (bookworm)

[13:44:58] [INF] [1] Main: Architecture: X64

[13:44:58] [INF] [1] Main: 64-Bit Process: True

[13:44:58] [INF] [1] Main: User Interactive: True

[13:44:58] [INF] [1] Main: Processor count: 4

[13:44:58] [INF] [1] Main: Program data path: /config

[13:44:58] [INF] [1] Main: Log directory path: /config/log

[13:44:58] [INF] [1] Main: Config directory path: /config/config

[13:44:58] [INF] [1] Main: Cache path: /cache

[13:44:58] [INF] [1] Main: Web resources path: /jellyfin/jellyfin-web

[13:44:58] [INF] [1] Main: Application directory: /jellyfin/

[13:44:58] [ERR] [1] Main: The server is expected to host the web client, but the provided content directory is either invalid or empty: /jellyfin/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

If I wanna inspect the container it says,

Error response from daemon: Container 4cc8600e7c546a3b9af34c68613596d6f51ef9018556686fa3fec6e4e35cfbcb is restarting, wait until the container is running

But the container is already running

from jellyfin-featured.

I backed up my container in a .tar extension and copied my home.html.chunk.js file into /volume1/docker/jellyfin/webroot. after that I followed the commands below

cp home-html.8ce38bc7d6dc073656d4.chunk.js home-html.8ce38bc7d6dc073656d4.chunk.js.orig
cp /volume1/docker/jellyfin/webroot/custom-html-chunk.js home-html.8ce38bc7d6dc073656d4.chunk.js

but now my UI of jellyfin doesn't show

from jellyfin-featured.

Hi I followed your instructions but I got stuck. It doesn't allow me to inspect the container anymore after I created the folder "webroot" inside jellyfin and added the volume to my docker-compose.

[13:44:58] [INF] [1] Main: Jellyfin version: 10.9.1

[13:44:58] [INF] [1] Main: Environment Variables: ["[JELLYFIN_LOG_DIR, /config/log]", "[JELLYFIN_CONFIG_DIR, /config/config]", "[JELLYFIN_CACHE_DIR, /cache]", "[JELLYFIN_WEB_DIR, /jellyfin/jellyfin-web]", "[JELLYFIN_PublishedServerUrl, https://jellyfin.2ndwonder.nl]", "[JELLYFIN_DATA_DIR, /config]", "[JELLYFIN_FFMPEG, /usr/lib/jellyfin-ffmpeg/ffmpeg]"]

[13:44:58] [INF] [1] Main: Arguments: ["/jellyfin/jellyfin.dll", "--ffmpeg", "/usr/lib/jellyfin-ffmpeg/ffmpeg"]

[13:44:58] [INF] [1] Main: Operating system: Debian GNU/Linux 12 (bookworm)

[13:44:58] [INF] [1] Main: Architecture: X64

[13:44:58] [INF] [1] Main: 64-Bit Process: True

[13:44:58] [INF] [1] Main: User Interactive: True

[13:44:58] [INF] [1] Main: Processor count: 4

[13:44:58] [INF] [1] Main: Program data path: /config

[13:44:58] [INF] [1] Main: Log directory path: /config/log

[13:44:58] [INF] [1] Main: Config directory path: /config/config

[13:44:58] [INF] [1] Main: Cache path: /cache

[13:44:58] [INF] [1] Main: Web resources path: /jellyfin/jellyfin-web

[13:44:58] [INF] [1] Main: Application directory: /jellyfin/

[13:44:58] [ERR] [1] Main: The server is expected to host the web client, but the provided content directory is either invalid or empty: /jellyfin/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

If I wanna inspect the container it says,

Error response from daemon: Container 4cc8600e7c546a3b9af34c68613596d6f51ef9018556686fa3fec6e4e35cfbcb is restarting, wait until the container is running

But the container is already running

okay so i see the issue and let me explain it, when you add the volume before running the container it will not populate the folder, however if you run the container first without the volume mapped then have it "rebuild" with that volume added it should work as intended (from my tests anyway)

so remove the volume from the docker compose and run

sudo docker-compose down && sudo docker-compose up then close the process with ctrl+c (or kill it via sudo kill PID ) and then edit the docker-compose.yml to have the volume mapped for webroot.. then run sudo docker-compose up this should then have the files in the folder (assuming you didnt create webroot as a blank folder beforehand.. that is important

from jellyfin-featured.

Does not work for me :(

from jellyfin-featured.