Thanks - rebooted server etc. - had already done that previously when the network changed onto the other subnet.
Still not able to connect “securely” via the chromecast same error. I do have it set to “require” secure connections, however that always worked previously… only thing that has happened is the move of subnets…
Thought you might be on to something there, as my new ISP router does look as though it is IPv4 only, however I changed the setting, rebooted “all the things” (plex server, chromecast, app), and still same error message I’m afraid.
…ok to add to the mystery, I’ve also had a broadband fault recently, and they’ve decided my router is faulty and causing some of the speed problems. Because of that, I’ve temporarily replaced back to my old router, but switched that router to the 192.168.1.x subnet.
Lo and behold Plex/chromecast is now working again!? Don’t quite understand this - I thought it would all be point-to-point on the internal home network, so why would th router cause an issue?
Yes they are on the same subnet, and they’re not in isolation mode.
It’s really odd, as all I’ve put back is the old router, (but changed it to work on the 192.168.1.x subnet), and everything is happy again. The old router does support IPv6 though, so that is still different. (Although I have switched off IPv6 support in PMS). Unless, as the other router is being classed as “faulty” it was doing other odd stuff…
OK I have a new router from my ISP now, as they sent that out due to some other issues. The problem is my “cannot cast to chromecast” issue is also back.
So:
With my old ISP router, (it supported IPv6), if I put that back in - having reconfigured it for the 192.168.1.x network as well, everything works fine! I can cast to chromecast from my mobile app no problem. This is via a seperate “mesh” wifi network (I don’t use the router’s inbuilt wifi).
If I install the new router, reboot “all the things” (PMS, Wifi, Phone, Chromecast), as soon as I try to cast to chromecast I get the same error message above about unable to connect securely.
I have however disabled IPv6 support in the PMS admin, so not sure if that is a red herring. I am now running the same 192.168.1.x network on both the old router and the new one, but only the old one allows me to cast to chromecast… Is there some “firewall” type thing happening - not sure why the router would be able to interfere with or block internal network traffic?
If I simply play back in the app that works fine, as does playing back in a desktop browser - it’s just chromecast that is broken.
PMS to force it to refresh locally (it might think a new cert isn’t needed yet)
