• 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 Jelly Fin and Nginx Proxy Manager

     
    • 0 Vote(s) - 0 Average

    Jelly Fin and Nginx Proxy Manager

    Has anyone had success using the NGINX Gui and Jellyfin?
    jakeymongoose
    Offline

    Junior Member

    Posts: 5
    Threads: 2
    Joined: 2023 Sep
    Reputation: 0
    Country:United States
    #1
    2023-09-12, 09:11 PM
    Been trying to get Jellyfin to reverse proxy using Nginx and can't get it too work. I've been able to the the Nginx Proxy Manager GUI to reverse proxy with my domain name as well as get ssl encryption through lets encrypt. So luck whatsoever with Jellyfin. I'm pretty new and i went the proxmox vm route and I think its confusing me. My setup is as follows

    Proxmox-Ubuntu Server-Docker/Portainer-Jellyfin Container-Nginx Container-Crowdsec (containers all on same network)

    I got the nginx Manager proxy to work by forwarding ports 80 and 443 to my Proxmox machine. Domain name (nginxmanger.xxxx.com) is pointed to the public IP address of the machine. I made a reverse proxy in the manager (nginxmanager.xxxx.com pointed to the IP Address of the Nginx docker container and port 81). I can now just type in the web address and i'm taken to a https instance of the nginx manager. 

    I have no such luck with Jellyfin when trying to replicate these sorts of settings. Remote access is enabled. Beyond that i'm pretty much stuck. I tried to edit the jellyfin config file but I could never get that to work either. I'm getting a lot of errors and i'm not sure which ip address i'm supposed to use (ubuntu server, docker container etc) and where. As it stands i'm only able to even access the jellyfin gui by using the private Ip of my ubuntu server machine followed by 8096. Which is allowed by my firewall rules. I'm going to try the tailscale route next.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2023-09-12, 09:24 PM (This post was last modified: 2023-09-12, 09:34 PM by TheDreadPirate. Edited 3 times in total.)
    To actually answer your question, you need to configure nginx to so that when you access whatever port on nginx it then forwards that traffic to jellyfin port 8096. Create a new proxy host, specify the IP of jellyfin, port 8096, http protocol.

    But to back up a little. I'm wondering why you chose your setup. You COULD just install jellyfin and NPM as containers directly on Proxmox. OR you could have just gone bare metal Ubuntu if that is the only VM. And then install jellyfin and nginx (not NPM) also bare metal.

    As it stands, you have several layers of virtualization complicating configuration and troubleshooting. To get hardware accelerated transcoding working your GPU will need to pass through two layers of virtualization before Jellyfin can access it. This requires additional configuration. If you hardware even supports that (IOMMU in your BIOS).

    If Ubuntu is the only VM, consider scrapping this setup and going bare metal everything. There is no benefit to this setup, as you described it, and only cons.
    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]
    jakeymongoose
    Offline

    Junior Member

    Posts: 5
    Threads: 2
    Joined: 2023 Sep
    Reputation: 0
    Country:United States
    #3
    2023-09-13, 06:40 AM
    Great insight! I definitely have delved too deep. I think I have an ok handle on the Proxmox layer but once I went to docker on top of all that I got way lost. Im trying to learn about all this stuff and I’m using jellyfin as a sort of goal. I think I will take your advise and cut back a few layers and try again. Btw the whole Tailscale thing works flawlessly. I just had to get Tailscale on the Ubuntu VM that has my docked containers.
    bitmap
    Offline

    Community Moderator

    Posts: 781
    Threads: 9
    Joined: 2023 Jul
    Reputation: 24
    #4
    2023-09-13, 06:46 AM
    *whispers* Come over to the dark side and containerize your life...
    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]
    jakeymongoose
    Offline

    Junior Member

    Posts: 5
    Threads: 2
    Joined: 2023 Sep
    Reputation: 0
    Country:United States
    #5
    2023-09-14, 03:17 AM
    Oh I will. I’m pretty new so I’m going to start over and see what I’ve missed along the way. The ultimate goal is to get pretty comfortable with vms and containers. I think I’m just lost as far as the networking and internal configurations etc. I can make sense of it better when it’s on one “machine”
    droog
    Offline

    Junior Member

    Posts: 1
    Threads: 0
    Joined: 2023 Aug
    Reputation: 0
    Country:Canada
    #6
    2023-09-14, 04:04 PM
    My setup is similar to yours.

    And yes, it sounds like you're trying to implement a bunch of things at the same time, and getting lost along the way.

    You're moving in the right direction though.  If you start by adding one piece to your stack, making sure it works, adding another piece, etc, then I'm sure you will succeed.

    Some specific suggestions:
    • I'll assume you're sticking with giving Jellyfin its own VM, with the VM running on top of Proxmox
    • After setting up the Jellyfin VM, make sure you're able to access Jellyfin webui from other computers on the network, without the reverse proxy involved (http://192.168.1.5:8096 or similar)
    • You might need to open port 8096 on your Jellyfin VM
    • Once you know for sure that this works, configure Nginx Proxy Manager and whatever DNS records are needed

       

       
    « 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