What is going on with chromecast support?

[Dysan 2]

Finally managed to install a certificate to solve the issue that the cast devices are not visible.

I can now see my chromecast devices, and select them.

The TV shows the Emby logo, and ready to cast.

But no matter if i use the app / chrome mobile or chrome desktop when i press play nothing happens.

neither the play or resume button responds.

info: Version 4.0.3.0 Running on http port 8096, and https port 8920.

attached is the server log.

 

 

Log.txt

Edited March 17, 2019 by Dysan

[Luke 37119]

Hi there, did you forget to attach the log file? What kind of certificate did you install? Is it a certificate that Chromecast will accept?

[Dysan 2]

Sorry forgot to attach. (done it in the post)

 

In te chromebrowser the certificate is approved, the connection works, but i cannot play anything.

When playing on my phone and selecting the cast icon, and correct device the playback immediatly stops on my device.

before the certificate (with the unsecure site warning) the behaviour was the same since the last update.

attached screenshot of the certificate

Edited March 17, 2019 by Dysan

[Luke 37119]

Does the server dashboard display the same remote address that is associated with the certificate?

[Dysan 2]

Yes, and the behaviour is the same when i access emby from the local lan ip on https (and before the certificate changes)

[Dysan 2]

Small update:

When using the chromebrowser on mobile, chromebook, and windows device in the local network

1. local ip of emby on http there are no chromecast devices available
2. local ip of emby on https there are chromecast devices available, tv goes in ready to cast from emby, but pressing play does absolutely nothing.
3. wan domain name of emby on http there are no chromecast devices available
4. wan domain name of emby on https there are chromecast devices available, tv goes in ready to cast from emby, and everything works as usual

When using the emby app, the cast icon is available and pressing play does nothing (same as 2 in example)

i know 1 & 3 are behaving is designed by google (no chromecast from non secure), but option 2 should be working?

When using option 4 isn't all my media played through the WAN network (thus giving me a low quality connection? )

[CBers 6771]

FWIW, I can cast OK to my Shield from the mobile Chrome browser on my phone and playback starts.

 

I have to use my external https (nginx) address though, otherwise you cannot connect to a Chromecast device.

 

If I use the local http address, there is no Chromecast devices to chose from.

 

I use a LetsEncrypt SSL certificate in nginx.

[Luke 37119]

 

 

1. local ip of emby on https there are chromecast devices available, tv goes in ready to cast from emby, but pressing play does absolutely nothing.

 

Because chromecast tries to use the same address and this will not work as it's not the same address that is associated with the certificate.

[Dysan 2]

Because chromecast tries to use the same address and this will not work as it's not the same address that is associated with the certificate.

So the only option is 4, but wont that stream everything from my WAN connection to the chromecast ?

without the certificate the results were the same? 

and why does the app have the same behavior?

[Luke 37119]

@@Dysan, I think that will actually vary per network setup because sometimes network routes can be optimized,

 

As far as why the app has the same behavior, there's two sides to this story:

 

• App connects to your Chromecast receiver (this is easier from the mobile apps, the browsers will require https)
• Chromecast receiver connects to your Emby Server - this will be the same no matter which controlling app you're using. if this is over https, you'll need to be using conditions that Chromecast will allow.

Does this help answer your question?