• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting Networking & Access Error when reverse proxy with Caddy.

    Pages (2): 1 2 Next »

     
    • 0 Vote(s) - 0 Average

    Error when reverse proxy with Caddy.

    Http2: stream closed and H3_REQUEST_CANCELLED
    chilledhobbit
    Offline

    Junior Member

    Posts: 7
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #1
    2025-02-17, 08:21 PM (This post was last modified: 2025-02-17, 08:31 PM by chilledhobbit. Edited 1 time in total.)
    Hi!

    I have already asked the same question on Caddy's forum, so I just link the thread over here. I hope someone here have a clue.

    https://caddy.community/t/http2-stream-c...lled/29955
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2025-02-17, 10:30 PM
    If LAN client's don't need direct access to Jellyfin (not through reverse proxy) you should remove the port publishing for port 8096. Assuming that Caddy and Jellyfin are on the same bridge network, port publishing is not needed. This would reduce the number of times traffic needs to jump between the host and bridge network stacks.

    Can you share the current state of your caddy and Jellyfin docker compose and the caddyfile?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    chilledhobbit
    Offline

    Junior Member

    Posts: 7
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #3
    2025-02-17, 11:43 PM
    Yeah I know, but I'm temporarily using it without reverse proxy.

    Code:
    version: "3"
    services:
      jellyfin:
        container_name: jellyfin
        image: jellyfin/jellyfin:latest
        volumes:
          - ./data/config:/config
          - ./data/cache:/cache
          - /mnt/data:/data
        devices:
          - /dev/dri/renderD128:/dev/dri/renderD128
          - /dev/dri/card0:/dev/dri/card0
        ports:
          - 8096:8096
        restart: unless-stopped
        user: 1003:1003
        group_add:
          - "44"
          - "109"

    Code:
    version: "3.7"
    services:
      caddy:
        container_name: caddy
        # image: caddy:latest
        build: .
        restart: unless-stopped
        ports:
          - 80:80
          - 443:443
          - 443:443/udp
        volumes:
          - ./data/Caddyfile:/etc/caddy/Caddyfile
          - ./data/data:/data
          - ./data/config:/config
        networks:
          - jellyfin_default

    networks:
      jellyfin_default:
        external: true

    Code:
    jellyfin.domain.tld

    reverse_proxy jellyfin:8096
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2025-02-18, 02:02 PM
    For the caddyfile, can you try using the LAN IP of the host instead of "jellyfin"? If you removed the port publishing you'd use the container's bridge IP instead.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    chilledhobbit
    Offline

    Junior Member

    Posts: 7
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #5
    2025-02-18, 03:28 PM
    I have actually already tested the LAN IP for the host, but I still get the error.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2025-02-18, 03:41 PM
    Have you made any changes to caddy? Besides disabling http3? Is http 1.1 still enabled for web sockets?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    chilledhobbit
    Offline

    Junior Member

    Posts: 7
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #7
    2025-02-18, 05:57 PM
    I have tried disabling http3 and http2. I haven't done anything with http1.1.

    From what I understand, web sockets are supposed to be handled automatically. So I haven't tried anything specific there.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #8
    2025-02-18, 06:07 PM
    I just noticed in your caddy docker compose that you aren't pulling an image, you are building something. What are you building and where was it sourced from? Are you running some development branch from Caddy's git or something?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    chilledhobbit
    Offline

    Junior Member

    Posts: 7
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #9
    2025-02-18, 07:25 PM
    I'm building only to get cloudflare dns challenge. So it's from original source.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #10
    2025-02-18, 07:34 PM
    I'm assuming you are building from a released version and not from the master branch/dev branch, correct?

    Are you behind a CGNAT?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Pages (2): 1 2 Next »

    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode