Been having issues with Plex. Everytime I go to the WebUI, it acts like it's a new server and than says "A problem has been detected with a core component of Plex Media Server." I can go through the setup manually, but every new session does the same thing

Things I've done:

• Run the DBRepair

• Completely deleted my appdata and re-installed

• Disabled my ad-blocker (last change I made was adding a bunch of adlists).

• Noticed in the logs it was listening on IPv6 and failing so I enabled that on my network and my machines are getting IPv6 global unicast addresses.

Do I need to scrub Plex logs before I upload them?

55 minutes ago, Doogs said:

Been having issues with Plex. Everytime I go to the WebUI, it acts like it's a new server and than says "A problem has been detected with a core component of Plex Media Server." I can go through the setup manually, but every new session does the same thing

Things I've done:

• Run the DBRepair

• Completely deleted my appdata and re-installed

• Disabled my ad-blocker (last change I made was adding a bunch of adlists).

• Noticed in the logs it was listening on IPv6 and failing so I enabled that on my network and my machines are getting IPv6 global unicast addresses.

Do I need to scrub Plex logs before I upload them?

Have a similar issue, a very strange one..

Stopped working, restarted, no dice, updated nothing. Tried the WebGUI, didnt work. Removed and added again, same issue.

Any guidance welcome as have a house with 2 kids pissed at me :-(

Log:

/usr/lib/python3.13/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.

import pkg_resources

Created by...

___. .__ .__

\_ |__ |__| ____ | |__ ____ ___ ___

| __ \| |/ \| | \_/ __ \\ \/ /

| \_\ \ | | \ Y \ ___/ > <

|___ /__|___| /___| /\___ >__/\_ \

\/ \/ \/ \/ \/

https://hub.docker.com/u/binhex/

2025-07-26 09:13:19.612469 [info] Host is running unRAID

2025-07-26 09:13:19.641813 [info] System information: Linux Tower 6.6.78-Unraid #2 SMP PREEMPT_DYNAMIC Thu Feb 20 13:33:15 PST 2025 x86_64 GNU/Linux

2025-07-26 09:13:19.670264 [info] Image tags: BASE_RELEASE_TAG=2025071502,IMAGE_RELEASE_TAG=1.42.0.9975-1-01

2025-07-26 09:13:19.705694 [info] PUID defined as '99'

2025-07-26 09:13:19.770319 [info] PGID defined as '100'

2025-07-26 09:13:19.832743 [info] UMASK defined as '000'

2025-07-26 09:13:19.869079 [info] Permissions already set for '/config'

2025-07-26 09:13:19.915999 [info] Deleting files in /tmp (non recursive)...

2025-07-26 09:13:19.955250 [info] TRANS_DIR defined as '/config/transcode'

2025-07-26 09:13:20.073014 [info] Starting Supervisor...

2025-07-26 09:13:20,407 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing

2025-07-26 09:13:20,407 INFO Set uid to user 0 succeeded

2025-07-26 09:13:20,417 INFO RPC interface 'supervisor' initialized

2025-07-26 09:13:20,418 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2025-07-26 09:13:20,418 INFO supervisord started with pid 7

2025-07-26 09:13:21,423 INFO spawned: 'plexmediaserver' with pid 60

2025-07-26 09:13:21,424 INFO reaped unknown pid 8 (exit status 0)

2025-07-26 09:13:21,567 DEBG 'plexmediaserver' stderr output:

Failed to load preferences at /config/Plex Media Server/Preferences.xml

2025-07-26 09:13:22,567 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2025-07-26 09:13:23,565 DEBG 'plexmediaserver' stderr output:

Failed to load preferences at /config/Plex Media Server/Preferences.xml

On 7/26/2025 at 5:17 PM, djglenn said:

Failed to load preferences at /config/Plex Media Server/Preferences.xml

probably your preferences files is corrupt, try stopping the container then delete this file and start the container again.

On 7/26/2025 at 11:21 AM, Doogs said:

Been having issues with Plex. Everytime I go to the WebUI, it acts like it's a new server and than says "A problem has been detected with a core component of Plex Media Server." I can go through the setup manually, but every new session does the same thing

Things I've done:

• Run the DBRepair

• Completely deleted my appdata and re-installed

• Disabled my ad-blocker (last change I made was adding a bunch of adlists).

• Noticed in the logs it was listening on IPv6 and failing so I enabled that on my network and my machines are getting IPv6 global unicast addresses.

Do I need to scrub Plex logs before I upload them?

I can only replicate this issue on Windows and iPad web clients. On Windows I've tried multiple browsers - Chrome and Firefox, cleared browser cache, checked cookie settings, etc. I've also deleted the perms.txt file which shouldn't matter since I deleted the entire appdata for this docker container.

About to fire up a Linux VM to see if that behaves the same.

Edited July 28, 2025Jul 28 by Doogs

On 7/15/2025 at 1:38 PM, binhex said:

Hi all, the issue where the container is stopping MAY of been related to the introduction of healthchecking, this checks to see if the internet connection is operational, if not the container is marked as unhealthy and then set to shutdown the container.

I have now relaxed this somewhat and if not configurd it will now simply mark the container as 'unhealthy' rather than exit, i have also introduced additional env vars to permit the user to decide what they want to healthcheck as well as the action they prefer - these env vars are new so you won't see these unless you add from CA again.

So the TLDR is a new image has just been triggered by a new version of plex and this will include the above changes, so please pull down latest and give it a try and let me know.

On the latest update of the container right now as of 7/31 and I still seem to be encountering issues with Plex randomly shutting down, typically in the early morning.

Log:

2025-07-31 05:02:15,156 WARN received SIGTERM indicating exit request

2025-07-31 05:02:15,157 DEBG killing plexmediaserver (pid 59) with signal SIGTERM

2025-07-31 05:02:15,157 INFO waiting for plexmediaserver to die

2025-07-31 05:02:16,158 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23289758800528 for <Subprocess at 23289758032832 with name plexmediaserver in state STOPPING> (stdout)>

2025-07-31 05:02:16,158 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23289758456144 for <Subprocess at 23289758032832 with name plexmediaserver in state STOPPING> (stderr)>

2025-07-31 05:02:16,158 WARN stopped: plexmediaserver (exit status 143)

2025-07-31 05:02:16,158 DEBG received SIGCHLD indicating a child quit

It doesn't appear that the container was marked "unhealthy," it was still marked healthy and the container was running, but Plex itself wasn't running. Restarting the container fixes it. I have disabled healthcheck through the "--no-healthcheck" parameter today to see if healthcheck truly is the issue (forgot to do that until now).

1 hour ago, Palaris said:

it was still marked healthy and the container was running, but Plex itself wasn't running

Then your issue is definitely not healthcheck related, if the container goes unhealthy then it previously rebooted the container, now it should do nothing when unhealthy (unless instructed to do so), and as its currently listed as healthy it seems very unlikely to be healthcheck.

Do you run CA backup by any chance?, that can (if configured) cause the container to be paused or even restarted during the backup process, so look at that.

Also check your syslog, you maybe running low on RAM, in which case out of memory killer (seen in the syslog as OOM Killer) will kill any processes using high RAM that are in a idle state, Plex is probably such a process and could be killed, solution is more RAM or less processes running.

On 7/26/2025 at 10:21 AM, Doogs said:

Been having issues with Plex. Everytime I go to the WebUI, it acts like it's a new server and than says "A problem has been detected with a core component of Plex Media Server." I can go through the setup manually, but every new session does the same thing

Things I've done:

• Run the DBRepair

• Completely deleted my appdata and re-installed

• Disabled my ad-blocker (last change I made was adding a bunch of adlists).

• Noticed in the logs it was listening on IPv6 and failing so I enabled that on my network and my machines are getting IPv6 global unicast addresses.

Do I need to scrub Plex logs before I upload them?

Having the same issue since last night, Plex crashed during a library scan, followed the same basic steps, ran DBRepair, wiped the Preferences.xml and perms.txt files after errors showed up that indicated these files may be corrupted, uninstalled and nuked the appdata directory, reinstalled, still stuck with "A problem has been detected with a core component of Plex Media Server." Logs have not been particularly useful. Not running CA backup, and currently have approximately 278GB of free ram (yes, that's gigabytes).

2025-08-03 08:50:18.246750 [info] Host is running unRAID

2025-08-03 08:50:18.314530 [info] System information: Linux servname 6.12.24-Unraid #1 SMP PREEMPT_DYNAMIC Sat May 3 00:12:52 PDT 2025 x86_64 GNU/Linux

2025-08-03 08:50:18.380519 [info] Image tags: BASE_RELEASE_TAG=2025071502,IMAGE_RELEASE_TAG=1.42.0.9975-1-01

2025-08-03 08:50:18.455477 [info] PUID defined as '99'

2025-08-03 08:50:18.535544 [info] PGID defined as '100'

2025-08-03 08:50:18.621301 [info] UMASK defined as '000'

2025-08-03 08:50:18.696313 [info] Permissions already set for '/config'

2025-08-03 08:50:18.774209 [info] Deleting files in /tmp (non recursive)...

2025-08-03 08:50:18.855319 [info] TRANS_DIR defined as '/tmp/PlexRamScratch'

2025-08-03 08:50:18.936674 [info] Starting Supervisor...

2025-08-03 08:50:19,402 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing

2025-08-03 08:50:19,403 INFO Set uid to user 0 succeeded

2025-08-03 08:50:19,418 INFO RPC interface 'supervisor' initialized

2025-08-03 08:50:19,418 CRIT Server 'unix_http_server' running without any HTTP authentication checking

2025-08-03 08:50:19,419 INFO supervisord started with pid 19

2025-08-03 08:50:20,424 INFO spawned: 'plexmediaserver' with pid 71

2025-08-03 08:50:20,425 INFO reaped unknown pid 20 (exit status 0)

2025-08-03 08:50:21,427 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2025-08-03 08:50:34,246 DEBG 'plexmediaserver' stdout output:

Critical: libusb_init failed

Logs.zip

Edited August 5, 2025Aug 5 by worldspawn

Hi Binhex,

My thanks to you. Just started using unraid and your binhex installs seem to run better than others. After success with radarr and sonarr. I thought I would switch my plex docker to binhex.

I'm able to install binhex-plex (also tried binhex-plexpass) I installed and everything is good. Started scanning my library.

I see others mention this. If I close the web interface and reopen it. it opens like a new install. I hit the 'got it' box, then it tells me A problem has been detected with a core component of Plex Media Server. if I click the name, all my info is still in there and I can just next through everything.

the docker is still running, plex is scanning files and I can play them on my client. Just have to re-setup each time I open the web interface.

I don't see any errors. Not sure where to look. Just wanted to mention it incase someone has a fix for me.

thanks!

Hello all, I've moved my plex library to unraid and am trying to claim my server. I'm unable to access the web UI

I've attached the docker logs and the "Plex Media Server.log"

It's showing some 401 errors accessing plex.tv. Please let me know if I should upload anything else, thank you.

docker-logs.txt plex-media-server.log

7 minutes ago, kamcknig said:

Hello all, I've moved my plex library to unraid and am trying to claim my server. I'm unable to access the web UI

I've attached the docker logs and the "Plex Media Server.log"

It's showing some 401 errors accessing plex.tv. Please let me know if I should upload anything else, thank you.

docker-logs.txt plex-media-server.log

Never mind, a new claim token worked, solved.

Hello all, I'm back, so while I was finally able to access the web UI, it still would not let me claim the server.

I then tried removing the entire config folder and starting completely from scratch, but no matter what, it tells me I'm not authorized. Attached are docker logs and plex server logs

docker-logs.txt plex-server-log.log

1 hour ago, kamcknig said:

Hello all, I'm back, so while I was finally able to access the web UI, it still would not let me claim the server.

I then tried removing the entire config folder and starting completely from scratch, but no matter what, it tells me I'm not authorized. Attached are docker logs and plex server logs

docker-logs.txt plex-server-log.log

Well, no clue what I've done to fix it. But after twenty attempts or so it finally just worked. Solved.

I'm unable to run DBRepair.sh without forcing the PMS media server to stop manually. The script doesn't seem able to do it for me. Any ideas?

On 7/31/2025 at 8:50 AM, binhex said:

Then your issue is definitely not healthcheck related, if the container goes unhealthy then it previously rebooted the container, now it should do nothing when unhealthy (unless instructed to do so), and as its currently listed as healthy it seems very unlikely to be healthcheck.

Do you run CA backup by any chance?, that can (if configured) cause the container to be paused or even restarted during the backup process, so look at that.

Also check your syslog, you maybe running low on RAM, in which case out of memory killer (seen in the syslog as OOM Killer) will kill any processes using high RAM that are in a idle state, Plex is probably such a process and could be killed, solution is more RAM or less processes running.

Ran into another random shutdown this morning.

I had the binhex-plexpass container configured to be skipped by CA backup completely, so it shouldn't have been stopping the container. Just for testing, I am going to turn it on, configured it to exclude media, cache and metadata folders, maybe turning it on might do something? Not sure.

I don't think it's a RAM issue. I've got 32 gb installed, and don't see and OOM Killer or anything similar in the syslog.

I also turned healthchecks back on for the container. Gonna let it run for a bit and see what happens, will return with results.

On 8/12/2025 at 12:47 PM, kamcknig said:

Well, no clue what I've done to fix it. But after twenty attempts or so it finally just worked. Solved.

It was actually a bug in the plex server itself. It's been fixed on latest update.

Had a drive crash and had problems with the rebuild and lost data. Had to let this sit for a month and now finally getting back to it and I can't get plex to launch and I get the following in the log files. Can anybody point me in the right direction to get this back up and running?

Aug 15 18:05:27 Tower rc.docker: binhex-plexpass: 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 prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
Aug 15 18:05:27 Tower rc.docker: nvidia-container-cli: initialization error: nvml error: driver not loaded: unknown
Aug 15 18:05:27 Tower rc.docker: Error: failed to start containers: binhex-plexpass

On 7/19/2023 at 11:40 AM, binhex said:

yeah its relatively new, i wrote it to help out people who run into db corruption, i hope it works for you, please let me know as you are my first live user to use it 🙂

Is this still working. I think my db got corrupted can u still use this script

22 minutes ago, Triplerinse said:

Is this still working. I think my db got corrupted can u still use this script

Yes, follow the steps and it’s really easy, I updated the steps I took on a previous post you can find on my profile on this topic.

Edited August 20, 2025Aug 20 by Kognac

12 minutes ago, Kognac said:

Yes, follow the steps and it’s really easy, I updated the stepsI I took on a previous post you can find on my profile on this topic.

I looked through it and It looks doable lol. In your 2nd post it says it wasn't finishing but then you deleted the perms.txt file. Is that located in the db file? And you manual deleted it.?

Edited August 20, 2025Aug 20 by Triplerinse

Just now, Triplerinse said:

I looked through it and It looks doable lol. In your 2nd post it says it wasn't finishing but then you deleted the perms.txt file. Is that located in the db file? And you manual deleted it.?

So I got it to work and then updated the steps I’ll make it more clear on an edit here in a sec.

The deleted perms file was for a weird issue that you are unlikely having.

8 minutes ago, Kognac said:

So I got it to work and then updated the steps I’ll make it more clear on an edit here in a sec.

The deleted perms file was for a weird issue that you are unlikely having.

Thanks for the help

11 minutes ago, Triplerinse said:

Thanks for the help

Good luck! It should fix it your issue though.

If you have a large database, be prepared for it to take forever though!

Edited August 20, 2025Aug 20 by Kognac

2 hours ago, Kognac said:

Good luck! It should fix it your issue though.

If you have a large database, be prepared for it to take forever though!

so i started it looks likes this

DBRepair.sh

Database Repair Utility for Plex Media Server (BINHEX)

Version v1.11.09

Select

1 - 'stop' - Stop PMS.

2 - 'automatic' - Check, Repair/Optimize, and Reindex Database in one step.

3 - 'check' - Perform integrity check of database.

4 - 'vacuum' - Remove empty space from database without optimizing.

5 - 'repair' - Repair/Optimize databases.

6 - 'reindex' - Rebuild database indexes.

7 - 'start' - Start PMS

8 - 'import' - Import watch history from another database independent of Plex. (risky).

9 - 'replace' - Replace current databases with newest usable backup copy (interactive).

10 - 'show' - Show logfile.

11 - 'status' - Report status of PMS (run-state and databases).

12 - 'undo' - Undo last successful command.

21 - 'prune' - Remove old image files (jpeg,jpg,png) from PhotoTranscoder cache & all temp files left by PMS.

42 - 'ignore' - Ignore duplicate/constraint errors.

88 - 'update' - Check for updates.

98 - 'quit' - Quit immediately. Keep all temporary files.

99 - 'exit' - Exit with cleanup options.

Enter command # -or- command name (4 char min) : 1

Stopping PMS.

Stopped PMS.

Select

1 - 'stop' - Stop PMS.

2 - 'automatic' - Check, Repair/Optimize, and Reindex Database in one step.

3 - 'check' - Perform integrity check of database.

4 - 'vacuum' - Remove empty space from database without optimizing.

5 - 'repair' - Repair/Optimize databases.

6 - 'reindex' - Rebuild database indexes.

7 - 'start' - Start PMS

8 - 'import' - Import watch history from another database independent of Plex. (risky).

9 - 'replace' - Replace current databases with newest usable backup copy (interactive).

10 - 'show' - Show logfile.

11 - 'status' - Report status of PMS (run-state and databases).

12 - 'undo' - Undo last successful command.

21 - 'prune' - Remove old image files (jpeg,jpg,png) from PhotoTranscoder cache & all temp files left by PMS.

42 - 'ignore' - Ignore duplicate/constraint errors.

88 - 'update' - Check for updates.

98 - 'quit' - Quit immediately. Keep all temporary files.

99 - 'exit' - Exit with cleanup options.

Enter command # -or- command name (4 char min) : 2

Automatic Check,Repair,Index started.

Checking the PMS databases

you said it will take for ever my db is about 128gb. do i have to keep the window open the whole time. Are we talking over night days lol just curious.

1 hour ago, Triplerinse said:

so i started it looks likes this

DBRepair.sh

Database Repair Utility for Plex Media Server (BINHEX)

Version v1.11.09

Select

1 - 'stop' - Stop PMS.

2 - 'automatic' - Check, Repair/Optimize, and Reindex Database in one step.

3 - 'check' - Perform integrity check of database.

4 - 'vacuum' - Remove empty space from database without optimizing.

5 - 'repair' - Repair/Optimize databases.

6 - 'reindex' - Rebuild database indexes.

7 - 'start' - Start PMS

8 - 'import' - Import watch history from another database independent of Plex. (risky).

9 - 'replace' - Replace current databases with newest usable backup copy (interactive).

10 - 'show' - Show logfile.

11 - 'status' - Report status of PMS (run-state and databases).

12 - 'undo' - Undo last successful command.

21 - 'prune' - Remove old image files (jpeg,jpg,png) from PhotoTranscoder cache & all temp files left by PMS.

42 - 'ignore' - Ignore duplicate/constraint errors.

88 - 'update' - Check for updates.

98 - 'quit' - Quit immediately. Keep all temporary files.

99 - 'exit' - Exit with cleanup options.

Enter command # -or- command name (4 char min) : 1

Stopping PMS.

Stopped PMS.

Select

1 - 'stop' - Stop PMS.

2 - 'automatic' - Check, Repair/Optimize, and Reindex Database in one step.

3 - 'check' - Perform integrity check of database.

4 - 'vacuum' - Remove empty space from database without optimizing.

5 - 'repair' - Repair/Optimize databases.

6 - 'reindex' - Rebuild database indexes.

7 - 'start' - Start PMS

8 - 'import' - Import watch history from another database independent of Plex. (risky).

9 - 'replace' - Replace current databases with newest usable backup copy (interactive).

10 - 'show' - Show logfile.

11 - 'status' - Report status of PMS (run-state and databases).

12 - 'undo' - Undo last successful command.

21 - 'prune' - Remove old image files (jpeg,jpg,png) from PhotoTranscoder cache & all temp files left by PMS.

42 - 'ignore' - Ignore duplicate/constraint errors.

88 - 'update' - Check for updates.

98 - 'quit' - Quit immediately. Keep all temporary files.

99 - 'exit' - Exit with cleanup options.

Enter command # -or- command name (4 char min) : 2

Automatic Check,Repair,Index started.

Checking the PMS databases

you said it will take for ever my db is about 128gb. do i have to keep the window open the whole time. Are we talking over night days lol just curious.

I believe you do have to keep the console window open, but yeah idk how large mine is but yours will take probably an hour or two.

2 hours ago, Kognac said:

I believe you do have to keep the console window open, but yeah idk how large mine is but yours will take probably an hour or two.

I'm really sorry i keep spamming you with this issue. i guess i got confused between 2 different methods (i believe). so binhex has his script he wrote and i believe it is  /home/nobody/dbrepair.sh. i saw a screen shot of a guy having an issue and the screen shot was the menus i was looking at. The one that you suggested is form this github? https://github.com/ChuckPa/DBRepair. Its been a long week and im just getting confused from all the previous post. i ran dbrepair.sh but it was sitting at checking pms database for 3 hours and didn't seem like it was running. Im about at the point to nuke the docker and start from scratch. sorry to bug you