bluelab1 0 Posted January 12, 2020 Share Posted January 12, 2020 What address is in your browser address bar at the time of testing? Hi thanks for the fast reaction. This is what I have on the dashboard - It used to work with the "remote" address (so to have the chromecast recognize the certificate) Running on http port 8096, and https port 8920. In-Home (LAN) access: http://192.168.2.230:8096 Remote (WAN) access: https://minimac.mine.nu:8920 A Link to comment Share on other sites More sharing options...
Luke 36886 Posted January 13, 2020 Share Posted January 13, 2020 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. So the host name is only resolvable on your local network? Because the change that was made in 4.3 was that if you are connecting to the web app via an https url, then that's the url we give to the Chromecast receiver. Previous behavior is that it would try and do some detection to figure out if you were on the local network or not, and then it would pass the local network url to your receiver without SSL. Now it's just passing the https url, but in your case, the Chromecast receiver can't resolve local dns names, nor will it trust your self-signed cert. Link to comment Share on other sites More sharing options...
Luke 36886 Posted January 13, 2020 Share Posted January 13, 2020 Hi thanks for the fast reaction. This is what I have on the dashboard - It used to work with the "remote" address (so to have the chromecast recognize the certificate) Running on http port 8096, and https port 8920. In-Home (LAN) access: http://192.168.2.230:8096 Remote (WAN) access: https://minimac.mine.nu:8920 A What address is in the browser address bar? Link to comment Share on other sites More sharing options...
bluelab1 0 Posted January 13, 2020 Share Posted January 13, 2020 https://minimac.mine.nu:8920/web/index.html#!/home.html Link to comment Share on other sites More sharing options...
Luke 36886 Posted January 13, 2020 Share Posted January 13, 2020 https:// Are you inside or outside the same local network as the server? Link to comment Share on other sites More sharing options...
willvincent 3 Posted January 13, 2020 Share Posted January 13, 2020 For myself, I'm only ever internal, always the same network. My internal network has name resolution, so I access my local server at: `https://emby:8920` This works with older versions of the emby server, but newer while I'm able to select the chromecast as the destination, no play action is honored. It simply behaves as if I never clicked the play button in the first place. Sounds like the changes made in 4.3 will prevent this from ever working unless I make the domain externally resolvable.. that's problematic -- I have no desire to serve content outside, I just need to be able to reliably cast to my internal devices -- and preferably not _only_ via android/ios control. Link to comment Share on other sites More sharing options...
Luke 36886 Posted January 13, 2020 Share Posted January 13, 2020 We'll just have to revert the change so that it never tries to use your ssl url on the local network. 1 Link to comment Share on other sites More sharing options...
Jemison 0 Posted January 14, 2020 Share Posted January 14, 2020 We'll just have to revert the change so that it never tries to use your ssl url on the local network. Hi Luke, this would be ideal. I, like willvincent, only ever stream emby on my internal network - streaming to chromecast via web is my primary use case as I'm not using an android/ios device . Thx! Link to comment Share on other sites More sharing options...
willvincent 3 Posted January 14, 2020 Share Posted January 14, 2020 We'll just have to revert the change so that it never tries to use your ssl url on the local network. Sounds like a straightforward solution. Happy to beta test when ready. 1 Link to comment Share on other sites More sharing options...
Chriswho 1 Posted January 17, 2020 Share Posted January 17, 2020 Hi. Not sure if my issue is the same - just connecting via local host 8096. Was able to cast from web app to Chromecast last week, now cannot. When I select the cast icon, I just get 'Play On' - no devices are listed: When I select cast from the Chrome menu, I can see my Chromecast (Living Room TV): I can cast from the Android app on my phone to the Chromecast, and then I see this in the cast menu: Not sure why this is happening now? Thanx. Chris. Link to comment Share on other sites More sharing options...
Luke 36886 Posted January 17, 2020 Share Posted January 17, 2020 Hi. Not sure if my issue is the same - just connecting via local host 8096. Was able to cast from web app to Chromecast last week, now cannot. When I select the cast icon, I just get 'Play On' - no devices are listed: When I select cast from the Chrome menu, I can see my Chromecast (Living Room TV): I can cast from the Android app on my phone to the Chromecast, and then I see this in the cast menu: Not sure why this is happening now? Thanx. Chris. You need to run the web app in a secure context. That means either localhost or https. If that's something you can't do, then use the android or iOS app. Link to comment Share on other sites More sharing options...
kingargyle 19 Posted January 18, 2020 Share Posted January 18, 2020 Hi Luke, this would be ideal. I, like willvincent, only ever stream emby on my internal network - streaming to chromecast via web is my primary use case as I'm not using an android/ios device . Thx! Yeah ran into this issue myself with 4.3, only plan to ever stream internally so having the old behavior would be ideal as well. Link to comment Share on other sites More sharing options...
Luke 36886 Posted January 18, 2020 Share Posted January 18, 2020 It will be in the next release. Thanks for the feedback. Link to comment Share on other sites More sharing options...
Chriswho 1 Posted January 19, 2020 Share Posted January 19, 2020 You need to run the web app in a secure context. That means either localhost or https. If that's something you can't do, then use the android or iOS app. Hey Luke I am running the web app as localhost. This is the address: http://localhost:8096/web/index.html#!/home.html. Today, Chromecast is showing in the Play On menu! I have made no changes to any settings. When I couldn't connect the other day, I reset the server, restarted the browser and restarted my computer, but still could not connect to the Chromecast. Any idea why this would happen? Link to comment Share on other sites More sharing options...
Luke 36886 Posted January 19, 2020 Share Posted January 19, 2020 Not at this time, no. Link to comment Share on other sites More sharing options...
Jemison 0 Posted April 12, 2020 Share Posted April 12, 2020 It will be in the next release. Thanks for the feedback. Hi Luke, Just tried this in 4.4.2.0 - working like a charm! Thanks! Link to comment Share on other sites More sharing options...
Luke 36886 Posted April 13, 2020 Share Posted April 13, 2020 Thanks for the feedback ! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now