Hello All,
i run the latest plex server in docker on Linux Debian.
After i changed my password the plex server is showing ‘Not Authorized’. And a lot of stuff in settings are missing. My library seems to be gone.
I renewed the claim token en started the docker container with this new claim token. But that didn’t help. How can i get the plex server back up and running again?
Maybe this can help you: Server credential reset utility for Linux-based platforms
I used the script but doesn’t recognize the docker installation. I will try to run it in the container itself later today.
Please post about your experiences and questions directly in the linked thread.
For the benefit of other users, too.
Yes i will. But for now i read in the post that i’m not using the official plex image for docker. I replaced the image with the original image and after that is started working out of the box again. So i haven’t changed anything i only changed the docker image and done.
My old image:
–Docker Hub (linuxserver/plex)
The new Image
–Docker Hub (plexinc/pms-docker)
My thoughts where: I have to stop the pms service in the container itself. And it seems that was not possible in the image i used. But in the image of plex itself there was a special script for that. So then i thought lets run that image and see and run the server credential reset script. But that is no longer necessary now.
Running the script in Docker – Can’t be done.
There is a design problem/race condition with how Docker works.
That having been said ------
I could modify it and take the chance (and print warnings).
My concern is PMS writing Preferences.xml right after I just fixed it.
(I could hard-stop PMS but that has database implications)
Suggestions?
Well, the preference file is available from the Docker host while the container is stopped. But you have to inspect the Docker container using Docker commands to determine the location of the preference file. I guess that is what the script is doing right? Locating the file and make changes to it? I could help you with that.
I agree, it’s easy to parse the docker spec file and figure out where things are.
The challenge is “which docker spec file and where is it?” .
That’s not doable via automation
Maybe it’s appropriate to create a “Manual Config” option?
It will ask you where things are first, verify, then go to work?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
