• 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 failed to bind port

     
    • 0 Vote(s) - 0 Average

    failed to bind port

    "curl: (7) Failed to connect to localhost port 8096 after 0 ms: Couldn't connect to server"
    primordialrage
    Offline

    Junior Member

    Posts: 1
    Threads: 1
    Joined: 2025 Jul
    Reputation: 0
    Country:United States
    #1
    2025-07-12, 06:54 AM (This post was last modified: 2025-07-12, 06:58 AM by primordialrage. Edited 2 times in total.)
    Greetings 

    I wanted to reach out to the community and see if anyone has had this issue, if not maybe if there is any information on how I can dig deeper in finding the root cause of this issue, or if there is any additional data or information needed

    ############
    Problem statement
    ############


    In portainer I changed the docker compose stack in order to bind some more media directories, and when I ran the compose it generated the following:
      "curl: (7) Failed to connect to localhost port 8096 after 0 ms: Couldn't connect to server"

    ########
    Logs
    ########


    In non working scenario Jellyfin gets stuck at this phase

    [06:15:06] [INF] [1] Main: Jellyfin version: 10.10.7
    [06:15:06] [INF] [1] Main: Environment Variables: ["[JELLYFIN_WEB_DIR, /jellyfin/jellyfin-web]", "[JELLYFIN_DATA_DIR, /config]", "[JELLYFIN_LOG_DIR, /config/log]", "[JELLYFIN_CONFIG_DIR, /config/config]", "[JELLYFIN_CACHE_DIR, /cache]", "[JELLYFIN_FFMPEG, /usr/lib/jellyfin-ffmpeg/ffmpeg]"]
    [06:15:06] [INF] [1] Main: Arguments: ["/jellyfin/jellyfin.dll"]
    [06:15:06] [INF] [1] Main: Operating system: Debian GNU/Linux 12 (bookworm)
    [06:15:06] [INF] [1] Main: Architecture: X64
    [06:15:06] [INF] [1] Main: 64-Bit Process: True
    [06:15:06] [INF] [1] Main: User Interactive: True
    [06:15:06] [INF] [1] Main: Processor count: 20
    [06:15:06] [INF] [1] Main: Program data path: /config
    [06:15:06] [INF] [1] Main: Log directory path: /config/log
    [06:15:06] [INF] [1] Main: Config directory path: /config/config
    [06:15:06] [INF] [1] Main: Cache path: /cache
    [06:15:06] [INF] [1] Main: Temp directory path: /tmp/jellyfin
    [06:15:06] [INF] [1] Main: Web resources path: /jellyfin/jellyfin-web
    [06:15:06] [INF] [1] Main: Application directory: /jellyfin/
    [06:15:06] [INF] [1] Emby.Server.Implementations.AppBase.BaseConfigurationManager: Setting cache path: /cache
    [06:15:06] [INF] [1] Emby.Server.Implementations.ApplicationHost: Loading assemblies
    [06:15:06] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Defined LAN subnets: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
    [06:15:06] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Defined LAN exclusions: []
    [06:15:06] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Used LAN subnets: ["127.0.0.1/8", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]
    [06:15:06] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Filtered interface addresses: ["127.0.0.1", "172.17.0.3"]
    [06:15:06] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Bind Addresses ["0.0.0.0"]
    [06:15:06] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Remote IP filter is Allowlist
    [06:15:06] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Filtered subnets: []

    #########
    Workaround
    #########

    completely remove all data/folders associated with current jellyfin and then rebuild jellyfin with new folders/data (not able to use previous config/data)

    this has happened 3 times and in one instance I also had to rename the new config and cache folder to ncache and nconfig (see compose below) and make the appropriate changes in the docker compose.

    I also made a copy of the compose onto the device and ran it to rule out issue with portainer but port binding issue remained

    I can recreate the issue by trying to run new instance of jellyfin with old files

    ########
    Device info
    ########


    MINISFORUM UN1290 
    12th Gen Core i9-12900HK(14C/20T) 
    32G RAM

    portainer ce 2.27.9

    jellyfin 10.10.7

    Ubuntu 24.04.2 LTS

    ##########
    Docker-Compose
    ##########


    services:
      jellyfin:
        image: jellyfin/jellyfin
        container_name: jellyfin
        network_mode: 'bridge'
        ports:
          - 8096:8096
        volumes:
          - /media/nvme1/jellyfin/nconfigConfused-faceconfig
          - /media/nvme1/jellyfin/ncacheConfused-facecache
          - type: bind
            source: /media/jf_nvme/media/anime
            target: /anime
          - type: bind
            source: /media/nvme1/anime
            target: /anime
          - type: bind
            source: /media/8tbHD/mnt
            target: /tvShow
        restart: 'unless-stopped'
    « Next Oldest | Next Newest »

    Users browsing this thread: 2 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