• 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 Reverse proxy not working for new PC?

    Pages (2): « Previous 1 2

     
    • 0 Vote(s) - 0 Average

    Reverse proxy not working for new PC?

    4r5hw45twh
    Offline

    Member

    Posts: 132
    Threads: 31
    Joined: 2024 Mar
    Reputation: 0
    #11
    2024-09-29, 12:20 PM (This post was last modified: 2024-09-29, 12:34 PM by 4r5hw45twh. Edited 5 times in total.)
    (2024-09-29, 12:04 AM)TheDreadPirate Wrote: Negatory.  Subdomain CNAMEs can point to domain names.  They can also be a completely different IPs.



    "jellyfin" is a cname that points to my domain.  So jellyfin.domain.tld would resolve to my public IP. This allows you to have multiple services listening on the same port since the reverse proxy would direct traffic to the proper destination based on the subdomain used.  This also allows you to change how Cloudflare handles each subdomain.  Whether DNS only or proxying.  If you used subPATHs you wouldn't be able to do this.  Like domain.tld/jellyfin.

    Hmm. I decided to try and just use NGINX Proxy Manager (NPM) on Docker (JF is on my machine directly, not Docker).
    On CF, I have my A domain record pointing to my server's public IP: https://i.imgur.com/9AE6YmP.png
    I have NPM proxy host set for the same subdomain name like: https://i.imgur.com/4JfyBCH.png
    I have a SSL (Let's Encrypt) thing setup on NPM. Ports are all forwarded fine.

    Still can't connect outside the network. If I bypass NPM completely and just use proxied CF + tunnel to my local IP, it works fine outside the network, which looks like this: https://i.imgur.com/rg373Xk.png - CF creates the record automatically when the tunnel public hostname is created, shown here: https://i.imgur.com/f7slqwc.png
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #12
    2024-09-29, 04:29 PM
    The A record should be just your domain, no subdomain, and your public IP. You'd create a separate CNAME that is just the subdomain name and the target is your domain name.

    Also, you should setup your clients to use Cloudflare for DNS to ensure that DNS updates are received immediately. Otherwise, changes to DNS for existing records not take 24-48 hours to propagate to your current DNS.

    I'll send you a screenshot in a PM so there is less ambiguity when hiding our info from public.
    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): « Previous 1 2

    « 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