• 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 General Questions newbie installing Jellyfin in TrueNAS - whats port bind mode?

     
    • 0 Vote(s) - 0 Average

    newbie installing Jellyfin in TrueNAS - whats port bind mode?

    ELI5 port bind mode options: publish on host vs expose port for intercontainervs none
    galoor
    Offline

    Junior Member

    Posts: 3
    Threads: 2
    Joined: 2025 Jun
    Reputation: 0
    #1
    2025-08-29, 10:48 AM
    so newbie trying to set up my own LOCAL only Jellyfin server and was following this video tutorial

    and was wondering what are options under Port Bind Mode in Network Configuration and need someone to ELI5 what those options are

    so the video seem to be a bit outdated but unlike in the video tutorial, setting up Jellyfin via TrueNAS SCALE's app manager, there's 3 other options under Network Configuration's Port Bind Mode:
    • Publish port on the host for external access
    • Expose port for inter-container communication
    • None 
    1.in ELI5, what do these options do? if I want to run it only locally with no plan on doing any port forwarding , which options do I select and what do i need to change?

    2.do i need to change the webUI Port? if so, is there a specific number i'm supposed to put or just leave what was provided there?

    3. whats the difference between Publish port on the host for external access vs Expose port for inter-container communication?


    Attached Files Thumbnail(s)
       
    bitmap
    Offline

    Community Moderator

    Posts: 1,058
    Threads: 9
    Joined: 2023 Jul
    Reputation: 30
    #2
    Yesterday, 01:14 AM
    1. Publishing a port allows communication outside of the docker stack. Most of the time you'll want to publish 8096. This will allow you to connect devices to IP:8096 for playback.
    2. Exposing a port doesn't really do much, it just lets other containers know they can communicate using the specified port.
    3. Nothing. You won't be able to access Jellyfin.
    Jellyfin 10.10.7 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage

    [Image: AIL4fc84QG6uSnTDEZiCCtosg7uAA8x9j1myFaFs...qL0Q=w2400]
    « 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