Jump to content

Chromecast problem


pbrouty

Recommended Posts

Detail4687

Yes that would be fine. Also for those who may have missed it, you can also use the web app over localhost, or our android mobile app, or iOS app.

 

Same problem here, and "web app over localhost" doesn't work either. Android does.  In the locahost the chromecasts (I have 3 on my local network) don't show up.

Link to comment
Share on other sites

Same problem here, and "web app over localhost" doesn't work either. Android does.  In the locahost the chromecasts (I have 3 on my local network) don't show up.

 

Hi there, web app over localhost works just fine. "Same problem here doesn't apply", because no one here has reported that.

Link to comment
Share on other sites

Detail4687

Hi there, web app over localhost works just fine. "Same problem here doesn't apply", because no one here has reported that.

 

?!?!?!?  This whole thread is about the problem.  I, too, am enjoying this issue. Anyway, localhost viw web app is not working just fine for mre.

 

5cd610a91dabd_Screenshot.jpg

Link to comment
Share on other sites

Hi, it's right in your screenshot. Don't  you see Chromecast in the middle of the list?

Link to comment
Share on other sites

Detail4687

Hi, it's right in your screenshot. Don't  you see Chromecast in the middle of the list?

No, that's not it.  Compare the three chromecasts to the right with my list.  None are there.

Link to comment
Share on other sites

  • 2 weeks later...
Detail4687

In re-installed Plex just for a test, and my Chromecast devices show up (Plex in Chrome on the same LAN). 

Link to comment
Share on other sites

When you click Chromecast in the middle, then it launches the native google cast picker and you see the same list as you would see if clicked the cast button in the browser. That's how you do it in the web app.

  • Like 1
Link to comment
Share on other sites

Detail4687

When you click Chromecast in the middle, then it launches the native google cast picker and you see the same list as you would see if clicked the cast button in the browser. That's how you do it in the web app.

that did it. My apologies. Such as simple solution. Thank you Luke!

Link to comment
Share on other sites

  • 7 months later...
Jemison

Hi all,

 

I just discovered this post - but recently my chromecast cast stopped functioning - the play button does nothing, although the Remote Control dialog is available - just nothing is received by the cc device.

 

