I will come back to this post and include the version…
On a new server setup I was unable to get the ‘Server Setup’ button to magically appear, unless I accessed the new server by IP. As I now understand, this is ‘normal behaviour’.
There should be a warning displayed for this bug, or better yet, fix the bug.
Server Version#: 1.18.1.1973
Player Version#: All so far.
Not a bug at all an intentional design feature. Really can’t fault plex if you didn’t read the installation instructions https://support.plex.tv/articles/200288586-installation/ under the section Opening the Plex Web App on a Device Other than the Server Itself.
Blame the user - seems like Plex is taking a page from the Apple playbook here. This is a bug. Anyone that sets up plex servers for specific purposes (as is now required because of all the other plex bugs), will probably have this issue.
The guide mentioned will probably not even be looked at by most folks that have been using plex for years.
Thankfully Emby does not have this problem.
Since you want to define design decisions as bugs because they do not match the way you would design it, sounds like Plex is not for you. Enjoy Emby.
Before this becomes any more polarized and I need speak louder,
The use of IP is required because of:
a. Confirmation of referrer IP
b. When using a hostname, particularly a FQDN, PMS has no knowledge of the trust level of that name.
Using either 127.0.0.1 / localhost , either directly or via SSH-tunnel, authenicates the connection as being by the owner (a reasonable level of certainty can be established given the connection is SSH-based (username / password).
When on the same subnet, the above conditions are somewhat relaxed but the Domain Name in use must be consistent with the spec for home .LAN / .LOCAL usage.
Thanks for the explanation.
A simple warning to the user when accessed via anything other than IP that certain functions are not possible, and to use IP, should be easy to do.
I’ve just had to delete the profile from 4 clients entirely, in order to get them to work with a new server, and I"m not in a particularly forgiving mood.
Manual selection of different servers should be an easy thing to do, and it is not. That in conjunction with this issue - which if you google it’s easy to see that many users have had - conflates things quite a lot. I thought that there was some value in having a thread that others could find, when they don’t read the manual.
This is still very clearly a bug as the software is behaving differently whether by design or accident, and there is no way except for documentation for an end user to know about it.
This is not a ‘design decision.’ that I find acceptable. Call it whatever term makes you happy. Removing functionality based on accessed URL without notification is not acceptable. Either display a warning, or don’t allow access at all through a local fqdn. Many servers will not be accessible easily through localhost if they are headless. Many, many admins use IPs as a last resort. Managing systems by IP gets old very quickly. We live in a DNS/DHCP world and Plex needs to move into it. Thanks for allowing me to clarify this issue.
The information is published in the support pages. Support.Plex.tv
under Installation
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
