Plex Server not found - 401 unauthorised

Plex Media Server Desktops & Laptops
1

Server Version#: 1.13.2.5154-fd05be322_amd64
Player Version#: Web Player

Hi all,

For a little while one of my two servers hasn’t been listing, looking at the chrome browser console (on win10) today I found this log item, which is odd as I’m signed in with my Plex account and further signed in using my personal user pin. I’ve seen in previous similar topics that running an SSH tunnel so you can almost get local access to the web page has been suggested, I’ve tried that and am encountering the same problem.

[Connections] HomeServ-J is unauthorized at http://127.0.0.1:9090 (Status 401)
onLogMessage @ main-1-7234a6396d00ac2d746d-plex-3.69.1-91b0591.js:3212

This issue (though perhaps not the log item as I didn’t check then) has been ongoing for some time, but just an FYI that just today I upgraded to this plex server version and subsequently changed the server IP and upgraded it to Ubuntu 18 from 16. …but again there was a problem before this, but this may have further complicated matters possibly.

Any help would be much appreciated, thanks!

2

Since port 9090 isn’t a Plex port, I’m uncertain why that port would be listed in your PMS logs and why PMS would be attempting to connect to it unless you have something on your system advertising itself as a player or IGD at that port.

Does this mean anything to you? Remind you of anything installed and running?

3

Heya, I used port 9090 as the SSH Tunnel port, it’s tunnelling to the server on port 32400

4

Ah… So you’ve setup a standard SSH tunnel

ssh -L 9090:127.0.0.1:32400 ip.addr.of.host

connection to the server and then opened

http://127.0.0.1:9090/web on your local browser ?

5

Bingo, yes, as I saw you suggested that to others in the past (though I used Putty as I’m on windows to be clear).

6

One of the things which can cause 401 (it doesn’t recognize you as the owner) are any open/held over tokens in the currently open browser window.

Choices are:

  1. Sign out of your Plex account in the browser (upper right corner)
  2. Open a new browser in-cognito window to use in connecting to the remote host
7

So used the guest mode in Chrome just now, (this time not using the tunnel) and gives same messages:

[Connections] [Anonymous] is unauthorized at http://192.168.0.10:32400 (Status 401)
http://192.168.0.10:32400/?X-Plex-Product=Plex%20Web&X-Plex-Version=3.69.1&X-Plex-Client-Identifier=bu83tbfh7o4smw4b7l1c2dna&X-Plex-Platform=Chrome&X-Plex-Platform-Version=70.0&X-Plex-Sync-Version=2&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=1920x465%2C1920x1080&X-Plex-Token=QLRpb7mwHwghjvebG3ip&X-Plex-Language=en 401 (Unauthorized)
[Commands] Executing lockUser
[Commands] Executing authenticateWithServer

Not sure why it says Annonymous as the browser shows my avatar and my other server (though it’s off right now so says Unavailable).

Could it be that some keys on the server don’t match the plex (cloud) servers now or something?

8

I use chrome. Guest mode has never done anything productive because active tokens are used. It only deletes anything added / changed. (undo)

Incognito (bring nothing forward) works best.

Even better is to use a different browser (firefox is good for this)

9

I assumed Guest mode was the new incognito as I no longer see incognito when I click on my avatar in chrome, sorry, just found it now, so will try again.

10

Hmm, ok I think my key idea might be right as it might be locked to the old internal IP (10.0.0.10) see the console log below… ps HomeServ-J is the local server on 192.168.0.10 (was 10.0.0.10).

[Servers] HomeServ-J was found through plex.tv
[Connections] Access token for HomeServ-J changed to b77rbk6K16ssLqrFwbFJ
[Connections] Testing all 1 connection(s) for HomeServ-J
[Connections] Added connection https://10-0-0-10.c63edda7b1464ecaa5aa03ef57756a35.plex.direct:32400 for HomeServ-J
[Connections] Testing connection for HomeServ-J at http://192.168.0.10:32400
[Connections] Testing connection for HomeServ-J at https://10-0-0-10.c63edda7b1464ecaa5aa03ef57756a35.plex.direct:32400
[Connections] HomeServ-J is unauthorized at http://192.168.0.10:32400 (Status 401)
[Connections] HomeServ-J is unavailable at https://10-0-0-10.c63edda7b1464ecaa5aa03ef57756a35.plex.direct:32400 (Status 0)
[Connections] Prevented fallback to insecure connection for HomeServ-J
[Connections] All connections to HomeServ-J failed
11

yep. Nail on the head. Youll need to get in it, knock down the connection to Plex.tv and reestablish.

If you aren’t sharing with many people, just blast the Preferences.xml and reclaim it as if cold (just don’t recreate library sections… those survive the soft reset).

If you are sharing with a lot, rename Preferences.xml then do copy/paste surgery on it, bringing the ID fields (Machine ID , processed machine ID, etc) forward into the new Preferences.xml.

12

Is there a way to change the internal IP without it forever locking me out?

13

The existing server instance records will need be deleted (general cleanup of Plex.tv)
Once you have ‘ownership’ again, we can see what it’s looking at.

I unfortunately really do need see the logs from PMS startup and where it connects to Plex.tv to see which adapters / IPs are being selected and reported to pinpoint what will resolve this permanently for you

14

Ok, so I’ve gotten it working again now, so for anyone that finds this in the future…

  1. I changed back to the original IP the server had (though I’m not sure that’s required)
  2. I deleted the device as listed in ‘authorised devices’ in settings on plex.tv
  3. I changed the server’s preference settings and re-claimed the server using these instructions: https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/?_ga=2.5230523.986023287.1542543017-939355295.1542543017

Hope that helps!

15

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