Hacker News Reader

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.

View on HN

> 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.

Reply on news.ycombinator.com