• 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 Jellyfin through caddy only accessable on local network

     
    • 0 Vote(s) - 0 Average

    Jellyfin through caddy only accessable on local network

    I can only access jellyfin on my local network
    bond-title-bond
    Offline

    Junior Member

    Posts: 8
    Threads: 2
    Joined: 2023 Nov
    Reputation: 0
    Country:United States
    #1
    2023-11-08, 02:57 AM
    Hello,

    huge noob here.

    I have jellyfin setup on debian going though caddy as a reverse proxy to my domain. I have cloudflare handling dns. Everything works when I'm connected to the local network but when I try to access it in public it doesn't work.

    I mostly followed this tutorial https://www.youtube.com/watch?v=zCyx4vmp4k0 but changed a few things. mainly I didn't include the api because it was giving me an error.

    I also have openvpn running on the whole server. I tried it with and without it running with no change.

    Does anyone know what I need to do to get this going?

    Thanks in advance!
    Openmediavault6
    Standalone Jellyfin
    Casaos for docker containers
    Amd ryzen 5 2600
    Gtx 1070
    10 x 6tb toshiba mg04 in raid 6
    weberc2
    Offline

    Junior Member

    Posts: 6
    Threads: 2
    Joined: 2023 Nov
    Reputation: 0
    #2
    2023-11-08, 03:47 AM
    How does it fail (what error are you getting)? Are you trying to access it via your VPN or the public Internet? without more information, my guess is the DNS entry contains the private IP address of your server rather than the public address—you can use dig or nslookup to check the IP address associated with your domain name.
    bond-title-bond
    Offline

    Junior Member

    Posts: 8
    Threads: 2
    Joined: 2023 Nov
    Reputation: 0
    Country:United States
    #3
    2023-11-08, 08:12 AM
    On web browsers it just doesn't load. On the android app it says "Tried 5 candidates for input, without success. Unable to reach server" then it shows 5 variations of my domain (https, http, port 8096 and 8920.

    I'm trying to access it via public internet.

    The nameserver is pointed at cloudflare. And DNS on cloudflare is pointed at my public  IP.

    It was working yesterday morning. But I uninstalled openmediavault because I couldn't get it to stop listening to port 80 and I caddy kept telling me I had a syntax error on the caddyfile. Once it was working (accessible via public internet through my domain name) I reinstalled openmediavault. I forgot to set the private IP to static so it changed. I couldn't get caddy to reload the new IP on the caddyfile without getting errors so I reinstalled caddy, changed the caddyfile to exactly what it was except the IP change and now it only works when I'm connected to the local network
    Openmediavault6
    Standalone Jellyfin
    Casaos for docker containers
    Amd ryzen 5 2600
    Gtx 1070
    10 x 6tb toshiba mg04 in raid 6
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2023-11-08, 12:31 PM
    When the local IP changed did you update your routers port forwarding rule?
    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]
    bond-title-bond
    Offline

    Junior Member

    Posts: 8
    Threads: 2
    Joined: 2023 Nov
    Reputation: 0
    Country:United States
    #5
    2023-11-08, 02:36 PM
    Hello again!

    Yes I updated the ports
    Openmediavault6
    Standalone Jellyfin
    Casaos for docker containers
    Amd ryzen 5 2600
    Gtx 1070
    10 x 6tb toshiba mg04 in raid 6
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2023-11-08, 03:33 PM
    In the network dashboard, is "remote connections" enabled? Is there a remote IP allow list?
    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]
    weberc2
    Offline

    Junior Member

    Posts: 6
    Threads: 2
    Joined: 2023 Nov
    Reputation: 0
    #7
    2023-11-08, 03:55 PM
    (2023-11-08, 08:12 AM)bond-title-bond Wrote: On web browsers it just doesn't load. On the android app it says "Tried 5 candidates for input, without success. Unable to reach server" then it shows 5 variations of my domain (https, http, port 8096 and 8920.

    I'm trying to access it via public internet.

    The nameserver is pointed at cloudflare. And DNS on cloudflare is pointed at my public  IP.

    It was working yesterday morning. But I uninstalled openmediavault because I couldn't get it to stop listening to port 80 and I caddy kept telling me I had a syntax error on the caddyfile. Once it was working (accessible via public internet through my domain name) I reinstalled openmediavault. I forgot to set the private IP to static so it changed. I couldn't get caddy to reload the new IP on the caddyfile without getting errors so I reinstalled caddy, changed the caddyfile to exactly what it was except the IP change and now it only works when I'm connected to the local network

    I've never used CloudFlare before, but I would check their logs to see if you can tell whether it's getting hit or not. I would also check Caddy's logs to see if the requests are making it to Caddy. Depending on the results, you might consider pulling CloudFlare out of the path altogether by pointing DNS directly at your public IP address (one other thing to verify is that you don't have any firewall rules in the path, particularly if you're using a cloud provider). Essentially you have to figure out where the failure point is (maybe you're already identifying that it's a caddy problem? I can't quite tell).
    « 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