Hacker News Reader

Comment by zeruch | Hacker News Reader

The literal only thing that keeps me from moving to Jellyfin is that I cannot seem to get it to work with a Chromecast.

If that worked (and I'm not sure if its a cert problem or something else) I'd be happily away from Emby/Plex and every other option I've used in the past.

View on HN

Interesting. I recently installed jellyfin and have no issues streaming it to my chromecast. It works beautifully.

I believe this might be caused by Google. Chromecasts will only cast from URLs that have a valid HTTPS certificate (self signed will not work). If you're accessing your Jellyfin over the local IP it will be impossible to get a valid certificate for it.

> If you're accessing your Jellyfin over the local IP it will be impossible to get a valid certificate for it.

I just made a domain name for all of my local network services. Each service gets a subdomain that resolves to a local IP address, so like jellyfin.mydomain.com -> 10.x.x.x. Then just do DNS validation with letsencrypt. Boom, valid cert.

Correct, that's what I do as well. I meant if you actually use 10.x.x.x:8096 to access your Jellyfin instance

FWIW if you want to run your Jellyfin on the public internet, you can use NAT hairpinning in your local network and have that subdomain resolve to your public IP, and still access it from within your network :).

For the record, Plex gets around this by having a wildcard cert for a domain which just resolves to the local IP, ie 10.0.1.2.local-plex.tv (or whatever it is) resolving to 10.0.1.2.

I could only get it to work when I was out of the house, but inside, it never connected. You can ask on their Github for support, but I wasn't able to solve even with their help.

This could be a whole lot of causes. For example, our home access points by default isolated each wireless client, so they couldn't even see each other, much less a central server.

Reply on news.ycombinator.com