Server Version#: 1.18.3.2129
My network subnet is slightly different: 196.168.192.0
I tried the following: allowedNetworks="196.168.0.0/24"
I am getting the infamous Illegal whitelist covers multiple WAN IPs error.
This is the Freenas Plex plugin that runs in a jail.
Network connectivity from the shell in this jail runs nominal.
Am I missing something?
Thanks in advance for any replies, pointers, tips.
Roy
Do you actually own that IP subnet assigned to Fibergrid in South Africa? Or did you arbitrarily decide it would be a good idea to not use a subnet from RFC1918 allocated space?
My money’s on “I mixed up my numbers and my subnet is really 192.168.196.0”.
You lost your money.
roy@globe ~ % ifconfig|grep inet|grep -v inet6|grep -v 127
inet 196.168.192.4 netmask 0xffffff00 broadcast 196.168.192.255
Thanks for the constructive and sarcastic free feed back.
It was not sarcasm. Do you or do you not own that subnet? If you do not, that is a terrible idea to use publicly routed subnets not assigned to you for your LAN .
Plex permits whitelisting of RFC1918 networks. Other networks cannot be whitelisted.
The thread below discusses the subject in detail. The way I read it is a) it is a design decision by Plex, and b) there is no workaround.
In addition to what others have said above, there’s a very practical reason not to use publicly-routable IP addresses for your private network space when using Plex. When one of your clients attempts to find your Plex server(s), or you browse to app.plex.tv, they do so by performing a DNS lookup of an FQDN which is based on your IP address. This happens even for local connections. That FQDN comprises several bits of information:
So, a final FQDN might end up looking something like (in your case):
196-192-168-4.abcdef0123456789.plex.direct
If you were to lookup up the IP address for this FQDN, it would be 196.168.192.4. This is fine for clients on your local network since they can reach this IP address without traversing your router. However, this could pose a problem for any remote clients. As they’re not on your local network, if they attempt to connect to this IP address they won’t be able to reach your server. They’ll reach whatever lives at the publicly-routable IP address on the Internet.
In practice, I don’t think this would happen. When remote access is enabled and clients request information about how to connect to your server, they are given multiple access URLs; they are marked as local and remote. Assuming a client knows it is remote, it should use the correct URL and Bob’s your uncle. But it’s still a very good practice to use one of the RFC-1918 address spaces for your private, non-Internet routable IP network unless you have a very good reason to not do so.
[Edit: I’ve re-tested (thanks @Volts) and the bit below is incorrect; the error definitely occurs in my environment]
Having said all that, I just attempted to reproduce this issue on Linux, Mac, and Windows Plex servers running version 1.20.3.3401 and was unable to do so. That is, I added 196.192.0.0/24 to my allowed networks, saved it, and watched my logs for the reported message for several minutes.
Allright. I will spend the weekend changing the IP addresses on my network to to conform to RFC-1918 standards.
I am running Plex Server as a FreeNAS plug-in. Weird that it works for you on Linux, Mac & Windows.
Thanks for the explanation though.
Roy
Good example. In addition to other clients, this would also affect systems in the Plex cloud, MyPlex, etc., that need to determine your PMS server reachability.
A note about subnet masks and CIDR / notation. x.x.0.0/24 includes everything from x.x.0.0 through x.x.0.255, but doesn’t contain x.x.192.0.
You need either to be specific, x.x.192.0/24, or to use a larger mask, x.x.0.0/16.
Is it possible you had a space or something else in the field? Mac & FreeBSD/FreeNAS immediately give the Illegal whitelist covers multiple WAN IPs error to me.
Oct 09, 2020 18:46:28.155 [0x80c8a2800] ERROR - Illegal whitelist covers multiple WAN IPs
Unless I used “bad” formatting:
Oct 09, 2020 18:46:40.018 [0x80c8a2800] ERROR - Error parsing allowedNetworks ' 196.168.192.024': Invalid argument
Oh, it’s definitely possible I missed something there; it was a quick test on each of them. In fact, I just tested again and indeed I immediately received the error. I’m not sure what I messed up earlier but, whatever it was, I did it three times.
My fingers did NOT want to let me type 196.168.192.0. Finger-level autocorrect kept kicking in!
No kidding. I wore my backspace key out.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
