Server no longer showing up in media list and I don’t see any way to add it. Settings menu appears to be missing several options (like adding a server). Adding a server to the web interface does not appear in the docs either.
If you’re talking about a server of yours that’s gone “missing” after you reset your password:
- open the version of Plex Web that’s bundled with your server locally – you need to do that using the server’s local IP address and from within the same subnet
- if you’re on the same machine as the server, use http://127.0.0.1:32400/web
- if you’re on the same network as the server, use http://[PMS IP address]:32400/web
- if the server is on a different network / remote, you’ll need to establish a local connection, e.g. using a SSH tunnel
- go to
Settings>[Server Name]>General - click the
Sign Inbutton at the center of this settings page (next to the “this server is unclaimed…” message)
Once you reclaimed the server, it’ll also show up in the navigation of your Plex clients (incl. Plex Web while you’re not using the local URL).
If you’re talking about something else… you cannot simply “add” other servers to your apps. Your friends can share their libraries with you or you can host your own server.
I’ve had this hosted docker server for 4 years and don’t recall having to ssh in. I would just browse to the server /web and claim it. And even when its fallen off, the server still appears (which i guess is why it appeared that setting options were missing). Further its still listed under authorized devices. Is ssh’ing new?
is there a way to do it without ssh’ing?
Can you remote desktop into the server?
no. I’m able to ssh into a different container on the network and ping it.
What does Claim | Plex do? Can i paste in a claim code?
If you can SSH into that container, and then use that connection to access the server it should do what you need.
An experimental tool is Server credential reset utility for Linux-based platforms
ssh isn’t installed on the plex container. 
Somehow I’ve done this without ssh.
For my first thought, as long as you can fake being on the same network (via ssh/port forwarding). IE being at Container 2, you can then just pull up the web interface and log in as if it was a local sever.
just found the docs from my hosting provider that says i should just be able to paste in a claim code, but that’s not working. Neither is port forwarding (but I’m probably doing that wrong and I shouldn’t have to do it anyway).
Other than the web, do you have any way to get terminal access on the docker containing plex?
no, but what I’m saying is I’ve never had it and I’ve never needed it. I’ve also found docs on several other hosting providers and they all use the claim code method. Has Plex disabled claim codes after the breach? And I was able to add my local server like you describe. Its so weird because I’m on the remote server and can see the settings and see my account. I even tried in incognito. Thanks for the help, but I give up.
@phiz314159 Dont give up, wait till next week, someone from Plex should be able to help you. Its the weekend so they are not really around.
I have a few questions:
- You can SSH to the host ?
- You can see where the real files, specifically ‘Preferences.xml’ is in the file system?
( look at where/configmaps to. Under that directory, findLibrary/Application Support/Plex Media Server/Preferences.xml)
If you can do this from the SSH, completely independent of the container,
then the utility I have will work for you too.
It is invoked, while a root user, by:
./UserCredentialReset -p "/external/path/to/Preferences.xml"
This bypasses host detection.
It does confirm PMS isn’t running as well as you’re running as ‘root’.
(running as root might be something I can forego in specific cases – needs considering and investigation)
Additionally, if you want to make it a single operation:
./UserCredentialReset -p "/external/path/to/Preferences.xml" PASTE_CLAIM_TOKEN_HERE
(remember, the claim token has a 4 minute life so don’t waste time… prepare first then get the token – paste it on the command line – hit enter.
I didn’t give up. I just took a break. But I finally figured it out. Here is the deal…
After the breach, Plex instructed you to change your password and disconnect your devices which drops your servers. It also leaves the last claim token behind (in the xml file referenced by @ChuckPa ), so the normal web form for claiming a plex server from a docker container never loads.
The solution is to get on the same network as the container, as you guys had suggested, but rather than do the ssh forwarding thing, its easier to get a claim token from Claim | Plex and then to include it in this curl command:
curl -X POST 'http://plex.server.ip:32400/myplex/claim?token=claim-xxxxxxx'
inserting your plex ip and claim token in appropriately.
This also does not require ssh access to the actual plex container. Voila! Server reclaimed.
One question: How do you claim a server which is already claimed ?
That shouldn’t work. If means I could steal your server , right?
Perhaps that’s why its not better documented, lol.
I thought the same thing. It seems like a security hole, but you’d have to be on my local network, so that’s a barrier.
Probably something the security team should test, but I don’t have ssh access to my container, so I’m glad this worked.
Interesting. So it only works when on the same local LAN.
Clever. I wonder if that’s what Plex/web uses when it claims the server ??
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
