Cannot claim server after docker removal + reinstall and entirely removing config directory

Plex Media Server Remote Access
,
1

Server Version#:1.28.1.6104-788f82488-ls128
Player Version#:4.84.1

I get a Not Authorized error when trying to claim my plex server, after a fresh docker reinstall, and after completely removing the config/Library folder.

I have plex lifetime pass and am logged in to plex.tv with that account, i always select my primary user when logging in (the user with crown icon).

I install the docker using this command (i have tried both with and without specifying the claim token in the docker command):

docker run --name=plex --net=host -e VERSION=latest -e LD_LIBRARY_PATH=/usr/lib/plexmediaserver -e PUID=1006 -e PGID=1006 -e TZ=SAST -v /data1/telly/config:/config -v /data1/telly/movies:/data/movies -v /data1/telly/tvshows:/data/tvshows -v /data1/telly/transcode:/transcode --restart unless-stopped lscr.io/linuxserver/plex:latest

I then run an SSH port forward from my local machine to the remote machine:

ssh -L 8888:127.0.0.1:32400 user@host

I navigate in a browser to localhost:8888 where I can confirm/modify the name of the new server but am then dumped at a Not Authorized error. When using the claim token in the docker command I am taken straight to the Not Authorized error. I have also tried stopping the docker, removing keys from the Preferences.xml file as per this advice and then starting the docker again, but I get the same Not Authorized result.

I have also tried claiming the server in a browser running remotely in X over SSH but I get the same Not Authorized result.

I do see some cross origin requests and other http requests denied in the developer console network tab, so I attach the console tab, as well as the plex media server logs.

I have been having this issue for some time, have tried many, many times over the last several months - I have tried the other main docker (plexinc/pms-docker:latest) and played with various docker version options - and read various other users’ experiences with similar issues around being unable to claim their plex server after some sort of reinstall, I see others such as this one were unresolved and closed after 90 days.

I attach PMS server and web console logs.

console-export-2024-1-16_11-10-41.txt (337.7 KB)
PMS.logs.zip (66.5 KB)

2

Correction: I did not mean to include this LD_LIBRARY_PATH in the docker command, that was leftover from some previous rabbit hole.

After the third time I installed the docker today I see it did upgrade to version 1.40.0.7775-456fbaf97 so I tried removing the keys from the Preferences.xml file and then trying the claim again, it looked a little updated but I get the same error. I attach the updated server and web console logs.

console-export-2024-1-16_12-6-49.txt (158.5 KB)
PMS2.logs.zip (127.0 KB)

3

Sigh … No replies yet …

Since I last posted, I have also tried the UserCredentialReset.sh script from @ChuckPa as per this:

I stopped my docker, ran it with -p option to my Preferences.xml and got this output:

Plex Media Server user credential reset and reclaim tool (User-Defined)
 
This utility will reset the server's credentials.
It will next reclaim the server for you using a Plex Claim token you provide from https://plex.tv/claim
 
Using given Preferences path:  'Preferences.xml'
Please enter Plex Claim Token copied from http://plex.tv/claim : claim-****************
Clearing Preferences.xml
Getting new credentials from Plex.tv
Claim completed without errors.
 Username: ****
 Email:    ********** 
Complete.  You may restart PMS.

but after docker restart I get the same result.

If I go to Authorized Devices in plex I see that it recently authorized with version number and everything:

schnauzer4
a few seconds ago
1.40.0.7775-456fbaf97
Plex Media Server
Docker Container (LinuxServer.io)
Linux 5.4.0-47-generic

But clicking on the server in plex interface i still get the dreaded:

image
image1056×473 28.3 KB

4

Plex blocks Hetzner.

5

aaaaah gaaaaaaad, that explains it, thank you!

An error message in the interface or at least using a different HTTP error code other than 401 would be nice.

6

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