Plex on Unraid. PLEASE GOD HELP>

Plex Media Server
1

Im using Unraid. I have had Plex-Media-Server running for 2-3 years. I had my issues here and there. Randomly about a month ago, my movies stopped getting scanned into plex. I use radarr for movies, and sonarr for tv shows. Nothing changed. One day no new movies i downloaded showed up in plex. The movies show up in my shares on unraid, they show up in my file explorer via SMB on my windows computer. I used grok and chat GPT and tried everything.. permissions were ok, file paths were ok.. logs were ok.. except AI kept saying my plex was bugging out when it scans for library files. Eventually.. I removed plex from unraid, and re installed it. this removed EVERYONE that I had already given access too. It also now has 2 movie tabs/libraries showing up under my server “tower”. There still is no new movies that i downloaded on the server, and no one can access it now also, even though it shows remote access is good. I NEED HELP I will pay.. i just need professional help please.. this is beyond me.

Plex Media Server Logs_2026-01-17_21-32-47.zip (2.5 MB)

Plex-Media-Server Movies not showing up in Plex. using unraid Plex docker
2

Found a few things.

  1. The certificate you added is not working. The error indicates either bad password, incorrect SSL algorithm (Plex requires SSLv3)
Jan 17, 2026 18:45:41.201 [22960210614928] DEBUG - MyPlex: using cached data for request for https://plex.tv/api/v2/server/users/features
Jan 17, 2026 18:45:41.239 [22960210614928] ERROR - [CERT] PKCS12_parse failed: error:11800071:PKCS12 routines::mac verify failure
Jan 17, 2026 18:45:41.239 [22960210614928] ERROR - [CERT] Found a certificate, but couldn't install it.
Jan 17, 2026 18:45:41.239 [22960210614928] DEBUG - HttpServer: Listening on IPv6 as well as IPv4.

Here is how to make your certificate.

  1. The database is damaged
Jan 17, 2026 18:45:51.057 [22960108387128] DEBUG - [DatabaseFixups/31DatabaseFixupsCleanupActivities] Executing fixup
Jan 17, 2026 18:45:51.382 [22960108387128] ERROR - [DatabaseFixups/31DatabaseFixupsCleanupActivities] SQLITE3:0x80000001, 779, index corruption at line 94622 of [a29f994989]
Jan 17, 2026 18:45:51.382 [22960108387128] ERROR - [DatabaseFixups/31DatabaseFixupsCleanupActivities] SQLITE3:0x80000001, 779, statement aborts at 41: [DELETE FROM activities WHERE `started_at`<:C1] database disk image is malformed
Jan 17, 2026 18:45:51.387 [22960108387128] ERROR - [DatabaseFixups/31DatabaseFixupsCleanupActivities] Fixup threw an exception: std::exception
Jan 17, 2026 18:45:51.387 [22960108387128] DEBUG - [DatabaseFixups/31DatabaseFixupsCleanupActivities] Fixup completed

The recommended fix is to substitute one of your backup DBs in to use as current

I wrote a tool which will help you do this (DBRepair), specifically the Replace command

Since your server does minimally run (the container starts), I would place DBRepair under /config and run it from inside the container (docker exec style) where it can detect which image you’re using and auto-configure the paths itself.

You can try to use the “Auto” function first but given the Index is malformed, it may not work.

That failing, REPLACE is your best option to recover.

  1. Since your LAN appears to be IPv4, you can turn off IPv6 support in Settings - server - Network