Server Version#:1.42.2.10156
Player Version#:4.147.1
Last night my server went down hard due to some outages. When it came back up I could not get the plex container to start up at all in my Unraid docker container. So I uninstalled the plex container and all the files I could find related to it (not the actual media files.)
I got it re installed and now every time the container reboots it looses the plex claim code. I have deleted the perms.txt, supervisord.log, prefrences.xml, setup plex.html, .localadmintoken, and plexmediaserver.pid files at different times and all at once in efforts to get a clean rebuild. Using the binhex-plex from the Unraid app store
I have also cleared all approved devices from the server as well.
No change when toggling from IPV4 and IPV6 to IPV4 only.
None of this works each time I reboot I still have to reclaim the server and re invite people to see my server. Additionally when I try to test it outside of my network its incredibly slow to access the server if it ever does. I currently cannot access it from my IOS device. Shows no servers available.
I have it on a custom port and it shows that its fully accessible outside your network and then a few minutes later it says its not ( been like this for years and I could still access it VIA relay ). Internet speed at the server is 950+ MB down and 20+MB up.
2025-12-15 16:49:09,192 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23001927637984 for <Subprocess at 23001928835696 with name claim-script in state RUNNING> (stdout)>
2025-12-15 16:49:09,193 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23001927199120 for <Subprocess at 23001928835696 with name claim-script in state RUNNING> (stderr)>
2025-12-15 16:49:09,193 INFO exited: claim-script (exit status 0; expected)
2025-12-15 16:49:09,193 DEBG received SIGCHLD indicating a child quit
2025-12-15 16:49:10,071 DEBG ‘start-script’ stdout output:
Critical: libusb_init failed
I am seeing an error Ive never seen before: Dec 17, 2025 17:31:40.344 [22403314535224] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published (Bad Authentication)'. @ChuckPa any idea what would cause that message?
When I initially claim the server, start the container back up, and go look in the file it writes the preferences and shows the claim code in there. After any sort of reboot I can go back into that file and all the spots related to my account and claim code ect will be blank.
Owner of the container does have read write priv for the file.
I have reclaimed the server after your request and it still drops the Claim code every time that the Docker container is rebooted (when I claim It I am putting the claim code in docker container) then go back into plex while on the same network in order to then manually click the claim button inside of settings.
I believe the issue had something to do with Binhex’s docker containers for Unraid. No matter which of his containers I installed and how I ran it or changed permissions on the file it would always revert the permissions back to where there was no read write for certain groups on the preferences file. I uninstalled his containers and then installed the official plex docker container and now its saving properly to the preferences file. It is also allowing me to reboot so it appears that it was the permissions issue on the preferences file. Thank you for the help.
