Server Disappeared, on manually reclaiming I become Not Authorized

[zolaster]

Server Version#: v1.25.9.5721-965587f64

The beginning of my problems was when I tried changing the mapped public port for my server. Then I read up on what the setting was actually doing and decided to change it back (back to default).

In the process of this, suddenly my Chrome web client stopped being able to see my server, could only see my friends servers. After repeated restarts and different attempts to connect with different methods and clients, I eventually decided to try to re-claim this server, thinking it must not be associated to my account for some reason.

On my linux server, I went through the steps to remove the PlexOnlineToken, PlexOnlineUsername, and PlexOnlineMail key pairs from Preferences.yml, started the server, and connected via a localhost port. I was able to see the appropriate UI, see that it was unclaimed under general. I could click claim, it asked me to login, and then it would spin for a bit, then I would get a message that I’m Not Authorized for this server. When I look browse servers, I again cannot see my server in the list. I look in the Preferences.xml, and see that the token/login info were recreate.

For giggles, I decided maybe I needed a new token, so I go and change my password and for all my accounts to be signed out. I go through the process again of removing the key/value pairs from preferences, start the server, and click claim. This time I see a new token in the file. Yet once again as soon as its done claiming, I no longer have access.

I even tried using the POST api to claim, getting a token from plex.tv/claim and using a manual curl call. This again seemed to work as expected, got a response back, and the token and credentials added to Preferences.xml. But once again, I still cannot find my server by browsing.

Finally, I went into my authorized devices, and removed my plex server there. Then went through the process to claim the server. I see my library/server show back up in the authorized devices section (indicating it was active a couple minutes ago), but again, via web or mobile or shield clients cannot browse this server.

It’s very weird that I can access the server fine while its unclaimed, but then the process of claiming it seems to remove my access.

Looking for any suggestions or help.

Thanks!

[zolaster]

I went so far as to try removing all 3 MachineIdentifier key/value pairs from Preferences.xml to see if there was something cached/registered about this plex instance, then claiming again. Still nothing (same issue where I could access it via localhost:32400, could hit the claim button, then get Not Authorized, and could see it when browsing servers).

During all of this I had also tried changing the Friendly Name of my server a few different times to see if that would help. It did not.

I tried manually editing the Preferences to put that non standard mapped port back in that was the beginning of this madness. I was able to access the server via the non standard port on localhost to try to claim it again, but once more post claiming it became not authorized and not visible.

So then I worried it was my plex account. So I downloaded PMS on my desktop and installed and created a new server, and this showed up just fine.

Finally, I tried just blowing away the Preferences.xml completely and starting and claiming the server fresh. This worked. I was able to claim the server (it was using the same database files so the libraries were intact) and it is working as expected. The unfortunate part about this is now I had to redo any settings, then also re-share the library with family, and they’ll have to do all the fun of re-pinning with the new library.

For giggles after the new server preferences was working I tried comparing them and there was nothing really different (identifiers, certificateuuid were basically the only differences). I even tried swapping my old preferences.xml back in and trying to claim again once I saw that the server/library was indeed functioning. No joy. So back to the new preferences, and I guess move on with life.

I’d still be curious if anyone has any thoughts on this and what went wrong.