So I’ve been testing around a bit, secured connections is set to required.
If I go to another computer, open a random browser and access https://plex.tv/web and log in, everything works fine. The connection is secure and all is well.
If I try to access via my local IP-address, 192.168.1.8:32400/web (example) it doesn’t work when secured connections are set to required. It works if I change to preferred.
I’ve also added the second computer’s IP-address so I don’t have to log in, this also works fine with the preferred setting.
I know I’m on my local network and encryption really isn’t that important but still would like to why it doesn’t work. Any help is greatly appreciated.
I’m running Windows 10, I haven’t done any configuration in the router.
I just assumed https would be used by default, a silly mistake. One step in the right direction, I now get to the interface but Chrome states the that connection isn’t secure, there is a line crossing out https.
I do have the green dot with the lock next to my username, which is confusing when Chrome says it isn’t secure.
This is my understanding of things, which could be horribly wrong:
It has to do with certificates.
Chrome is using the https protocol, so Plex shows the green lock.
However, your PMS server does not have a security certificate from an accepted authority, so Chrome marks the connection as insecure.
Going through app.plex.tv, which does have the necessary certificates, makes Chrome happy.
And… we’ve just reached the limit of my knowledge on the matter.
There’s probably a way to grab a certificate from Let’s Encrypt and install it on your PMS. However, a) others will have to weigh in with the details, and b) using app.plex.tv authenticating with plex.tv servers forgoes the need for everybody to have their own certificate (my understanding anyway).
Simply use the hosted web app.
There is no good reason to prefer the local app.
If you load the local web app per http, the browser throws the warning because it cannot verify the identity of your server. That only works if you access it per domain name. You can’t use a cryptographic certificate with an IP address.
Have you tried to load the local web app per https ? It works sometimes.
