I’ve been trialling a new version of a router from my ISP and since I have had that when I connect to plex using the https://app.plex.tv/desktop url after I authenticate I can only ever get a ‘remote’ connection to my server and bandwidth is limited.
If I connect to the local IP address then plex tells me I have a local connection and all is good.
I have been in communication with the team who are producing the new hub but so far I haven’t got a solution.
I’m running plex in an unbuntu bhyve vm on a freenas 11.2 server (HP microserver).
Should Plex pick up my local server when I use the https://app.plex.tv/desktop url and then locate my local server? That used to be the case with my old router.
I’ve been working with my ISP (I work for them anyway) with this issue and we have now verified that the new router is working in a correct way and indeed testing with the old route also displays the same behaviour.
I have carried out multiple tests and built several additional Plex servers both on a Windows machine and my Freenas 11.2 server with both a byhive virtual machine running ubuntu and a FreeNAS jail both running the latest version of Plex.
In all the tests if I connect using https://apps.plex.tv/desktop from a browser (and multiple browsers firefox, chrome, edge and on a ubuntu desktop or Windows) the Plex web page tells me the connection is remote. It I use the Windows Plex app it tells me the server is nearby. I have also used the PlexAmp client on ubuntu but I can’t tell from that how that’s connectiing.
If I use my local local ip and port from a browser, I authenticate via the plex.tv url becaus I’m redirected there but the Plex page tells me I’m connected nearby.
Please could you have another look at this for me as something about the way Plex is behaving is inconsistent and I’d like to know that whichever way I connect (url or ip) I connect locally rather plex telling me I am using a remote connection via the url and locally using the ip.
