@OttoKerner said:
@ourcontact said:
Then I found "Settings - Web - General - ‘Allow Fallback to Insecure Connections’ = was set to “Never” instead of “on same network as server”.
Perhaps this got reset to Never on an update? Not sure when using the local FQDN started having these issues but all is basically good now.
This preference is stored in a Cookie in your browser. You might want to make sure this cookie “survives” a browser cache cleaning.
Don’t know what to say here, no browser cache has been cleared and it was an issue in multiple browsers as well as incognito mode, After I made the change all browsers had the change. Anyway it is good now and I know where to look if it happens again.
As to why use this local domain name instead of plex.tv? Well I shouldn’t have to, but there was a level of perceived ease of use and understanding from others in the house.
It only affects the use of plex web. All other types of Plex clients don’t require input of an URL.
And you can give your users browser bookmarks or shortcuts on their desktop as well
or change the URL on your intranet landing page to the one I gave you above. (this will also ensure that your users are always using the latest web app version)
Understood, “the bookmark” is my home LAN webserver page, don’t need more dang bookmarks 
I’ll think about changing the redirect, appreciate the advice.
it seems even using the IP doesn’t always end up secure, haven’t tracked that one down.
Using the IP won’t get you a secure connection, because the certificate is not valid for a private IP address. It is only valid for the subdomain on the plex.direct domain, your server gets assigned automatically as soon as it is started and connects itself to plex.tv
well it did… maybe some “magic” redirects going on in the background, but it appears to be locked sometimes when accessing via IP - see attached screenshot…
Also I am still getting Indirect from Plex.TV so I need to keep reading to try to see if there is something going on there.
‘Indirect’ is battled with the solutions I discussed in the thread https://forums.plex.tv/discussion/comment/1400116/#Comment_1400116
Got it, I had updated my post with the result of needing to whitelist DNS Rebinding.
After making these configuration changes, you must restart
(in this order and with plenty of time inbetween)
- your router
Nope, haven’t rebooted my router for days, able to add uPnP service, update whitelist, etc. no reboot necessary.
- your Plex Server
Maybe for something, I did a ‘service plexmediaserver restart’ once early on when testing, but I made scores of changes back and forth after that and most changes went into effect immediately.
- your clients
I did do a lot of browser reloads to see if anything changed.
If you don’t restart, the changes won’t get into effect.
Changing the ‘Secure Connections’ preference requires also a Server restart, btw.
I could make this change and see the results without me restarting the server, perhaps it is restarting itself.
(I am not using a Windows server if that matters)
Thanks again, your link in first post gave me all I needed, just took me a while to work through it all.
