I have a headless Windows PC which I use as a Plex Server.
I have not upgraded it for a while because it seems that every time I upgrade I either lose function for the whole interface changes often with detrimental aspects like DISCOVER and LIVE which I do not want or need.
Now I read that I have to claim my server?
I am not clear what this means, as usual there is huge documentation but with too much information and said information does not answer the key questions.
My biggest concern is that my server is truly headless, if “claiming” means I have to log in every time I use it then that will not be possible and I will have to find an alternative to Plex. My Server is Win10 and is turned on and off via Alexa, I have configured windows so that this is not an issue. I use a plex service so nobody is logged in to a user account.
I really do not understand this “claiming”, it sounds like another data grab.
People have made posts saying that they are losing their mind trying to do this “claiming”, When I look at the documentation above it seems that whatever claiming is or was, it has changed causing even more problems.
The statement makes this oxymoronic comment saying it will be simpler but then says simply “opening the local, bundled Plex Web client will no longer give access to claim the server”.
“Servers will now, by default, need to be claimed (i.e. signed-in to a Plex account). Coinciding with this new requirement, we’re also making some changes to the process for claiming a server. Due to this, the old method of claiming a server will no longer work (simply opening the local, bundled Plex Web client will no longer give access to claim the server). We’ve simplified the process of claiming a server, as explained below.”
Then it tries to justify this “claiming” by suggesting it is “intended to provide both security and user-experience benefits”
Well I have never used this, never had any security issues and am not feeling any user experience benefits. Let me break this down
The new claiming experience happens without having to load any third-party web pages, which avoids encouraging users to treat potentially-untrusted, insecure servers the same way they’d treat trusted Plex domains. This reduces phishing risks.
Currently I don’t have to load any 3rd party webpages, so I am not encouraged to treat potentially-untrusted, insecure servers the same way they’d treat trusted Plex domains. SO THERE IS NO PHISHING RISK
previously, if a server became signed-out (whether due to intentional user action, a bug, or malicious attack), the server would default to an insecure state that was more vulnerable to certain classes of exploit. The new behavior ensures the Plex Media Server never enters an insecure state in this way.
My server is rebooted several times a day, it is mostly off and only used for a short period as I might if I switch from Apple TV to Plex. I save power by using Alexa to turn it off.
I want it to JUST WORK, it is intentional, it is secure, the only reason is ever needed internet access was because PLEX wanted to add paid for services. It is not insecure, it is in it’s own private network with no access, although I do now want to share a library.
Today I heard that I now have to ENABLE remote access (which means opening ports on my routers) in order to share a library, that action would compromise my network. I don’t know what Plex means when it says an “insecure state” when all I want is a “set and forget” solution, something I have had for years.
* The old default requires a number of internal security mechanisms to behave in insecure ways by default, which can lead to security brittleness. Once it’s rolled out across all platforms, the new behavior will allow us to tighten internal infrastructure to be as secure as possible in all cases.
What the hell is “security brittleness”, honestly try to search for it online, it sounds like some psuedo blah invented to make you do something to achieve the very opposite of security.
Why is it called “claiming” if it means I need to log in every time I start my server then what about the plex service (created by a Plex User), does that count.
Imagine if every employer who has a server that just works when rebooted required some sort of login before it worked. If it is NOT logging in then what on earth is it?
If it is some sort of one off registration, then why is that not done when Plex is first installed and why not call it registration. I do not know how registration could not be done, I created a dedicated account for my server because I did not want the server to have viewing preferences and all that BS, I just wanted it to SERVE.
Honestly I have versions of Plex I ran more 15 years ago that did not make life so complicated, they did not need to be logged onto the internet, except when gathering images and reviews online for my library films and series.
Most of my content was converted from DVD years ago, it took ages and I am glad it is done, occasionally I buy or obtain DVD’s via freecycle and add them to my server, that used to be the only time I enabled internet access. Other devices in my home which are on a VLAN could access my server with no issue, now it all seems to be going horribly wrong.
Am I best to actually rollback my install to a very old version of Plex or should I look for an alternative? If so what?
Server Version#: Win10
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
