• 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 Jellyfin is the only service in my k8s cluster that cant be curled (or accessed)

     
    • 0 Vote(s) - 0 Average

    Jellyfin is the only service in my k8s cluster that cant be curled (or accessed)

    SpiderUnderUrBed
    Offline

    Junior Member

    Posts: 14
    Threads: 7
    Joined: 2023 Oct
    Reputation: 0
    Country:New Zealand
    #1
    2025-08-20, 12:01 PM (This post was last modified: 2025-08-20, 12:02 PM by SpiderUnderUrBed. Edited 1 time in total.)
    https://pastebin.com/Qu1VPsMf

    Code:
    spiderunderurbed@raspberrypi:~/k8s $ curl -H "Host: jellyfin.spidershomelab.xyz" http://192.168.0.22:80
    ^C
    spiderunderurbed@raspberrypi:~/k8s $ curl -k -H "Host: jellyfin.spidershomelab.xyz" https://192.168.0.22:80
    404 page not found


    jellyfin is the only service in my k8s cluster which I cannot curl, its also the only thing that runs on another node. How do i fix this so i can access jellyfin through my ingress?

    Code:
    spiderunderurbed@raspberrypi:~/k8s $ kubectl get ingress
    NAME                  CLASS    HOSTS                            ADDRESS                    PORTS  AGE
    gitea-ingress        traefik  gitea.spidershomelab.xyz        192.168.0.22,192.168.0.36  80      6d
    glance-ingress        traefik  glance.spidershomelab.xyz        192.168.0.22,192.168.0.36  80      6d
    gotify-ingress        traefik  gotify.spidershomelab.xyz        192.168.0.22,192.168.0.36  80      6d
    jellyfin-ingress      traefik  jellyfin.spidershomelab.xyz                                  80      3m4s
    nextcloud-ingress    traefik  nextcloud.spidershomelab.xyz    192.168.0.22,192.168.0.36  80      6d
    uptime-kuma-ingress  traefik  uptime-kuma.spidershomelab.xyz  192.168.0.22,192.168.0.36  80      6d
    vaultwarden-ingress  traefik  vaultwarden.spidershomelab.xyz  192.168.0.22,192.168.0.36  80      6d
    wordpress-ingress    traefik  spidershomelab.xyz              192.168.0.22,192.168.0.36  80      6d
    spiderunderurbed@raspberrypi:~/k8s $ 


    I am able to ping it from a container, the main issue is 8096 I think, that and/or pod-to-pod connectivity between nodes as I think it worked when jellyfin was on the same node as traefik? but there is also some weird jellyfin stuff happening. If it listens to 0.0.0.0 by default then I am really confused as to whats happening, if its only listening to localhost that makes more sense, here is some more information (my traefik), also I installed metallb to try and fix this issue, and I always had cilium running as my CNI
    traefik:
    https://pastebin.com/7ANL8T8L
    svc, pods, ingresses, etc:
    https://pastebin.com/uumFPiDu

    Also since I recently installed metallb to try and fix this issue, the ip metallb got for my ingress isnt working with the curl commands too, well with everything except jellyfin, and I did set the jellyfin domain env variable correctly.
    toytown
    Offline

    Member

    Posts: 96
    Threads: 3
    Joined: 2023 Jun
    Reputation: 3
    #2
    2025-08-20, 12:37 PM
    For CURL don't you need the "L" flag so that it follows the "web/" redirect?
    SpiderUnderUrBed
    Offline

    Junior Member

    Posts: 14
    Threads: 7
    Joined: 2023 Oct
    Reputation: 0
    Country:New Zealand
    #3
    2025-08-20, 12:57 PM (This post was last modified: 2025-08-20, 12:59 PM by SpiderUnderUrBed. Edited 1 time in total.)
    (2025-08-20, 12:37 PM)toytown Wrote: For CURL don't you need the "L" flag so that it follows the "web/" redirect?



    spiderunderurbed@raspberrypi:~/k8s $ curl -H "Host: jellyfin.spidershomelab.xyz" http://192.168.0.241/ -L
    Gateway Timeoutspiderunderurbed@raspberrypi:~/k8s $



    It doesnt work with the -L flag too
    « Next Oldest | Next Newest »

    Users browsing this thread: 2 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