I use plex web app (version Version 3.2.0) and the newest Chrome as a browser.
My plex server is always listed as remote, which leads to constant transcoding.
Even though i am in the same LAN.
If I use an earlier version of plex web app (e.g. 2.12.9) this works fine.
Is this a bug or am I missing something?
Thank you
Are you on the same subnet as your server or on a guest network in your house that may use a different subnet?
Is the client wireless?
Settings - Web - General
‘Allow Fallback to Insecure Connections’ = “On same network as server”
Afterwards, reload the web page
more info here
@cayars said:
Are you on the same subnet as your server or on a guest network in your house that may use a different subnet?Is the client wireless?
I am in the same subnet. in the same LAN. it is not a wireless client.
I am using a Laptop with direct wired connection to the same router.
My web player is set to ‘Allow Fallback to Insecure Connections’ = “Always”
@jesse000 said:
And what does your server say under
Settings - Server - Network - ‘Secure Connections’ ?
If it is “required” there, the web client is not allowed to ‘fall back’.
And yours says?
@cayars said:
And yours says?
Whoopsy, my mistake!
I edited instead of replying. 
@jesse000 said:
My web player is set to ‘Allow Fallback to Insecure Connections’ = “Always”
And what does your server say under
Settings - Server - Network - ‘Secure Connections’ ?
If it is “required” there, the web client is not allowed to ‘fall back’.
@OttoKerner said:
@jesse000 said:
My web player is set to ‘Allow Fallback to Insecure Connections’ = “Always”And what does your server say under
Settings - Server - Network - ‘Secure Connections’ ?
If it is “required” there, the web client is not allowed to ‘fall back’.
Under Settings - Server - Network - ‘Secure Connections’ it says ‘Prefered’
And under Settings - web - General - Allow Fallback to insecure Connections it says ‘On the same network as server’
I’ll just mention that Plex has hardcoded knowledge of RFC1918 addresses (192.168.0.0,/16, for example) and it assumes that any server addresses outside these ranges are not “nearby”.
@kochhaus said:
I’ll just mention that Plex has hardcoded knowledge of RFC1918 addresses (192.168.0.0,/16, for example) and it assumes that any server addresses outside these ranges are not “nearby”.
Good idea!
@jesse000 which server address are you using for your internal network?
Another thing to try: Disable ‘Secure Connections’
(restart server afterwards and after a few minutes the client(s) as well)
@kochhaus said:
I’ll just mention that Plex has hardcoded knowledge of RFC1918 addresses (192.168.0.0,/16, for example) and it assumes that any server addresses outside these ranges are not “nearby”.
My Pley server IP is within that range
@OttoKerner said:
@kochhaus said:
I’ll just mention that Plex has hardcoded knowledge of RFC1918 addresses (192.168.0.0,/16, for example) and it assumes that any server addresses outside these ranges are not “nearby”.Good idea!
@jesse000 which server address are you using for your internal network?
Another thing to try: Disable ‘Secure Connections’
(restart server afterwards and after a few minutes the client(s) as well)
I am using this local IP: http://192.168.178.58
My Plex server is correctly detected as ‘nearby’ if:
- if I acces the locally hosted website/ web app.
- if I disable secure connections entirely
It does not work though, if I enable secure connetions and if I go through ‘app.plex.tv/web/app’
@jesse000 said:
I am using this local IP: http://192.168.178.x
OK, this is perfectly fine and in a reserved IP range for private networks.
My Plex server is correctly detected as ‘nearby’ if:
- if I acces the locally hosted website/ web app.
- if I disable secure connections entirely
It does not work though, if I enable secure connetions and if I go through ‘app.plex.tv/web/app’
This tells us that it must have something to do with either ‘DNS rebinding protection’ or ‘DNS resolution’. (or both)
steps 3a and 3b in my first link above apply then
@kochhaus said:
I’ll just mention that Plex has hardcoded knowledge of RFC1918 addresses (192.168.0.0,/16, for example) and it assumes that any server addresses outside these ranges are not “nearby”.
Sorry to sidetrack but curious if Plex handles the other two non-routable ranges the same way?
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
@jesse000 what happens if you go to http://www.t1shopper.com/tools/port-scan/
Input your public IP address and put in the port you are using (eg 32400). Does it say OPEN?
@cayars said:
Sorry to sidetrack but curious if Plex handles the other two non-routable ranges the same way?
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
Yes, it does.
Cool thanks!
@cayars said:
@kochhaus said:
I’ll just mention that Plex has hardcoded knowledge of RFC1918 addresses (192.168.0.0,/16, for example) and it assumes that any server addresses outside these ranges are not “nearby”.Sorry to sidetrack but curious if Plex handles the other two non-routable ranges the same way?
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16@jesse000 what happens if you go to http://www.t1shopper.com/tools/port-scan/
Input your public IP address and put in the port you are using (eg 32400). Does it say OPEN?
The Port is Open according to1shopper.com
@OttoKerner said:
@jesse000 said:
I am using this local IP: http://192.168.178.xOK, this is perfectly fine and in a reserved IP range for private networks.
My Plex server is correctly detected as ‘nearby’ if:
- if I acces the locally hosted website/ web app.
- if I disable secure connections entirely
It does not work though, if I enable secure connetions and if I go through ‘app.plex.tv/web/app’This tells us that it must have something to do with either ‘DNS rebinding protection’ or ‘DNS resolution’. (or both)
steps 3a and 3b in my first link above apply then
As a workaround, I used DNS rebinding protection for ‘plex.direct’. I set this up quite some time ago. But it’s still active.
Could that have anything to do with it?
@jesse000 said:
As a workaround, I used DNS rebinding protection for ‘plex.direct’. I set this up quite some time ago. But it’s still active.
Generally, the protection from DNS rebinding is a good thing. Only the Plex ‘secure connections’ fail to function if DNS rebinding is not allowed for the domain plex.direct.
So yes, if you created an exemption before, keep it active.
Have you tried to set the DNS server from your local network to Google? (8.8.8.8)
