Jellyfin Forum
SOLVED: Problems with Caddy - 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: Problems with Caddy (/t-solved-problems-with-caddy)

Pages: 1 2


RE: Problems with Caddy - TheDreadPirate - 2025-04-16

A couple of things.

1) You can remove the extra_hosts section. That is only required when using host networking so that health checks work.
2) Give jellyfin a static IP and explicitly set the hostname. And I recommend using jellyfin bridge IP for the caddyfile.

Code:
jellyfin-prod:
    image: ghcr.io/jellyfin/jellyfin:10.10.7
    container_name: jellyfin-prod
    hostname: jellyfin
    user: ${MEDIAUSER}:${MEDIAUSER}
    group_add:
      - '${RENDER}' # Intel render group
    networks:
      blackmoon:
        ipv4_address: 172.16.100.10
    expose:
      - 8096
    volumes:
      - ./jellyfin-prod-data/config:/config
      - ./jellyfin-prod-data/cache:/cache
      - /media/ramdisk:/media/ramdisk
      - /media/library:/media/library:ro
      - /media/library/liveTV:/media/library/liveTV:rw
    devices:
      - /dev/dri:/dev/dri
    environment:
      - TZ=${TZ}
    restart: unless-stopped

Ignore the "expose" section. My reverse proxy runs directly on the host and expose is required to make it accessible outside of the bridge network, but without port publishing on the host.


RE: Problems with Caddy - MassiveA - 2025-04-16

Ok thank you, I will give this a try.


RE: Problems with Caddy - MassiveA - 2025-04-17

Hi, so I've implemented the changes you recomended, I also went in the networking settings in Jellying and assigned to the Known Proxys section the static IP I assigned to Caddy in the compose. I tried briefly streaming something remotely and I think the situation is improved a lot, to the point where I would think it is probably solved. Caddy is still giving the http2 stream closed warn. But honestly if it was like this from the beggining I wouldn't have checked. Here is the new configuration.

https://pastebin.com/LeUkWkDP


RE: Problems with Caddy - TheDreadPirate - 2025-04-17

Someone else posted that Caddy HTTP2 warning a couple weeks ago and, AFAICT, it was unclear if this is an actual problem or not as it didn't cause any noticeable problems.

I couldn't find a clear answer on Caddy's forum either.


RE: Problems with Caddy - MassiveA - 2025-04-17

Well, thank you very much, I'm marking this as solved,