• 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 Streaming from Jellyfin to Chromecast

     
    • 0 Vote(s) - 0 Average

    Streaming from Jellyfin to Chromecast

    Jeelyfin cannot do it, others can. Why is that?
    Uberkeyser
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2024 Oct
    Reputation: 0
    Country:Germany
    #1
    2024-10-21, 04:07 PM (This post was last modified: 2024-10-21, 04:09 PM by Uberkeyser. Edited 2 times in total.)
    I am trying to use Jellyfin as a Media server (on a Raspi)  to distribute content (including DVB-C live channels) to local devices, mainly to Google Chromecasts.
    I keep reading that streaming from Jellyfin to Chromecasts was tricky and required weird tasks, involves setting up a local DNS server that has some kind of facilitated https-certificates for the Jellyfin server and forwarding router ports in order to trick the Google devices to connect to that DNS server instead of Google's DNS servers..... all of which is weird to me not because it sounds complicated but because it sounds like compromizing my local network's security.

    While I understand the explanation (Chromecasts have hardcoded DNS servers (8.8.8.8 and 8.8.4.4) and wont connect to anything else); I wonder why other Upnp servers (namely KODI) can stream to Chromecast entirely in the local network, nothing being connected to the Internet, leave alone registered on Google'S DNS servers. (Before you ask why I am not simply using KODI then, KODI cannot transcode )

    Can anyone enlighten me how KODI does it, and why Jellyfin can't?
    niels
    Offline

    Core Team

    Posts: 248
    Threads: 4
    Joined: 2023 Jun
    Reputation: 12
    Country:Netherlands
    #2
    2024-10-22, 06:52 AM (This post was last modified: 2024-10-22, 06:53 AM by niels.)
    I'm not sure how it works with Kodi, but for other media servers they often use proxy everything through their cloud. Jellyfin doesn't have this, media is loaded directly from your server when you cast. For that network access Google uses their own nameservers (8.8.8.8) and require a secure connection (https) so your DNS should resolve properly with a valid certificate.
    [Image: GitHub%20Sponsors-grey?logo=github]
    Uberkeyser
    Offline

    Junior Member

    Posts: 2
    Threads: 1
    Joined: 2024 Oct
    Reputation: 0
    Country:Germany
    #3
    2024-10-22, 01:56 PM
    Thanks, Niels. But it does not explain the phenomenon. For complete disclosure: I am using Home Assistant to trigger a stream from KODI (DLNA/Upnp) to Chromecast. It works like a charm, as long the source is using a codec that Chromecast can handle so no transcoding necessary. But neither KODI nor Home Assistant is connected to a cloud (That's a fact not a guess)
    As an explanation I was rather thinking of something like UPnP using neither domain names nor https, hence Chromecast's dendency on Google's DNS is irrelevant for Upnp. But then this should also apply to 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