Sometime this week one of my family members lost the ability to connect securely so everything is now streaming at 2mbit max. It is the case for their Windows app, Web browser, Roku TV app, and a stand alone Roku Premier. At another family members, they have not seen any change with their Roku and connect at full speed. The problem house hasn’t updated anything that they are aware of (not technical so they don’t touch the network.) The server hasn’t had any issues with having remote access enabled (that is after it broke a few months ago and I had to set up manual port forwarding).
I re-setup the Plex for Windows on their pc and got a message that ‘the server was not set to allow for secure connections’ even though it was currently set at Required (though I tried preferred and saw no change). I have to Enable Relay on the server for them to see anything.
I am not able to access their router yet unfortunately as it was provided by the ISP (Ubiquity Edgemax - Rainier Broadband) and they don’t know if they have a password for it. I did try the steps here Why does my Plex Media Server think a local PC is remote. to try to see if it is some new DNS rebinding issue but got an error of “Please sign in” from their side when entering in https://plex.tv/pms/resources.xml?includeHttps=1& X-Plex-Token=xxxxxxxxxxxx (with the actual token).
Any thoughts as to how to further troubleshoot and resolve?
Most likely a DNS issue. Their ISP might have switched on a filter policy or might have changed something else related to DNS.
If it’s really a DNS issue, you cannot solve it easily without access to the router configuration. If they don’t use any other “server” apps like online gaming or other streaming software, you might be able to put a second router behind the first from the ISP.
In its settings put 8.8.8.8 as the DNS server (that address is Google’s).
Another (tiny) chance is to change the public port number of your Port Forwarding to something different than 32400, just in case their ISP is filtering traffic based on well known port numbers.
You’ll have to make the change both in the settings of your router and in Plex.
Thanks Otto. I gave the outside shot a try by assigning a random number in the 40,000 range and it didn’t change anything for them. Which is good I suppose that they aren’t specifically trying to hinder Plex via port blocking.
Edit: The wonderful ISP doesn’t give customers access to the router directly and they don’t even have limited web config (like Comcast). Tech guy said he confirmed DNS Rebinding is not blocked. Couldn’t/wouldn’t config the DNS server to cloud flare or google (don’t know what it is) but I’m being escalated to ‘tier 2’ for help. If Rebinding isn’t blocked, I have no idea what to do next.
Changed the title of this post as it turns out it wasn’t anything directly to do with changes on their side as I saw a comment from another user noting external problems with this release that were fixed by a rollback to 1.18.8.2527. I noticed my server had an update on the same day they lost connectivity.
Rolling it back to 1.18.8.2527 immediately resolved the issue and they are able to connect directly and stream at full bitrate.
Again, it did not affect another location or my ability to connect directly via my cell phone (wifi off/cellular network).
