Server Version#: 1.32.3.7089
Player Version#: 9.23.0.1746 (Android) - Chromecast
Hi - I moved to a new ISP a couple of weeks ago who provided a new router.
Since then I have been unable to cast from my plex media server to my chromecast devices due to an issue with secure connections. I suspect that this may be due to DNS rebinding protection from the ISP in some way. This document describes issues with DNS rebinding protection which may cause problems: https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/#toc-4
I have tried using alternative DNS servers however and that has not worked, it then goes on to describe scenarios with dnsmasq and pfSense DNS Resolver.
I don’t seem to have any other options within my new router. If I reconnect my old router, everything works perfectly again.
Are there any further diagnostics I can do to pinpoint whether this is the problem - or any other workarounds (other than putting the old router back)? Any help would be appreciated.
What ISP do you have? or just the model of the router they gave you. Possibly someone else has the same and knows solution. Are you able to use Remote Access?
Thanks I was previously with Sky and am now on talktalk, and it is the new talktalk hub, which I believe is a Sagemcom FAST 5364 - though as is usually the case the ISP has it pretty locked down I think.
It is a terramaster NAS server on the local network running PMS.
All other connections to it work and playback is no problem, so PC/laptop browser can play fine. Mobile app can play fine on the phone as well - just when you try to cast to any of our Chromecast from the app (we have two) it fails with that error.
It is not WiFi, as that is disabled in both my new and old router, as I have a mesh network which connected the same to either router.
Oh, and yes all other apps etc are casting fine to Chromecast (e.g. Disney+, Netflix etc)
Yeah - tried both preferred and required (there is no disabled?), but neither option makes any difference. I think the chromecast is not permitted to connect insecurely - so it will force the requirement for a secure connection from what I’ve read anyway - a google restriction a few years ago?
Thanks - I don’t think this will help - I don’t have any problems playing via any of my browsers - they all work fine. Also the android app plays fine when playing back on the phone. The only problem occurs when I try to cast from the app (or chrome browser) to a chromecast device, where it fails with that error.
Looks like this is definitely a DNS rebinding issue. Your server is still blocked.
This line is a test for that.
May 31, 2023 18:43:41.686 [139725742254736] DEBUG - Network: 192-168-1-240.abcdefghijklmnopqrstuvwxyz012345.plex.direct failed to resolve to 192.168.1.240 but instead yielded (null)
We have a bunch of employees who are in the UK but none that have responded to me so far are using Talk talk so not sure if that is something you can change in their router. (I’m assuming you tried something like Googles DNS on your server computer already)
I edited the title of this topic to include TalkTalk so hopefully maybe another user may have it and know a solution with their hardware.
Thanks - yeah I tried google, cloudflare and cisco alternative DNS services, but none of them worked. The router itself must be blocking resolving local network addresses or something. The ISPs support don’t seem to have any idea though. Looks like I will just have to go back to my old router for now.
