Server Version#: 1.43.2.10687
Player Version#: VIDAA 5.94.1
Recently downloaded plex on my TV and first used it to access a friend’s server with his remote watch pass. Then set up my own server on my PC, logged in, and when I tried to watch from my TV (running plex for VIDAA) it said I needed a remote watch pass. My TV and laptop are on the same local network, and I am not a very computer savvy person so the router is straight out the box with standard settings.
The first 3 numbers on the IP addresses for the PC and TV are the same. I have a VPN on my PC which I think may have been switched on when I downloaded PMS and logged in for the first time, but is now switched off. I’ve been trying to troubleshoot this for hours - accessing router settings etc. Downloaded Plex on my phone, which does have a VPN on it, and can access that just fine with VPN on and off. Checked my browser settings, checked my network settings, tried adding the TV IP address to Plex custom server address/local auth… basically everything that pops up when you google the title of this post. Can anyone help with what I might have done wrong?
Which steps, specifically, did you try? Arguably, the most important one is to ensure that you’re using a DNS server which doesn’t restrict private IP addresses (DNS rebinding protection). There are specific steps you must take to mitigate this. The most straightforward is to ensure your clients use a DNS server which isn’t your local router (like 1.1.1.1 or 8.8.8.8).
Definitely steps 5-7 and 11. I was having a go at step 10 but got nervous about editing the port forwarding settings on my router and called it quits for the night. For steps 1-4 - I don’t think I’m using containers from what I could tell via Google. Was pretty sure about DNS rebinding but could be wrong. No other router-type devices, and I think my IP address is within the home network range (it’s 192.168.1.xxx) on each device.
Apologies for being a complete computer idiot but what exactly is the client? Is that the TV? I had a go at changing the DNS settings on that (changed DNS 2 to 1.1.1.1) and changed the DNS provider on chrome to cloudflare but that made no difference. I could try changing DNS 1 on the TV in the morning if that is what you mean?
No worries! Yes, the client is whichever device(s) from which you’re attempting to reach your Plex server. It could be a TV, a web browser, whatever.
If you can change the primary DNS server on your TV to 1.1.1.1 and restart the TV, that might help.
For some background, the way Plex works for server discovery is to perform DNS lookups on connection information your server publishes to its (Plex’s) servers. DNS rebinding protection prevents lookups for host names to be resolved to local addresses. This forces Plex clients to attempt to use the public connection information, if it exists. This results in connection attempts appearing to be from remote sources, hence the error.
Public DNS providers, such as CloudFlare and Google, don’t impose these restrictions.
Its actually easier to set the DNS settings at the router level. That’s what I do. Google & Cloudflare are good choices. I’m using the Adguard public resolvers myself.
Holy crap, I owe you my life. I just changed the primary DNS server to 1.1.1.1 and now it works!! Thank you SO MUCH. Are there awards or something that I can give you??
