herod2k 1 Posted November 25, 2019 Posted November 25, 2019 (edited) Hi, I'm trying to cast Emby to my chromecast by I can't.My configuration:Sever: Latest Docker container on Linux Alpine as host. The server uses a SSL certificate generate automatically using Traefik. Emby server version: 4.3.0.26 Clients: Android Phone Sony XZ Premium (and others devices) My server is at home and until now I've never had a problem with Emby, I can use it locally with my Nvidia Shield, Android Phone, iPhone, MacBook Pro, etc etc. Also outside my apartment, everything works perfectly, I can stream and trans-code without any problem. Today I've installed a Chromecast first gen in my bedroom, I opened my Android app, pushed the button cast, the Cromecast changed to Emby (ready to cast) and when I went to push play on my phone the button didn't do anything, it seemed like disabled. So I've disconnected the chromecast from my phone, I played something, it was working perfectly, so I've tried to enable the cast during when it was already on play. Same thing happened. The chromecast went to Ready to cast, but the app on my phone stopped to work and it went to a grey screen.Screenshot: https://ibb.co/4R9xD3tI've also try the same steps with an iPhone and I got the same results. I've tried to cast with my laptops (Linux and MacOS) using Google Chrome, but my chromecast doesn't appear in the list:Screenshot: http://i.imgur.com/KdtQ4PZ.pngIt should appear there and also my Nvidia Shield. I can see just my browser and the phones. I've tried to cast Netflix and Youtube and they work perfectly. I've also tried to reduce the video quality from my phone configuration, to 720pScreenshot: https://ibb.co/QcLJQCR I've checked also the logs, but I didn't find anything weird inside, just some socket Error Any idea if it is a bug or something that I should fix?ThanksH2K Edited November 27, 2019 by herod2k
herod2k 1 Posted November 26, 2019 Author Posted November 26, 2019 Small Update: I have a Chromecast second generation, not the first one.
herod2k 1 Posted November 27, 2019 Author Posted November 27, 2019 (edited) Ok. I've found out the have the same problem described here:https://emby.media/community/index.php?/topic/56771-chromecast-address/page-1 If it could be usefull to someone a temporary workaround is to put the local server ip and local port on my mobile app or use chrome browser on the phone and cast from there. (To cast from the browser I discovered that you must use the https connection) Edited November 27, 2019 by herod2k
Luke 38844 Posted November 28, 2019 Posted November 28, 2019 Thanks for the feedback. Glad you sorted it out in the browser. Are you still having an issue casting from the store apps?
Solution herod2k 1 Posted December 1, 2019 Author Solution Posted December 1, 2019 Hi Luke! Thanks at the end I've found the solution. In the network configuration I've put my host IP in "Bind to local network address". And I've also closed the external port forwarding of the 8096 and 8920 (I probably forgot then open) and now it works perfectly. I suppose that it was trying to use the docker ip 172.0.0.x and not finding anything it was trying to use the external domain with the 8096 with the ssl. But it was totally wrong combination. Now it works flawlessly. Thanks again H2K 1
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