Good afternoon.
I recently received an email from you with the title (Action required: Important notice of a potential data breach).
I did everything that was indicated in the instructions, but after changing the password I can not get directly to my server.
That is, authorization on https://app.plex.tv/ goes through and transfers me to my server where in any library folder it says “Not authorized. You do not have access to this server”
What could be the reason?
Thank you.
Sounds like you opted to sign out all devices while resetting your password. That includes the server. You’ll need to reclaim the server to re-link it to your Plex Account:
Thank you very much for your reply.
I’ll come home from work and try.
Thank you again for your reply.
OMG, It really did help!
Thank you very much once again!
I am also experiencing the same issue ever since the infamous Data Breach email. If I reboot my server it works for a period of time but eventually it reverts back to the “Not Authorized - You do not have access to this server” message.
I tried following the steps provided by @tom80H but I do not see the “this server is unclaimed” message under Settings>General. So the only option I am left with is to reboot which is getting really annoying.
Thank you
What are you seeing on the General settings page instead?
Right now it’s working because I rebooted. I will grab a screenshot next time I get the “not authorized” message. Thank you for your help - much appreciated.
@tom80H - Issue has resurfaced. Here are a few screenshots.
In the first one it shows the “Not Authorized” message. On the left hand side where my server name is listed I am unable to select settings from the right click menu
The second one is of my Settings > General screen which I access from the top toolbar and I do not see the “this server is not claimed” message
Well… there’s no Sign In button because there’s no server settings for you.
I’ve recently noticed that Plex might consider my server to be unauthorized if I’m waking it up from sleep and it takes a little too long to react. Does the issue on your end persist if you do a forced reload of the web app?
EDIT: Ok, I looked at my own server’s local web client. It matches yours, so you do appear to be loading the local client.
Here is a screenshot with the URL - looks like I am accessing properly through the local server
Also, I am using Chrome on a MAC Mini and did try a forced reload (Shift+Command+R) and still same result.
I think that @tom80H may be right: “Plex might consider my server to be unauthorized if I’m waking it up from sleep and it takes a little too long to react”. Right now the only way I can get it to work is by shutting down my MAC Mini completely and rebooting.
instead of rebooting the Mac… can you give it a few seconds after you get the Not authorized message, then click ⌥+⌘+R (option+command+R). This will reload the page from the source (instead of potentially refreshing it from cache). If it’s really about the web app considering your server to be not authorized because it was too slow to react, it should subsequently load ok.
Just tried Option+Command+R and it did not do anything
I also tried Command+Option+E to clear the cache and then Shift+Reload. This time it reloaded but still receiving the Not Authorized message
This has been happening to me long before the password breach and I cannot seem to find a solution either.
I am having same issue as @garybrazier. Running PMS on EX2 Ultra. Was working fine before the password reset. Tried the claim server token still not working.
Not to add onto the pile but I too am having the same problem. My PMS is just on a desktop running Windows 10. I have tried several “fixes” but nothing works.
Like @PigRenter I’ve lost access on my server account (have a server/client account configuration).
The owner of the server doesn’t have access to anything, but the client can still watch from it, so it is accessible.
I’m running it in the official Docker container, and I’ve tried updating the claim token, but nothing changes.
** UPDATE **
After looking at the logs I see that Plex has issues resolving some host names. One of these seems to be connected to Let’s Encrypt.
Could this just be as simple as a certificate issue? My server can ping and traceroute these domains, so it’s not on a system level, so my guess is just that a certificate issue is causing the HttpClient in Plex to refuse the connection.
Only thing I can’t figure out is why it works for other users and not the owner.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
