Server Version#: 1.15.1.710
Player Version#: web 3.83.1
While looking through logs for info on why Plex is choosing the software encoder for some of my transcodes, I came across these entries in my log, which I find confusing. I can’t tell if it thinks I’m local or not. I’ve also been having issues recently where it seems to think I have no access to manage my own server from local, so I wonder if this is contributing. So…am I local as far as Plex is concerned, and could this be causing the random-ish ‘No soup for you’ messages I get when I try to go in to server settings locally? I’ve never had that issue before.
Mar 01, 2019 19:09:18.776 [8000] VERBOSE - Comparing request from 192.168.1.180 against 192.168.1.0/255.255.255.0
Mar 01, 2019 19:09:18.776 [8000] DEBUG - Request came in with unrecognized domain / IP 'plex.chiefmas' in header Host; treating as non-local
Mar 01, 2019 19:09:18.776 [5968] DEBUG - Request: [192.168.1.180:51110 (Allowed Network)] GET /web/index.html (15 live) GZIP Signed-in
Mar 01, 2019 19:09:18.776 [5968] VERBOSE - * Host => plex.chiefmas.local:32400
Your custom domain names don’t have a fitting cryptographic certificate, which prevents ‘Secure Connections’ from working.
Don’t use custom domain names.
Always use the private IP address of your server to load the web app, if you don’t want to use the web app from app.plex.tv
(although there is no real reason prefer the local web app over the hosted one)
Hmmm ok…is that a new thing, some extra enforcement of certificate requirements? I’ve been running and accessing the server locally this way for years, without any issue. Also, I’m curious, why it only has part of the host name there, is that just a display thing? Because if that’s what it’s doing it’s compare with from the header, yeah that’s gonna fail to compare to anything since it’s incomplete. I can issue it a cert from my local certificate server, I just never bothered because I never had any problems referring to it by it’s local DNS fqdn before.
I have a reason, I think it’s rather unnecessary to send extra traffic up to the router that likely can be handled in my core switch. I’ll just start using the IP, I suppose. It’s too bad Plex doesn’t actually perform a DNS look up there though.
