A change is coming along in a future version of Plex Media Server whereby the hostname returned by uname -n will be treated as local and coupled with the local server IP being in the List of IP addresses and networks not requiring auth should allow it through without authentication.
If you search for the error you found in the log, you should be able to find the other forum topics on this
I have multi network with Vlan eg: Vlan1 172.168.5.0/24 Vlan2 172.168.10.0/24 Vlan3 172.168.15.0/24
My plex server it in Vlan1 and I put in the List of IP addresses and networks not requiring auth 172.168.5.0/24,172.168.10.0/24,172.168.15.0/24 and no browsers, chromecast, iPad works in all Vlan (Vlan1, Vlan2 and Vlan3) always ask connection login.
With Version 1.0.3.2461 it works perfectly.
@testpatatepoil1234 said:
I have multi network with Vlan eg: Vlan1 172.168.5.0/24 Vlan2 172.168.10.0/24 Vlan3 172.168.15.0/24
My plex server it in Vlan1 and I put in the List of IP addresses and networks not requiring auth 172.168.5.0/24,172.168.10.0/24,172.168.15.0/24 and no browsers, chromecast, iPad works in all Vlan (Vlan1, Vlan2 and Vlan3) always ask connection login.
With Version 1.0.3.2461 it works perfectly.
Thank you for the info
Please enable both debug and verbose logging on Plex Media Server
Save changes and restart the server
Then try to access from within the allowed networks and get the Plex Media Server.log and please attach
I’ve noticed this too. Considering it occurred with the same update on android that forces you to pay even if you’re VPN’d to your home, I’ve concluded that Plex is looking to start requiring a plex pass even if you don’t require their service to connect you to your own network.
I can’t even connect to the web player in my own house via hostname anymore with the latest update, it catches IPV6 and thinks its out of the house and attempts to force a login.
I don’t get the money grab, plex? Some of us are more than capable of routing our own internet traffic to our own network. I don’t need any help there.
@ewoliver said:
I’ve noticed this too. Considering it occurred with the same update on android that forces you to pay even if you’re VPN’d to your home, I’ve concluded that Plex is looking to start requiring a plex pass even if you don’t require their service to connect you to your own network.
A Plex Pass gives access to additional features. Having a plex.tv account to authenticate does not mean you need a Plex Pass. A plex.tv account is free
@ewoliver said:
I can’t even connect to the web player in my own house via hostname anymore with the latest update, it catches IPV6 and thinks its out of the house and attempts to force a login.
With hostname currently you have to authenticate. A change is coming along to change this when coupled with the local server IP being whitelisted in the List of IP Addresses and networks not required to auth. This will be based on what uname -n or equivalent returns - there are a couple of forum topics on the subject
@ewoliver said:
I don’t get the money grab, plex? Some of us are more than capable of routing our own internet traffic to our own network. I don’t need any help there.
You can’t even open the android app now without signing in with a plex pass or paying $4.99 to not have to sign in.
And no whitelist has ever been required until the latest update on my server. I’ve rolled back and everything works as expected now.
until now, whether from vpn or local network, server.active_directory.publicdomain.com:32400/web always pulled up the server. Now that is only possible by localhost or the IP directly.
@ewoliver said:
And no whitelist has ever been required until the latest update on my server. I’ve rolled back and everything works as expected now.
until now, whether from vpn or local network, server.active_directory.publicdomain.com:32400/web always pulled up the server. Now that is only possible by localhost or the IP directly.
IMPORTANT: With the security changes in version 1.1.0, if your Plex Media Server is signed in to a plex.tv account, then all of the apps you use must also be signed-in. If you use older apps that cannot authenticate (e.g. LG’s MediaLink or SmartShare apps), you can add the IP address of the device to the following advanced preference: Settings > Server > Network > List of IP addresses and networks that are allowed without auth. (We strongly encourage apps to be signed in for improved security and enhanced functionality.)
No purchase was required for Android until the latest update pushed to the play store (at least on my Nvidia Shield).
My server has never been signed in. It always asks me to claim it, which is kind of annoying. I’ve never had a plex pass. I have an account but don’t use it for anything.
@testpatatepoil1234 said:
I have multi network with Vlan eg: Vlan1 172.168.5.0/24 Vlan2 172.168.10.0/24 Vlan3 172.168.15.0/24
My plex server it in Vlan1 and I put in the List of IP addresses and networks not requiring auth 172.168.5.0/24,172.168.10.0/24,172.168.15.0/24 and no browsers, chromecast, iPad works in all Vlan (Vlan1, Vlan2 and Vlan3) always ask connection login.
With Version 1.0.3.2461 it works perfectly.
Thank you for the info
Please enable both debug and verbose logging on Plex Media Server
Save changes and restart the server
Then try to access from within the allowed networks and get the Plex Media Server.log and please attach
From your log:
Sep 08, 2016 08:15:55.031 [2440] ERROR - Illegal whitelist covers multiple WAN IPs
I don’t know why PMS thinks those IPs are WAN rather than LAN, but it’s undoubtedly throwing away the whole list of allowed addresses because of it.
I’m glad that Plex has decided to allow us a whitelist at all but Plex has created several problems for its customers by attempting to “supervise” what we’re allowed to whitelist. They should stop this entirely and simply allow it to work for any addresses specified. If they want to pop up a warning about what they think might be a problem fine, but don’t actually block it from working.
People setting up a private media server in their homes are going to tend to be a highly technical lot. We don’t need help setting up or securing our home networks. Make the defaults anything you like, just let us change them to what we know is right for our network.
@jfconde said:
From your log:
Sep 08, 2016 08:15:55.031 [2440] ERROR - Illegal whitelist covers multiple WAN IPs
I don’t know why PMS thinks those IPs are WAN rather than LAN, but it’s undoubtedly throwing away the whole list of allowed addresses because of it.
I’m glad that Plex has decided to allow us a whitelist at all but Plex has created several problems for its customers by attempting to “supervise” what we’re allowed to whitelist. They should stop this entirely and simply allow it to work for any addresses specified. If they want to pop up a warning about what they think might be a problem fine, but don’t actually block it from working.
People setting up a private media server in their homes are going to tend to be a highly technical lot. We don’t need help setting up or securing our home networks. Make the defaults anything you like, just let us change them to what we know is right for our network.