Pms not recognised after password change

Plex Media Server Desktops & Laptops
,
1

Hi,

I’m a PlexLifeTime User since 2016 and I absolutely love the software. Unfortunately I face an issue which I’ve never faced before and I need some help:

I recently changed my password and the following problems occur since then:

Once I login to my server with my local IP on port 32400 there is no server available and I can’t even add my own server running on my linux machine. The admin configuration settings are very limited to what I used to have in the past.

Infrastructure:

  • Dedicated ubuntu 18.04 VM
  • Server Version#: plexmediaserver_1.18.8.2527-740d4c206_amd64.deb
  • Browser: Tried Opera, Firefox, Chrome Normal mode and private mode

What did I try:

I have all my data on my NAS and run the PMS on a dedicated Ubuntu VM and I don’t care about any configuration backups at all. All I want is to be able to run PMS again on a VM and add my existing server. My assumption is that there is an issue with the login credetials mapped to Plex since sometimes during logins I receive error messages.

@Plex Team, could you please reset my account or help me out that I can connect my Plex account with my local PMS and than I’ll be able to read the couple libraries?

Thanks a lot for your support.

Server Version#: plexmediaserver_1.18.8.2527-740d4c206_amd64.deb

[
{
“type”: “info”,
“host”: “10.1.1.26:32400”,
“userAgent”: “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.122 Safari/537.36 OPR/67.0.3575.53”,
“browser”: {
“platformVersion”: “10.14”,
“id”: “opera”,
“name”: “Opera”,
“version”: “67.0”,
“webkit”: true,
“platform”: “OSX”,
“platformID”: “osx”,
“platformModifierKey”: “command”
},
“version”: “4.22.2”,
“username”: “walkerjonas”,
“cloudUrl”: [
{
“scheme”: “https”,
“address”: “plex.tv”,
“uri”: “https://plex.tv”,
“testState”: “connected”,
“isBundled”: false,
“isFallback”: false,
“relay”: false,
“isUntested”: false,
“isPending”: false,
“isConnected”: true,
“isUnauthorized”: false,
“isUnavailable”: false,
“isFailed”: false,
“isAborted”: false,
“isLoopback”: false,
“isPrivate”: false,
“isHttps”: true,
“isSecure”: true,
“isPlexDirect”: false,
“currentTest”: null,
“sources”: [
{
“id”: “internal”
}
]
}
]
}
]

2

I wrote this for Synology but should work fine for everyone.

3

Thanks for the quick reply. Unfortunately that doesn’t help. I tried it already yesterday and now again. (I changed my password again: Login to www.plex.tv → settings → redirected to the app
and changed the pw there while hitting the sing-out devices radio button).

Once I login on a new fresh private mode browser with the new password PMS fails to realise that I PMS is already running and asks me to download the software again?

image
image951×526 115 KB

What’s interesting when I try to login in Firefox then I get a error message. With Safari, Opera and Chrome I can login and face the issue in the screenshot above with Firefox I get this:

image
image733×685 71.4 KB

If I go to my forum account and logout there:

image
image557×234 8.99 KB

And then do the same steps you mentioned in the FAQ then I get the “no soup” message

image
image1549×323 108 KB

4

Your screen shots show your Plex/web was SIGNED IN while looking for the server (look at your avatar in the upper right).

You need to be signed out in this scenario. You want the unclaimed / unassociated server to be found first.

If you are signed in, plex/web will only look for what it already knows.

5

I followed this tutorial from your link above (see below). Up to step 7 I’m not signed in so once I’m on my local IP:32400 it asks me to sign in and that’s what I do. So how am I supposed to claim the server without being signed it before? Step 7 looks like this:

How should I claim the server without being logged in?
Thanks

Begin here:

  1. Sign out the plex/web browser
  2. Open a new Window
  3. Go to to www.plex.tv (not app.plex.tv)
  4. Sign into your account settings.
  5. Force sign out everything as you change the password.
  6. Open an incognito window
  7. Open http://ip.addr.of.host:32400/web (or 127.0.0.1:32400/web if on the host)
  8. Sign in
  9. Claim it again.
1 Like
6

See the app.plex.tv URL redirect? The server still thinks it’s part of your account.

did you REMOVE it from Authorized Devices -> Servers?

Are you and the server both on the same subnet ?

7

Yes I see the redirect and no matter what I do it always happens. So far I wasn’t on the same subnet I logged in via VPN. This might have been the issue. I was able now to login and claim the server, never the less there were some redirections to app.plex.tv.

Here is what I just did right now which is the solution for my problem:

  • I logged in into PMS and removed every single entry from authorized devices.
  • Connect to my windows VM in the same subnet as plex (never connected to plex before from this VM)
  • Download Firefox (never used Firefox before on this VM)
  • Go to to www.plex.tv (not app.plex.tv)
  • Settings -> redirects me to app.plex where I change the password + hit the force logout radio button
  • sign out from app.plex
  • confirm with connecting to plex.tv --> i’m logged out
  • use my host computer (non rdp vm) to login again to remove this firefox (from vm) again from authorized devices
  • go back to rdp windows vm (which is in the same subnet) with fresh firefox browser and open a private browser
  • go to 10.1.1.26:32400/web and it redirects me immediately again to app.plex.tv like the last screenshot but after the login I was able to claim the server

Well, it’s a bit unfortunate that a single password change leads to such a mess but on the other hand the support from ChuckPa was very good. Thanks a lot, appreciate it.

1 Like
8

I think I see the root cause. I logged in via VPN.

Can’t do that. It detects and uses the Referrer IP – which probably isn’t on the same subnet, is it?

When not on the same subnet. SSH tunnel to 127.0.0.1 is by far the simplest solution. It works every time without fuss or fail.

1 Like
9

probably that was the issue indeed. thanks.

10

Thanks for your feedback. I will add that to the cautions in the procedure.

It’s ridiculous to be such a fiasco

11

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.