I had already configured my emby server with a self-signed CA issued certificate.  The CA certificate is trusted on my chrome clients (Windows, android) - and up until about Sept/Oct - I had no problems casting from any device with chrome via https (8920).   Emby Server configuration has remote server name defined that matches the certificate subject name, and I added my local subnet as both local and remote whitelisted. In addition I used an online tool (can't locate it atm) to confirm the certificate would pass Google's validity tests - so that I don't get the annoying certificate is untrusted indicator in chrome.

 

For about a year I've been casting no problems, but it stopped.  I'm on emby version 4.3.1 on debian buster - and unfortunately I haven't been able to pinpoint exactly what happened prior to my losing the ability to play. 

 

Oddly enough, I can cast from a non-local web-browser pointing to the http (8096) instance on the server.

 

Any suggestions where to look to solve this?

Link to comment
Share on other sites

Hi all,

 

I just discovered this post - but recently my chromecast cast stopped functioning - the play button does nothing, although the Remote Control dialog is available - just nothing is received by the cc device.

 

I had already configured my emby server with a self-signed CA issued certificate.  The CA certificate is trusted on my chrome clients (Windows, android) - and up until about Sept/Oct - I had no problems casting from any device with chrome via https (8920).   Emby Server configuration has remote server name defined that matches the certificate subject name, and I added my local subnet as both local and remote whitelisted. In addition I used an online tool (can't locate it atm) to confirm the certificate would pass Google's validity tests - so that I don't get the annoying certificate is untrusted indicator in chrome.

 

For about a year I've been casting no problems, but it stopped.  I'm on emby version 4.3.1 on debian buster - and unfortunately I haven't been able to pinpoint exactly what happened prior to my losing the ability to play. 

 

Oddly enough, I can cast from a non-local web-browser pointing to the http (8096) instance on the server.

 

Any suggestions where to look to solve this?

 

What kind of certificate? Your Chromecast receiver is probably rejecting the SSL cert. Either that or it's not able to resolve the domain name attached to it.

Link to comment
Share on other sites

craigmac99

What kind of certificate? Your Chromecast receiver is probably rejecting the SSL cert. Either that or it's not able to resolve the domain name attached to it.

 

I am also having this issue and it started after i upgraded to 4.3.1, no issue before hand. im using a self signed cert and the domain name is resolvable on my local network so should be by the Chromecast as well. The only change was the upgrade to 4.3.1 so i feel it has to be related. 

 

how can i check if the CC is rejecting the cert? is there a debug log i can enable and retrieve from the Chromecast? 

Link to comment
Share on other sites

I am also having this issue and it started after i upgraded to 4.3.1, no issue before hand. im using a self signed cert and the domain name is resolvable on my local network so should be by the Chromecast as well. The only change was the upgrade to 4.3.1 so i feel it has to be related. 

 

how can i check if the CC is rejecting the cert? is there a debug log i can enable and retrieve from the Chromecast? 

 

There isn't really a way to get that specific error message other than testing the same address with plain http. So that's what you might want to start with. Re-configure your emby server for plain http, then use the android or iOS app to see if you can cast to your Chromecast.

Link to comment
Share on other sites

craigmac99

There isn't really a way to get that specific error message other than testing the same address with plain http. So that's what you might want to start with. Re-configure your emby server for plain http, then use the android or iOS app to see if you can cast to your Chromecast.

There is no issue with the Android app, this is what im using as work around for now, its only the web player. Video also plays just fine in the web player directly only the issue of nothing happening when you click play button when casting to the Chromecast app. Issue only started occurring after upgrade to 4.3.x, app loads up fine on the Chromecast from web player (full screen with logo) but nothing happens when you click any of the various play button.

 

 

i can see in chrome network inspect console that the request is sent out as a GET when i click the play button with a 200OK response code, but nothing happens on the Chromecast:

 

https://emby.hidden.local:8920/Users/5ee6b1e68284414599a7d13ce2fc4741/Items/21299

 

There appears to be well formed request and response headers as well so not sure what the issue might be here. Was working flawlessly untill i installed 4.3 im going to see if i can downgrade or setup a test with pre 4.3 code but don't have much time these days to build it unfortunately.

Link to comment
Share on other sites

Please try what i suggested using the android app to cast to chromecast. That's now you can narrow down a problem of general connectivity vs. a problem with the SSL certificate.

Link to comment
Share on other sites

Jemison

Hi Luke,

 

I can cast from http as well as from the android app.  Just not from https.  I used the site crt.sh/lintcert to verify that my self-signed certificate didn't contain validation errors, which is what I did originally months ago when I first switched to emby.  I'm willing to install an older release of emby if you can provide guidance.

Link to comment
Share on other sites

Jemison

Ok, so I created a new VM and installed release 4.2.0.40, created a new self-signed certificate that matched the new server - configured the networking settings - and voila - I can cast from chrome browser via https:8920!

Link to comment
Share on other sites

Jemison

Works with release 4.2.1.0 too.  I don't know how to install the minor 4.3 releases - but I can if it will help identify where it begins to fail - just need some howto guidance  :D

Link to comment
Share on other sites

Jemison

Hi again,

 

From this thread, seems that the source isn't being made available for emby version 4.x  :( .

 

Is there anything else we can provide to demonstrate the error to help lead to a fix?

 

Thanks

Link to comment
Share on other sites

willvincent

Since I keep getting notifications, and I just updated my server version -- I'll add that I too am no loner able to cast to chromecast with my previously working self-signed cert after upgrade.  I can still select chromecast, and choose the desired destination, but when I click play _nothing_ happens.. casting from android/ios still works as expected, going to revert to prior server version and see if it works again

Link to comment
Share on other sites

willvincent

Confirmed. Reverting to 4.2.1 my self-signed cert works again as expected.

4.3.x and 4.4.x are not behaving as expected.  Though interestingly, 4.3 _was_ working yesterday before a system reboot today, after which it would not work, so I tried installing 4.4 and it too didn't work properly, revert to 4.2 works again.

 

:unsure:

Link to comment
Share on other sites

bluelab1

I also updated my server version and am not able to cast to chromecast. It was ok with my self-signed cert before upgrade.  Same case: I select chromecast as the destination, and it says "ready to cast as usual" but if I click play apparently nothing happens.. Same as before reported: casting from android works as expected.


 


my 2 cents 


Link to comment
Share on other sites

 

I also updated my server version and am not able to cast to chromecast. It was ok with my self-signed cert before upgrade.  Same case: I select chromecast as the destination, and it says "ready to cast as usual" but if I click play apparently nothing happens.. Same as before reported: casting from android works as expected.

 

my 2 cents 

 

 

What address is in your browser address bar at the time of testing?

Link to comment
Share on other sites

What address is in your browser address bar at the time of testing?

 

My address is link and the hostname embysvr is resolvable on my network by my nameserver.  The self-signed certificate has embysvr has the commonName as well as the subject alternate name so that it passes crt.sh/lintcert validation.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...