• 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 SOLVED: Jellyfin stuck at 'restarting' | localhost:8096 not working

     
    • 0 Vote(s) - 0 Average

    SOLVED: Jellyfin stuck at 'restarting' | localhost:8096 not working

    Don Cezar
    Offline

    Junior Member

    Posts: 4
    Threads: 2
    Joined: 2023 Dec
    Reputation: 0
    #1
    2023-12-22, 06:38 PM (This post was last modified: 2023-12-22, 07:24 PM by Don Cezar. Edited 4 times in total.)
    Both issues are now solved, below are the fixes.
    Using two computers - one with Ubuntu server and docker container running jellyfin, one with windows, both connected to the same router.

    First issue: Jellyfin container stuck at 'Restarting'
    Fix: Make a new user and give it permissions to only access the folder you need. (Inside my path I made a jellyfin folder for the container with 3 sub-folders: cache, config & media)
    Code:
    sudo adduser jellyfin
    sudo usermod --shell /usr/sbin/nologin jellyfin
    sudo chown -R jellyfin:jellyfin /path/jellyfin
    id jellyfin

    Replace the id of the jellyfin user and the path in the following command, then run it:

    Code:
    sudo docker run -d --name jellyfin --volume /path/jellyfin/config:/config --volume /path/jellyfin/cache:/cache --mount type=bind,source=/path/jellyfin/media,target=/media --user id:id --net=host --restart=unless-stopped jellyfin/jellyfin

    Second issue: Localhost website wouldn't load
    Fix: Localhost only works for the current machine you're using. To access the website on another machine, even if on the same network, run hostname -I and use the first IP followed by the 8096 port. Example: 192.168.100.14:8069
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2023-12-22, 07:16 PM
    What networking type did you use? Host or bridge? Can you share your docker config for the container?
    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]
    Don Cezar
    Offline

    Junior Member

    Posts: 4
    Threads: 2
    Joined: 2023 Dec
    Reputation: 0
    #3
    2023-12-22, 07:23 PM
    (2023-12-22, 07:16 PM)TheDreadPirate Wrote: What networking type did you use?  Host or bridge?  Can you share your docker config for the container?

    I figured it out with the help of the people in Docker's discord server. If you could please check the fix I edited in the first post and let me know if it's alright so other users can potentially find this thread and use the same fix, that'd be great.
    Yababakets
    Offline

    Junior Member

    Posts: 17
    Threads: 1
    Joined: 2023 Dec
    Reputation: 2
    #4
    2023-12-22, 07:25 PM
    Do you have any ports published in Manual network port publishing (portainer - docker)?
    Are you on bridge or host network in Advanced container settings / Network (portainer - docker)?
    Is your Local HTTP port number set to 8096 in Dashboard / Network / Server Address Settings (Jellyfin) ?
    « 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