Server Version#: 1.19.3.2852 - plexinc/pms-docker:latest
Player Version#: 8.1.0
Network = Bridge Mode.
DNS = Google
/config partition = configured and tested.
Preferences.xml = found and have been updated by plex successfully with PlexOnlineToken
Do you use the PLEX_CLAIM parameter as documented here?
https://hub.docker.com/r/plexinc/pms-docker/
Hi, Coxeroni,
Thank for you attention.
I have claim it with the GUI and works perfectly.
PLEX_CLAIM works only 4min = once, this is exactly as far as I get now.
The real problem accrues after the restart of the container -> unclaimed.
Obviously it doesn’t work perfectly 
So do you use the Plex claim parameter or not? The reason I ask is, I am using it and never had this problem and also didn’t need to claim via web.
Obviously yes! But I don’t understand why???
This solution provides is an initial claim and the initial client works.
To be sure that I not wrong, I have tried PLEX_CLAIM as parameter and it’s delivered as expected the same results.
The real problem accrues after reboot.
The only possible conclusion is the claim is not reboot persisted! And my question is and why is that so?
According to my investigations the PlexOnlineToken tag in Preferences.xml is key to success and this have been updated by plex in this file.
According to my knowledge this far: Every requirement to work is set but it still doesn’t. Ufff
My checks that I have done until now:
I cannot help you further I guess, I am a docker user but not an expert.
The PLEX_CLAIM should only be required on the initial docker run, after that it is claimed.
Sounds suspiciously like the permissions of your /config folder are not setup properly. Use the plex id id plex on the NAS to get the values for the PLEX_UID and PLEX_GID that way it won’t have any problems r/w files. You may need to add the plex user to docker
Thx for trying, I appreciate your effort.
Hi Tiebierius,
thx for joying the discussion.
I agree, these symptoms will perfectly fit for this kind of error.
Therefore, I make sure that the file Preferences.xml belongs to the user and group plex and any folder under the file.
No selinux can be found in the container.
The only question is what kind of permission error can possibly occur?
Besides plex is able to update PlexOnlineToken in this file .
I thought I was the only one. I am also expeirncing this on official pms docker. Never had any issues. All my clients/users can view content but my admin account can’t access the server via web.
I’m on Debian so I don’t have to mess with selinux or firewall, not currently running Plex in a docker but this is all I did previously.
Downloaded plex:
sudo dpkg -i plexmediaserver
Claimed my server http://ip_of_plex:32400
sudo systemctl disable plexmediaserver
sudo systemctl stop plexmediaserver
Add plex to docker group:
sudo usermod -aG docker plex
sudo id plex
id=998(plex) gid=998(plex) groups=998(plex),107(render),997(docker)
docker run file
docker run \
-d \
--restart unless-stopped \
--name plex \
--network host \
-e TZ="America/New_York" \
-e PLEX_UID=998 \
-e PLEX_GID=998 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /var/lib/plexmediaserver:/config \
-v /plex:/data \
-v /plex/transcode:/transcode \
--device /dev/dri:/dev/dri \
plexinc/pms-docker:public
Done.
There is no permission issue.
To prove my theory:
I enable in the container the bash shell for the user plex.
Run a shell as user plex.
Go by head to this file. Read it, change it, make a backup of it an restore it.
All works.
Problem solved by magic after update to version 1.9.4.2902.
I don’t understand why it works, but I’m happy that it does.
Thanks for help!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
