This thread is not for discussing the introduction of the Remote Watch Pass and this restriction for free users as such.
All postings trying to bring that up, will be deleted immediately.
The same happens to descriptions of how to circumvent the requirement for Remote Watch Pass, or posts which are asking about it.
Please stick to the topic:
Here we are trying to collect various tips, which could help those users who are only using Plex within their home network, but see the message from the title anyway.
- when using virtualization/containers for the server, use âHost networkingâ. If you use âBridgeâ instead, a layer of NAT will be inserted, which moves your server into a different network than your local clients are. The server being in a different network is considered âremote accessâ.
- Verify that you are not affected by âDNS rebinding protectionâ. Because if you are, clients are not able to use secure connections in your local network. https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections#toc-4
- Check for other network components which could cause a split of your network. More than one ârouterâ-type device, wireless bridges, a separate Mesh router, coax network bridges etc. could all be configured to perform NAT. NAT should only be performed in your main internet router, and nowhere else in your home network.
- Ensure that your home network address is in one of the ranges, which are explicitly designated for private use: Private network - Wikipedia
- When using the web app, check browser features or plugins which could obscure/hide a deviceâs IP address (e.g. iOS WLAN settings, MacOS: System Settings > Privacy & Security > Local Network > Chrome/Safari)
- if you use the local web app, load it into your browser using the private IP address of your server. Do not use a domain name.