I’ve finally managed to get acces to my personnal libraries under the new app (only took 10 days of posts on this forum…) only to get a popup on my phone app that I need a Remote Watch Pass to cast my videos (from my personnal libraries) to my Chromecast.
I should note that I use the admin account of the PMS to access Plex on my phone app.
My understanding is that “remote watch” or “remote streaming” is different from streaming from my local network.
Am I missing something? My understanding is that despite the new app I should still me able to stream my videos from my Plex Server, using my phone’s Plex App as long as everything is connected on the same local network (my house network).
I am refering to this support article where it says that remote streaming is a way to access my Plex Media Server from outside my local network implying that I shouldn’t need that when streaming from my local network.
This obvisouly used to work just fine before the update…
The dashboard doesn’t really help. Since I cannot start a video from my phone’s app, the stream doesn’t appear in the dashboard.
I’ve tested blocking the mobile data from my phone to garantee that my phone is connected to my LAN (through WIFI) and is on the same network as my NAS running PMS but that didn’t solve the problem.
I can also tell that I do not run a VPN, neither on my LAN nor on my NAS.
So I am really unsure as to why all my mobile devices running the PLEX app are seen as being remote (outside of my LAN).
Check your router any settings named similarly to the below. They might be in a dedicated security section, or in the access point or Wi-Fi settings. Or even in the general LAN configuration:
Device isolation
Client isolation
Network isolation
Access Point/AP isolation
Guest network/Wi-Fi
Basically, look for anything that would potentially isolate devices connected via Wi-FI from the broader LAN.
Enabling guest functionality for a network is likely to do this, but any form of isolation could prevent the Wi-Fi client from being able to connect to other devices on the network. This would cause the client to attempt to connect via a remote connection, if available.
I’ll look into this but just found out while rying to that I do not have my router’s admin password anymore
I still find it weird that some existing settings would be working just fine with the old app but blocking the new app. I’ll keep posted when I get my router’s access back. I might have to resort to reboot it
Not a typo. It’s been my default gateway address for quite some years, not sure why exactly I ended up changing the default 192.168.1.x. I think I was testing various routers and wanted to differentiate the different newtorks. the 55 was purely random, I didn’t know that was a reserved address and even less that it could be a problem on a local network. I never had any issues with anything on my network before the Plex update.
I’ll switch it back to the standard 192.168.1.x whenever I gain back access to my router (or reboot it) to see if this changes anything.
So, finally had the time to regain control over my router.
I rebooted it to factory setting and now have a clean 192.168.3.x local network with a 255.255.255.0 submask. I’ve kept al of my devices on automatic IP adressing through DHCP.
I’m still getting the same remote streaming error when trying to load a video from a personnal libray on my phone. The phone is on the same network and submask as the NAS. I am now able to stream from the app.plex.tv. This wasn’t working in the past days so it’s a step forward !
On another post, a Plex Moderator asked me about containers on my NAS.
There are 3 default containers in the NAS but none are mapped to neither of the 2 Ethernet port of the NAS.
I think it might be a quirk of networking itself. IP addresses that are considered “public” are automatically handled as if coming from or to the internet. Since you set your local network IP range to one that is considered “public”, it’s possible that the Plex server - following standard rules for public IPs - considered all traffic to or from an IP in that range as being “remote”. And unless you have a Plex Pass or “Remote stream” pass, you are now restricted from doing anything “remote”.
Fixing your IP to be in an IP range considered “local” or “private” probably fixed it.
Incidentally, this is also a way to get around the new restriction on remote streaming. If you client looks to have a local IP (by using a VPN into your home network), Plex cannot tell you are remote, and allows streams.
