Continuation of Frustrated by Password Reset - #17 by FordGuy61 . I get claimed 0. I have plex running as a docker container. I am using the https://account.plex.tv/en-GB/claim to get a new claim which i then enter into my docker compose. I stop the container, and start it again, but, I still cant see my media, and no server is recognized. The docker image is the official plex image. No idea what to do next. All of this started after the password reset that was suggested after the plex hack.
I moved your post to the docker section of the forum.
From previous thread:
Point a browser at the Plex server: http://<ip address>:32400/identity . You should see a line of XML containing claimed="0" (unclaimed) or claimed="1" (claimed).
If you cannot claim the server via http://:32400/web, then try the User Credential Reset utility.
The Readme on the Github page has information on how to use with Docker containers.
I do not use Docker for Plex and am unfamiliar with the details of doing so (why I moved your post from a more general thread). Others should be able to provide more details.
I’m sorry, but, I prefer not to use tools to do any authorization/password related stuff from the internet. If there is a plex tool, I would use it, but.. i dont think there is.
It is written and supported by @ChuckPa. He is a contract employee for Plex and creates all the packaging for all Plex Linux distributions. You can find his posts all over the Linux and NAS sections of the Plex forum.
Since the script is his intellectual property and he is not a full time Plex employee, it cannot be published on a Plex website (Plex corporate rules). That is why it is on GitHub.
See this post: One NAS say"claim" other "Not authorized" after password reset- "PlexData" path in docs seems wrong - #5 by dane22
User Credential Reset clears information from preferences.xml, retrieves new information from plex.tv, then inserts it back into the preferences.xml file. You can download and inspect it yourself.
FWIW, I ran it on my Synology NAS and Ubuntu PC and it worked without a hitch. There’s nothing sneaky or nefarious.
If you do not wish to use it, see Why am I locked out of Server Settings and how do I get in?. That will remove four entries from preferences.xml, unclaiming the server. Then try re-claiming the server.
1 Like
May I be of assistance here?
First, thanks for your help here! I think one of your solutions would have solved this for me. I finally went with a solution that was simple enough for me to understand, attached here. Both the server and the client are functioning.
As I run plex in a docker container, I cant run anything in the plex container itself. Other containers let me login, but, the plex container has this disabled somehow.
In the end the bitter-sweet feeling is a combination of why a password reset should require a server claim (hardly user friendly), and the immediate support I received from you on the forum. Thanks!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
