I have just noticed that when access plex via a browser (I have tried IE11 and Chrome) it is streaming stuff by going out over the Internet! My server is on the same network as the PCs in the house.
My Roku’s are all fine and connect correctly internally, but the web browsers do not. Which means I get stuttering as my server is uploading everything to the Internet for my PC to download it again which is obviously ridiculous.
If I disable remote access on the server then the browsers work as expected and traffic is all internal. However that means I can’t access my stuff when I’m away which is no good…
Using PMS 1.2.7.2987 on a Windows box
That’s a very old version of Plex server. Any reason why you haven’t updated?
Basically newer versions break the xbmcnfoimporter third party scraper.
Ok, I figured out a work-around…
If I browse to the server using its IP address, it connects as in internal client and works as expected with all traffic being local to the internal network.
Pointing my browser to http://192.168.1.21:32400/web/index.html - works as expected as a client on the LAN
If I browse to the server via it’s DNS/NetBIOS machine name Plex then seems to think it sits outside the network and all streaming is done over the DSL connection and back in again…
http://vm-cronos:32400/web/index.html - Plex thinks is a WAN connection.
Pinging vm-cronos results, as expected, in it’s IP address of 192.168.1.21
What is going on? Or is it a case of Plex not being clever enough to resolve the machine name and realise it’s internal? I am sure this hasn’t always been the case, and I haven’t modified anything in my setup for a couple of months now and it worked OK before.
I have of course tried the usual stuff of turning it off and on again, signing in and out etc.
@AndrewUK said:
If I browse to the server via it’s DNS/NetBIOS machine name Plex then seems to think it sits outside the network and all streaming is done over the DSL connection and back in again…
http://vm-cronos:32400/web/index.html - Plex thinks is a WAN connection.
Pinging vm-cronos results, as expected, in it’s IP address of 192.168.1.21
You should not use an own domain name. Just bookmark the IP address.
What happens is probably this:
when you use the domain name, the browser treats this as a different website than 192.168.1.21
Each website has its own cookie, and therefore a separate set of preferences
(Everything you tweak under Settings - Web)
If you don’t allow Plex Web to fall back to an unencrypted connection,
(Settings - Web - General - ‘Allow Fallback to Insecure Connections’)
it can only switch to the public connection over the internet - because this has a valid cryptographic certificate.
Your custom domain name has not a matching certificate.
The private IP address is made valid by a mechanism called “DNS rebinding”, btw.
https://support.plex.tv/hc/en-us/articles/206225077-How-to-Use-Secure-Server-Connections
If you disable Secure Connections on the server, it will work as it did with older server versions.
