@michael.spam said:
confirmed, insecure allowed management.
I don’t think I fiddled around with many settings. My goal was to get it tested to see how the platform compares to XBMC/Kodi.
That is good in that it ties in with what I discovered and the bug that has just been unearthed
A fix will be out soon - not sure if it is going to be in Plex Web 2.6.2.
A number of factors affect the outcome resulting in access to the server on the same machine fails through localhost or 127.0.0.1 when the following scenarios arise:
- Server
Secure Connectionsset toRequiredorPreferred(default) - Plex Web App default setting of
Allow fallback to insecure connectionsset toNever - Pin added to the server account
- Server not enabled for
Remote Accessor Remote Access through public IP and port not working
andRouter DNS Rebinding Protectionin place making local access through TLS secure connections via local-ip plex.direct route not available
To explain - with the pin added the connection through 127.0.0.1 is failing and that will be fixed. It tires to find alternative route. With secure connections in place, it has to use one of the 2 secure plex.direcct url’s. If DNS Rebinding protection is in the router then the local ip plex.direct url fails. Only other option would be the remote access public ip and public port plex.direct url. If remote access is not enabled then this will not be available and resulting in failure to connect to the server
Until the bug is fixed - the problem can be avoided by
- enabling remote access and getting it to work
or - overcoming DNS Rebinding Protection (may be possible by adding Google DNS to the router DNS) or going for suggestions mentioned on this support page https://support.plex.tv/hc/en-us/articles/206225077-How-to-Use-Secure-Server-Connections section on
DNS Rebinding
or - changing Plex Web App setting to always allow insecure connections
