# Plex on Unraid. PLEASE GOD HELP\>

**URL:** <https://forums.plex.tv/t/plex-on-unraid-please-god-help/935558>\
**Category:** Plex Media Server\
**Tags:** server-unraid\
**Created:** [January 18, 2026, 3:16am UTC](https://forums.plex.tv/t/plex-on-unraid-please-god-help/935558 "2026-01-18T03:16:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [January 18, 2026, 3:45am UTC](https://forums.plex.tv/t/plex-on-unraid-please-god-help/935558/2 "2026-01-18T03:45:36Z")

</div>

Found a few things.

1. The certificate you added is not working. The error indicates either bad password, incorrect SSL algorithm (Plex requires SSLv3)

```auto
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.

> [@Linux Tips](https://forums.plex.tv/t/linux-tips/276247/25):
>
> OpenSSL v3.0.0 and PMS. For those using their own domains and certificates with PMS , PMS 1.32.0.6865 and above updates OpenSSL from v1.1.1 to v3.0.0 . (changed the numbering scheme in the process) The consequence of this is OpenSSL v3 removed several “less secure” encryption methods. The impact on you, if you’re using an older distributions where openssl v3 is not the default, if not already doing so, you will need pay special attention to how your certificates are generated As example,…

1. The database is damaged

```auto
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

> **[GitHub - ChuckPa/DBRepair: Database repair utility for Plex Media Server...](https://github.com/ChuckPa/DBRepair)**
>
> Database repair utility for Plex Media Server databases

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

---

_[View the full topic](https://forums.plex.tv/t/plex-on-unraid-please-god-help/935558)._