![]() It would be great if we could have an option in the Emby server to override this behaviour. In summary it looks like the Emby code is doing a check when chromecasting: "if URI is a DNS name, then use the discovered local IP address elseif URI is an IP, use the provided IP" However, if from the browser I use the docker host IP and port (10.10.3.212:14665), I can login to Emby and chromecast without any issue. I don't even see the chromecast attempting to do a DNS lookup of. I've confirmed this with a packet trace, and I can see that the chromecast is repeatedly trying to access 172.17.0.2:8096 which is what the emby server thinks its local IP address is. When you create the playlist, the name will automatically be highlighted, allowing you to enter any name you want.The XMLTV and M3U playlist can be directly imported to Emby or Plex. IPTV Player: play m3u playlist is very safe to use. ![]() The flow from the client to Emby looks like this:Ĭlients (10.10.x.x range) -> :80 (resolves public IP 58.161.xx.xx) -> hairpinNAT-to-loadbalancer (10.10.3.221:80) -> emby docker instance (10.10.3.212:14665)įrom the browser this is a perfect experience both on the internal network, and externally.įrom the internal network, when I select the option to cast to my chromecast I can see that the chromecast is failing to reach the emby server. The XMLTV and M3U playlist can be directly imported to Emby or Plex. As a result I've ensured my domain is resolvable by public DNS servers and used NAT hairpin to allow me to hit my public IP address from the internal network to access my emby instance. Add Emby on Android TV to access your personal media, recordings. I'm aware that chromecast bypasses any internal DNS servers in favour of 8.8.8.8. Emby Android While this patch makes your local server believe Emby Premiere features. This setup works perfectly, with the exception of chromecast when I use a DNS name in the browser.įor example, Emby is currently running in my environment as follows:Įmby container IP: 172.17.0.2 (this is the IP that's reported as the local IP in the Emby dashboard) DNS and load balancing is used to advertise the service dynamically. The container starts on any node within the cluster and on a randomized port which is mapped to 8096 within the container. ![]() I now run Windows Media Player client on a Windows 10 PC. ![]() I'm running the docker image on top of a mesos cluster with DC/OS and marathon. Plex gathers posters and artwork, cast and crew info, ratings, and more. Apologies for resurrecting this thread, however I am having the same issue as the O.P. ![]()
0 Comments
Leave a Reply. |