Emby Docker Chromecast Playback Issues

[josephdouce 3]

So here is my issue, I am running Emby in Docker behind a nginx proxy with SSL

 

I am able to access the server at and web playback works fine

 

https://emby.myhost.com 

localhost:8096 

192.168.1.100:8096

 

However, Chromecast only works when I use the actual machine IP 192.168.1.100:8096

 

Chrome definitely accepts my SSL cert shown here

 

 

The flows are as follows 

localhost:8096 > Docker Container > Emby Server 

192.168.0.100:8096 > Docker Container > Emby Server 

https://emby.myhost.com:443 > 443 nginx-proxy 8096 > Docker Container > Emby Server

It looks like the host names are not correctly passed to Chromecast as obviously Chromecast wont be able to resolve localhost and it adds the 8096 port to https://emby.myhost.com because its on the local network which also doesn't resolve.

 

[Luke 42086]

Hi, what kind of SSL cert are you using? You need to make sure the cert is something that Chromecast will accept.

 

Second, if you connect with the local hostname, then Chromecast will use the local ip address that is displayed on the front page of the emby server dashboard, so you'll want to make sure that is correct. Thanks !

[josephdouce 3]

LetsEncrypt

 

The dashboard shows the docker container IP which doesn't work however I have the same issue over WAN, what I want is to use emby.myhost.com regardless of weather I am local or WAN which actually works fine for everything except Chromecast which is confusing as hell. 

 

does chromecast just not like host names? I cant see why one of the first 2 should work and the other shouldn't when they are both point to the same IP

 

myhost.com:8096      Chromecast doesn't work      (WAN manually forwarded ports)

95.145.......:8096        Chromecast works                (WAN manually forwarded ports)

 

emby.myhost.com:80 Chromecast doesn't work     (nginx-proxy 80:8096)

 

192.168.1.100:8096   Chromecast works                (local no forwarding required)

localhost:8096            Chromecast doesn't work     (local no forwarding required)

Edited December 28, 2017 by josephdouce

[Luke 42086]

over WAN it will use the remote address displayed in the emby server dashboard. There are hosting settings under Advanced that can help you tweak these, and/or you may want to adjust the network settings of the Docker container. Thanks.

[josephdouce 3]

over WAN it will use the remote address displayed in the emby server dashboard. There are hosting settings under Advanced that can help you tweak these, and/or you may want to adjust the network settings of the Docker container. Thanks.

 

It appears not, since if I connect over WAN using the host name Chromecast doesn't work, but if I connect using the WAN IP it works fine. Is there a way I can see the exact command that is being sent to the chromecast? 

[Luke 42086]

Then why not just use the WAN IP? I don't really know what command you mean. We simply look at the address, and if it's something that Chromecast supports then we use that. If not, then we use the address listed on the front page of the emby server dashboard. thanks.

[josephdouce 3]

I can just use the WAN IP but its annoying that the host name doesn't work, I mean the url that is sent to the chromecast, using the WAN IP is a work around but why would an IP and a host name that points to that IP behave differently.