September 30, 2025Sep 30 On 9/28/2025 at 4:07 PM, binhex said:You should set CLAIM_SERVER to 'yes' and put in a valid claim token for the value of PLEX_CLAIM only when you want to claim your server, once you have claimed your server then set CLAIM_SERVER to 'no', this will then stop the server from attempting to claim on startup.Here is what I have done nowGet new Claim CodeEnter Claim code into docker settings and set CLAIM_SERVER to "yes"This correctly claims the serverI do still get this error2025-09-29 20:53:46,371 DEBG 'start-script' stderr output:Error in command line:the argument for option '--userId' should follow immediately after the equal signChange CLAIM_SERVER to "no" and restart containerNo issues so far with an unclaimed server (thank you!!)
October 1, 2025Oct 1 I setup tailscale and it was working, but now when I start the container it is unable to download the tailscale files.I edited the pacman file with new mirrors I found, but still doesn't work. something about pkg_resources module is deprecated as an API
October 5, 2025Oct 5 Having issue adding a network XMLTV file when adding a Tunarr or ErsatTV tunerFile works and have validated itAny ideas?Have tried both containers as Host & bridge and same error
October 5, 2025Oct 5 Ok confirmed something wrong with the container that stops it loading local network XMLTV guides
October 21, 2025Oct 21 On 9/30/2025 at 12:23 PM, Shu said:Here is what I have done nowGet new Claim CodeEnter Claim code into docker settings and set CLAIM_SERVER to "yes"This correctly claims the serverI do still get this errorChange CLAIM_SERVER to "no" and restart containerNo issues so far with an unclaimed server (thank you!!)did this, still get the error , but it works. thank you.
October 30, 2025Oct 30 So this started last week, this container is as up to date as it can be. Running on Unraid 7.0.1Binhex-Plex is eating literally every bit of ram it possibly can which halts the entire server. I used DBRepair to automate the repair process of plex's DBs but that came back clean and successful. Logs show nothing from either the container or unraid, just the halting of services before the eventual death of it all. Anyone else have this issue? After either gaining control and rebooting the container (or rebooting the server as a whole) Plex runs super snappy and loads no problem. It takes roughly 1 to 3 hours before it dies again.Edit: I've updated the server to 7.2.0 and I removed/reloaded the plex container. So far it's been stable again for ~12 hours at leastEdit 2: nope, cratered again about an hour ago. attached plex log. I have a feeling this is what is causing it. Unsure if Plex issue specifically or not. please let me know. Plex Media Server.log Edited October 30, 2025Oct 30 by Rockstar Logs attached
November 21, 2025Nov 21 Hey everyone,I’m not sure if this is an issue on my end or something with the Docker image, but every time my server restarts, I’m forced to re-claim it again. The server doesn’t seem to retain the claim token or persistent auth data between restarts.I’ve confirmed my volumes are mapped, and nothing else seems out of the ordinary. Has anyone else run into this or know what might be causing it?Any suggestions would be appreciated!Thanks.
November 22, 2025Nov 22 I am having the logs tell me that I don't have plex_claim yes/no or the other one yes/no every startup. I tried both, and alternated, and I can't rid of the bloody error message. The server is claimed.IT says it pulls a config file from like etc/modprobe.d/plexmediaserver and in that file is plex_claim code. I tried commenting it out at first, no cigar, deleted it, it was remade.the little listing things make sad.
November 23, 2025Nov 23 Author On 11/21/2025 at 11:57 AM, owzo said:Hey everyone,I’m not sure if this is an issue on my end or something with the Docker image, but every time my server restarts, I’m forced to re-claim it again. The server doesn’t seem to retain the claim token or persistent auth data between restarts.I’ve confirmed my volumes are mapped, and nothing else seems out of the ordinary. Has anyone else run into this or know what might be causing it?Any suggestions would be appreciated!Thanks.what is variable claim_server set to?, it should be set to 'no' unless you want to claim, i suspect its set to 'yes' (not the default).
November 23, 2025Nov 23 Author 13 hours ago, paradox.actual said:I am having the logs tell me that I don't have plex_claim yes/no or the other one yes/no every startup. I tried both, and alternated, and I can't rid of the bloody error message. The server is claimed.IT says it pulls a config file from like etc/modprobe.d/plexmediaserver and in that file is plex_claim code. I tried commenting it out at first, no cigar, deleted it, it was remade.the little listing things make sad.you are missing two new(ish) variables that have got added to the template, updates to the template do NOT get pushed to users, so if you want to get rid of the messages (which btw are harmless as i have put in defaults if they are not defined) then you will need to add in the additional variables 'CLAIM_SERVER' and 'PLEX_CLAIM'.
November 26, 2025Nov 26 Running Version 4.147.1Trying to update via Unraid and failing:Error response from daemon: Conflict. The container name "/binhex-plexpass" is already in use by container "b2b981d83941485470843ae9bab185d0f3c15bb145ec467f052d20d9d052fc30". You have to remove (or rename) that container to be able to reuse that name.
December 5, 2025Dec 5 This latest update is broken. It won't install even after I removed the docker image.Error: failed to register layer: rename /var/lib/docker/image/btrfs/layerdb/tmp/write-set-2720484931 /var/lib/docker/image/btrfs/layerdb/sha256/9465850a4794df81633065da39c728411e3d957f9d5ec553deb7650b40ce0f8b: file existsI even tried deleting the existing file through the terminal with no luck. Edited December 5, 2025Dec 5 by DOUG SAWYER
December 9, 2025Dec 9 Working through an issue after updating to 1.43.0.10389-1-01 and updating Unraid to 7.2.2. After the update, the docker image gave the "Execution Error - Server Error" message and failed to start the container. I tried rebooting/removing/reinstalling the image; this was my result:I came across this:Docker Fails to Launch GPU Containers with NVIDIA Runtime, but Podman Works - Docker Engine / General - Docker Community ForumsSeeing how that post identified their container issues related to their GPU, I removed the host keys related to my nVidia GPU in my configuration the container was at least able to start.Seems like there's a CUDA issue with the driver version vs. the one I had installed? Anyways, this at least got my docker container back up and running so I can troubleshoot the rest of the issues. Wanted to post this here in case anyone else was having an issue.
December 9, 2025Dec 9 1 hour ago, SirRedwood said:Working through an issue after updating to 1.43.0.10389-1-01 and updating Unraid to 7.2.2. After the update, the docker image gave the "Execution Error - Server Error" message and failed to start the container. I tried rebooting/removing/reinstalling the image; this was my result:I came across this:Docker Fails to Launch GPU Containers with NVIDIA Runtime, but Podman Works - Docker Engine / General - Docker Community ForumsSeeing how that post identified their container issues related to their GPU, I removed the host keys related to my nVidia GPU in my configuration the container was at least able to start.Seems like there's a CUDA issue with the driver version vs. the one I had installed? Anyways, this at least got my docker container back up and running so I can troubleshoot the rest of the issues. Wanted to post this here in case anyone else was having an issue.I had to downgrade to the Production Branch. Unraid wasn't seeing my GPU under the v590.44.01 driver. Problems fixed!
December 16, 2025Dec 16 Hello all,I cannot get Plex to start up. When I look at the logs this is what I see. Nothing is sticking out to me within them. Any ideas?text error warn system array loginUnlinking stale socket /run/supervisor.sock2025-12-15 17:15:42,605 DEBG 'start-script' stdout output:The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.2025-12-15 17:22:28,061 WARN received SIGTERM indicating exit request2025-12-15 17:22:28,062 DEBG killing start-script (pid 91) with signal SIGTERM2025-12-15 17:22:28,062 INFO waiting for start-script to die2025-12-15 17:22:31,066 INFO waiting for start-script to die2025-12-15 17:22:34,070 INFO waiting for start-script to die2025-12-15 17:22:37,073 INFO waiting for start-script to dieCreated by...___. .__ .__\_ |__ |__| ____ | |__ ____ ___ ___| __ \| |/ \| | \_/ __ \\ \/ /| \_\ \ | | \ Y \ ___/ > <|___ /__|___| /___| /\___ >__/\_ \\/ \/ \/ \/ \/https://hub.docker.com/u/binhex/2025-12-15 17:30:00.308752 [info] Host is running unRAID2025-12-15 17:30:00.344676 [info] System information: Linux SolidSnake 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May 3 00:12:52 PDT 2025 x86_64 GNU/Linux2025-12-15 17:30:00.375151 [info] Image architecture: 'amd64'2025-12-15 17:30:00.411827 [info] Application name: 'plexpass'2025-12-15 17:30:00.445042 [info] Base image release tag: '2025120203'2025-12-15 17:30:00.477399 [info] Application image release tag: '1.43.0.10389-1-01'2025-12-15 17:30:00.516021 [info] PUID defined as '99'2025-12-15 17:30:00.557832 [info] User 'nobody' already has UID '99', skipping usermod2025-12-15 17:30:00.594883 [info] PGID defined as '100'2025-12-15 17:30:00.631213 [info] Group 'users' already has GID '100', skipping groupmod2025-12-15 17:30:00.663384 [info] UMASK defined as '000'2025-12-15 17:30:00.702911 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'2025-12-15 17:30:00.747879 [info] Deleting files in /tmp (non recursive)...2025-12-15 17:30:00.787763 [warn] TRANS_DIR not defined,(via -e TRANS_DIR), defaulting to '/config/tmp'2025-12-15 17:30:00.830391 [info] Starting Supervisor...2025-12-15 17:30:01,339 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing2025-12-15 17:30:01,340 INFO Set uid to user 0 succeeded2025-12-15 17:30:01,652 INFO RPC interface 'supervisor' initialized2025-12-15 17:30:01,653 INFO supervisord started with pid 202025-12-15 17:30:02,656 INFO spawned: 'claim-script' with pid 842025-12-15 17:30:02,657 INFO spawned: 'start-script' with pid 852025-12-15 17:30:02,658 INFO reaped unknown pid 21 (exit status 0)2025-12-15 17:30:02,665 DEBG 'claim-script' stdout output:[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping claim process.2025-12-15 17:30:02,666 INFO success: claim-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)2025-12-15 17:30:02,666 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23349841158432 for <Subprocess at 23349841150368 with name claim-script in state RUNNING> (stdout)>2025-12-15 17:30:02,666 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23349840832912 for <Subprocess at 23349841150368 with name claim-script in state RUNNING> (stderr)>2025-12-15 17:30:02,666 INFO exited: claim-script (exit status 0; expected)2025-12-15 17:30:02,667 DEBG received SIGCHLD indicating a child quit2025-12-15 17:30:02,684 DEBG 'start-script' stdout output:[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.2025-12-15 17:30:03,686 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2025-12-15 17:30:22,934 DEBG 'start-script' stdout output:Critical: libusb_init failed2025-12-15 17:49:08,894 DEBG 'start-script' stdout output:The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.2025-12-15 18:08:43,694 DEBG 'start-script' stdout output:The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.2025-12-15 18:23:47,846 DEBG 'start-script' stdout output:Dolby, Dolby Digital, Dolby Digital Plus, Dolby TrueHD and the double D symbol are trademarks of Dolby Laboratories.2025-12-15 18:28:53,579 DEBG 'start-script' stdout output:The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.2025-12-15 18:48:59,453 DEBG 'start-script' stdout output:The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.2025-12-15 19:17:58,866 DEBG 'start-script' stdout output:The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.2025-12-15 19:46:26,265 DEBG 'start-script' stdout output:The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.2025-12-15 20:12:18,923 DEBG 'start-script' stdout output:The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.2025-12-15 20:38:07,987 DEBG 'start-script' stdout output:The '--scan' operation is deprecated and will be removed in future versions of Plex Media Server.2025-12-15 21:14:14,509 WARN received SIGTERM indicating exit request2025-12-15 21:14:14,510 DEBG killing start-script (pid 85) with signal SIGTERM2025-12-15 21:14:14,511 INFO waiting for start-script to die2025-12-15 21:14:17,516 INFO waiting for start-script to die2025-12-15 21:14:20,520 INFO waiting for start-script to die2025-12-15 21:14:23,525 INFO waiting for start-script to die Edited December 16, 2025Dec 16 by El Player
December 16, 2025Dec 16 1 hour ago, El Player said:Any ideas?Try the plex docker from linuxserver - i use this docker for years without issues... Edited December 16, 2025Dec 16 by Zonediver
December 18, 2025Dec 18 On 11/23/2025 at 5:00 AM, binhex said:you are missing two new(ish) variables that have got added to the template, updates to the template do NOT get pushed to users, so if you want to get rid of the messages (which btw are harmless as i have put in defaults if they are not defined) then you will need to add in the additional variables 'CLAIM_SERVER' and 'PLEX_CLAIM'.Is this why my trying to update the docker fails?docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running createContainer hook #4: exit status 1, stdout: , stderr: 2025/12/18 12:30:33 Error updating ldcache: error running pivot_root: pivot_root .: invalid argumentexit status 1: unknown.
December 19, 2025Dec 19 Author 20 hours ago, Paul_Ber said:Is this why my trying to update the docker fails?in a word, no, probably db corruption that's the normal issue, open the file /config/Plex Media Server/Logs/Plex Media Server.log and check for the word corruption or error .
January 7Jan 7 I deleted my original post here at the end because it was similar to other issues above and it wasn't adding anything new. Hopefully, this adds a bit more detail that could be useful. My original problem is that Plex isn't scanning the libraries or adding any new additions to the app.On the Docker tab, I grabbed the logs from the plex container and it has this error at the end of the file "Critical: libusb_init failed". All the googles kept saying that it was an error related to Plex looking for USB tuner or USb controller and the devs said it could be ignored. Until I learn different, I'll ignore that for now. Next, I grabbed logs from inside the Plex app. I searched for the latest "Plex Media Scanner Analysis.log" file and found the errors I pasted at teh bottom of the post. Searching for these, lead to this page in the Plex support articles Repair a Corrupted Database | Plex SupportThis is where I hope I can get some help. Is the "VACUUM;" command the right tool to repair the database with? Can I run that command from the console located in the context menu of binhex-plexpass? Or will I need to run it from the Plex SQLite tool?Thanks in advance for any help.Dec 30, 2025 21:00:23.044 [22398567471872] ERROR - SQLITE3:0x80000001, 11, database corruption at line 72267 of [a29f994989]Dec 30, 2025 21:00:23.044 [22398567471872] ERROR - SQLITE3:0x80000001, 11, statement aborts at 3: [SELECT value FROM 'main'.'fts4_metadata_titles_icu_stat' WHERE id=?] database disk image is malformedDec 30, 2025 21:00:23.044 [22398567471872] ERROR - SQLITE3:0x80000001, 11, statement aborts at 10: [UPDATE metadata_items SET library_section_id=:U1parent_id=:U2metadata_type=:U3guid=:U4edition_title=:U5slug=:U6hash=:U7media_item_count=:U8title=:U9title_sort=:U10original_title=:U11studio=:U12rating=:U13audience_rating=:U14rating_count=:U15tagline=:U16summary=:U17content_rating=:U18content_rating_age=:U19is_adult=:U20index=:U21absolute_index=:U22duration=:U23metadata_agent_provider_group_id=:U24user_thumb_url=:U25user_art_url=:U26user_banner_url=:U27user_clear_logo_url=:U28user_square_art_url=:U29user_music_url=:U30user_fields=:U31originally_available_at=:U32available_at=:U33expires_at=:U34refreshed_at=:U35year=:U36added_atDec 30, 2025 21:00:23.044 [22398567471872] ERROR - Exception inside transaction (inside=1) (/home/runner/_work/plex-media-server/plex-media-server/Library/MetadataItem.cpp:1102): std::exceptionDec 30, 2025 21:00:23.044 [22398567471872] ERROR - Exception inside transaction (inside=1) (/home/runner/_work/plex-media-server/plex-media-server/Library/MediaItem.cpp:1877): std::exceptionDec 30, 2025 21:00:23.044 [22398567471872] ERROR - Thread: Uncaught exception running async task which was spawned by thread 22398740000512: std::exception Edited January 7Jan 7 by Ogre_
January 7Jan 7 Author 11 hours ago, Ogre_ said:"Critical: libusb_init failed". All the googles kept saying that it was an error related to Plex looking for USB tuner or USb controller and the devs said it could be ignored. Until I learn different, I'll ignore that for nowYep, ignore it, it is not critical even though the stupid message from Plex says otherwise.11 hours ago, Ogre_ said:RROR - SQLITE3:0x80000001, 11, database corruptionYep this is a classic case of db corruption, it's the most common problem with Plex, luckily for you there is an included script in the image which should help you out (skip install instructions), instructions for use can be found here (script authors git repo): https://github.com/ChuckPa/DBRepair
January 13Jan 13 On 10/5/2025 at 6:01 PM, dopeytree said:Having issue adding a network XMLTV file when adding a Tunarr or ErsatTV tunerFile works and have validated itAny ideas?Have tried both containers as Host & bridge and same error Anyone know how to get this to work with URLs with binhex containers? The official container works just fine using URLs in this field.On 10/5/2025 at 6:01 PM, dopeytree said:Having issue adding a network XMLTV file when adding a Tunarr or ErsatTV tunerFile works and have validated itAny ideas?Have tried both containers as Host & bridge and same error I have this same issue and know the URL path works... I tested in the official Plex container with no issue.Any ideas why binhex doesn't work with URLs here?
January 18Jan 18 I keep getting "Failed to get runtime from the file, make sure ffprobe is available", what am I doing wrong or how can I fix? Thanks so much for all of your time!
March 13Mar 13 Did anyone else get an email from Plex regarding action required to update plex media server on linux systems?
March 13Mar 13 Yes I did as well. Unsure if we need to do that with the upcoming repository releases or what the plan is.
March 13Mar 13 20 minutes ago, owlcookie said:Did anyone else get an email from Plex regarding action required to update plex media server on linux systems?Yes I got one, it does say if you are running it on docker or nas you can ignore the email. Edited March 13Mar 13 by Triplerinse
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.