Jellyfin Forum
SOLVED: Jellyfin web client docker compose - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Jellyfin web client docker compose (/t-solved-jellyfin-web-client-docker-compose)

Jellyfin web client docker compose - Limos21 - 2024-08-13

Hi all,

I need some help with setting up a docker compose file for hosting jellyfin with the web client. I have already invested quite some time, searched the internet and the forum, but do not seem to find a solution.

The problem I am currently facing is that when I try to access my custom, local jellyfin endpoint on http://192.168.178.55:2008 where the web client is supposed to be, it is not available.
I followed the instruction from the official documentation to set up the web client: Web Client Configuration
The jellyfin server is up and running and idles, but I can not reach the web client interface on  http://192.168.178.55:2008 instead I am redirected to the web folder that I specified in the docker compose file ->  http://192.168.178.55:2008/web/

I also need to mention, the web folder is not empty. I copied the official jellyfin web client repository from jellyfin/jellyfin-web: Web Client for Jellyfin (github.com) in there.

My setup is the following:

Jellyfin-Version: 10.9.4
OS: Ubuntu Linux
Hosting: Docker (Compose)

This is the docker compose file that I have created and used:

Code:
version: "3.8"

services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    container_name: jellyfin
    restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    networks:
      - traefik-proxy
    ports:
      - 2008:8096 # HTTP traffic
#      - 8920:8920 # optional HTTPS traffic
      - 7359:7359/udp # optional service auto-discovery
      - 1900:1900/udp # optional service auto-discovery
    environment:
      TZ: Europe/Berlin
      JELLYFIN_CONFIG_DIR: /config
      JELLYFIN_CACHE_DIR: /cache
      JELLYFIN_LOG_DIR: /log
      JELLYFIN_WEB_DIR: /web
      JELLYFIN_DATA_DIR: /data
      JELLYFIN_HOSTWEBCLIENT: true
#      JELLYFIN_PublishedServerUrl=192.168.0.5  # optional and not needed
    user: 1000:1000 # user and group that owns the volumes
    group_add:
      - "993" # Change this to match your "render" host group id and remove this comment -> "getent group render | cut -d: -f3"
    volumes:
      - ./config:/config
      - ./cache:/cache
      - ./logs:/log
      - ./web:/web
      - /storage/jellyfin/data:/data
      - /storage/jellyfin/tvshows:/tvshows
      - /storage/jellyfin/movies:/movies
      - /storage/jellyfin/music:/music
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
    labels:
      # Watchtower
      - "com.centurylinklabs.watchtower.enable=true"
      # Traefik

networks:
  traefik-proxy:
    name: traefik-proxy
    external: true


I have also put the log in the appendix.

Thank you in advance for your help.

RE: Jellyfin web client docker compose - Limos21 - 2024-08-13

I have to comment also that the jellyfin version I initally stated is wrong, it is actually V10.9.9

RE: Jellyfin web client docker compose - TheDreadPirate - 2024-08-13

A couple of things you can try. You can have Jellyfin straight up listen on port 2008 instead of trying to map the inner/outer ports. You'd have to modify network.xml and restart the container.

Code:
<InternalHttpPort>8096</InternalHttpPort>

Also, since you are using bridge networking, perhaps switch to using "expose" instead of "ports".

My docker compose for reference.

Code:
services:
  jellyfin-testing:
    image: jellyfin/jellyfin:10.9.9
    container_name: jellyfin-testing
    user: 110:110
    group_add:
      - "993" # Intel render group
    networks:
      blackmoon:
        ipv4_address: 172.16.100.2
    expose:
      - 8096
    volumes:
      - ./jellyfin-stable-data/config:/config
      - ./jellyfin-stable-data/cache:/cache
      - /media/library:/media/library:ro
      - /media/storage2:/media/storage2
      - /media/ramdisk:/media/ramdisk
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
    restart: 'unless-stopped'

networks:
  blackmoon:
    ipam:
      driver: default
      config:
        - subnet: "172.16.100.0/24"


RE: Jellyfin web client docker compose - Limos21 - 2024-08-14

Hi again,

thank you for your response.
I need to clarify that there is no issue with mapping the port from the container to my custom host port because jellyfin is reachable on the custom port. The problem is that when accessing http://192.168.178.55:2008 the jellyfin logo immediately pops up and then the web client seems to stuck then. I am not forwarded or shown the server selection or login screen. Ist just the logo popping up, nothing else.

This is what I see in the browser:

   

RE: Jellyfin web client docker compose - TheDreadPirate - 2024-08-14

In your opening post you said 10.9.4, but your log says 10.9.9. If you upgraded recently, try clearing your browser cache or opening an incognito window. There were big changes in 10.9.9 that re-worked how Jellyfin caches browser data.

RE: Jellyfin web client docker compose - Limos21 - 2024-08-14

Hi again,

I cleared the browser cache and also opened an incognito window. It did not work out.
Here is also the "web" folder where I copied the src folder of the official web client github repository.
Is this the right folder structure, because I am unsure if that is causing the problem?
   

RE: Jellyfin web client docker compose - TheDreadPirate - 2024-08-14

Why did you manually copy jellyfin-web? The docker image comes with it. This may be the problem.

Comment out the volume for /web and the environment variable for /web in your compose and recreate the container to make sure that everything is reset.

Code:
sudo docker compose up -d jellyfin --force-recreate


RE: Jellyfin web client docker compose - Limos21 - 2024-08-14

Finally that solved everything Smiling-face !!!! Many thanks.