7 minutes ago, ConnerVT said:

Stop Plex.

Delete the Codecs folder.

Start Plex

Plex will download a fresh Codecs folder with the correct files.

This has been an ongoing thing with Plex for several years.

Perfect! Thank you so much!

"Weird experiences" is a very vague description, so I won't give any advice. It really depends on your equipment, the media file(s) being played, how the media is being played (Direct Play, HW transcoded, CPU transcoded), the client (dedicated app on TV/device, web browser). So any variables to consider, so there is no One Size Fits All.

The two situations I've seen issues where updating the codecs seem to solve the issue is with EasyAudioEncoder and with HDR media (when it isn't a Plex update shooting itself in the groin). Since deleting the Codec folder and letting the software get a fresh copy is a simple troubleshooting task, it is always worth a try to see if it solves the issue.

The unanswered question is - What causes the codec to get corrupted? Is it a software issue in the Plex app itself, or something from the system/server side? I only have needed to do this maybe two times in the 7 (?) years I have been using Plex, so I don't know. But I have passed this tip to many here on the Unraid forum, and most all have had a positive result.

On 4/13/2025 at 9:09 AM, jedivoodoo said:

Lately my Plex install is ballooning my docker folder (I switched from image years ago) and I'm not sure what's up. Not the appdata, but the actual docker container folder data itself as reported by Unraid when you hit "container size" in the docker section of the Unraid gui. I woke up to a notification that my ssd was filling up, and after trying to figure out the source I found the Plex docker size to be reporting over 1TB. Updating/restarting the container seems to reset the size back to the expected 300 or so MB. As far as I can tell all of my mounts are correctly mounted to outside of the container (I have not changed them in well over a year). Looking at the different support channels, I seem to be having a similar issue to this post: https://forums.plex.tv/t/unraid-plex-ballooning-overlay2-folder-in-docker-directory/865874 but since the issue was not resolved over on the Plex forums I figured I'd try here as well. I just restarted the container to clear some space and neglected to grab logs, I'll update this post later when I start to see it fill up again. I was wondering if anyone has any ideas where to start for dealing with this.

Did you find a solution for this?

It started happening every week or so to me. There's nothing in the logs that can tell me something, but because of the time of the day this happens it's clear it's happening when the docker container updates.

Like you said, a restart fixes the issue. The funny thing is, I know it's not issolated. Literally when it happens to me, all the servers shared to me are also down, and I have contacted the owners, and they see the same issues.

I'm surprised I can't find more reports for this issue.

3 hours ago, pmcnano said:

Did you find a solution for this?

It started happening every week or so to me. There's nothing in the logs that can tell me something, but because of the time of the day this happens it's clear it's happening when the docker container updates.

Like you said, a restart fixes the issue. The funny thing is, I know it's not issolated. Literally when it happens to me, all the servers shared to me are also down, and I have contacted the owners, and they see the same issues.

I'm surprised I can't find more reports for this issue.

I have not! It's still ballooning and I just kinda let it do it's thing, since I use the backup and restore plugin to have the container update once a week. I know it's eating my nvme with writes but I can't find a solution so I don't really have a choice.

9 hours ago, pmcnano said:

Like you said, a restart fixes the issue. The funny thing is, I know it's not issolated. Literally when it happens to me, all the servers shared to me are also down, and I have contacted the owners, and they see the same issues.

most likely a failed mount inside plex container.

sample, transcode location, compare your mount with your entry inside plex

especially when after a reboot "temp" files are gone

7 hours ago, alturismo said:

most likely a failed mount inside plex container.

sample, transcode location, compare your mount with your entry inside plex

especially when after a reboot "temp" files are gone

I appreciate the tip but as I've posted earlier, this is not the case. All of my mounts are correct and have not changed in well over a year, but this issue is relatively new. It is related to the sonic analysis feature as far as I can tell and happens primarily when I add new music.

i keep getting the error below over and over again, with and my plex server is not starting.

Any ideas?

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.42.1.10060-4e8b05daf/PLEX MEDIA SERVER/0d186f19-9edb-4b8a-499b5ab6-3906d437.dmp

Starting Plex Media Server. . . (you can ignore the libusb_init error)

libc++abi: terminating with uncaught exception of type soci::soci_error: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=6553

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.42.1.10060-4e8b05daf/PLEX MEDIA SERVER/42dd8a4a-cd9c-4b06-7860c7a3-5b9fbe8c.dmp

Starting Plex Media Server. . . (you can ignore the libusb_init error)

libc++abi: terminating with uncaught exception of type soci::soci_error: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=6553

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.42.1.10060-4e8b05daf/PLEX MEDIA SERVER/38e3ec8b-6469-4ebc-c2f652ae-7227e001.dmp

Starting Plex Media Server. . . (you can ignore the libusb_init error)

libc++abi: terminating with uncaught exception of type soci::soci_error: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=6553

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.42.1.10060-4e8b05daf/PLEX MEDIA SERVER/71a87f08-dfaf-4caf-96ca5f82-574677a4.dmp

Starting Plex Media Server. . . (you can ignore the libusb_init error)

libc++abi: terminating with uncaught exception of type soci::soci_error: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=6553

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash

The recent security announcement prompting us to update lead me to go into the server settings to check the version number and I see a version 4.x instead of the current ranges of 1.42.x. My docker image is at 1.42.1

Just curious what explains this discrepancy?

6 minutes ago, yan said:

The recent security announcement prompting us to update lead me to go into the server settings to check the version number and I see a version 4.x instead of the current ranges of 1.42.x. My docker image is at 1.42.1

Just curious what explains this discrepancy?

That is the version of the web client. To get the server version, scroll down the left on the same settings area and under your server name, go to Settings, General. It should say something like "Version 1.42.1.10060", but I'm guessing a docker update will be available soon enough.

Since an update at the beginning of June plex has consistently been using 100% of the CPU (as shown in Glances), I've gone through and disabled all scheduled tasks besides credit and intro scanning, what is the best way to determine the culprit here? What's the appropriate log to look into? Any help is appreciated!

Edited September 2, 2025Sep 2 by MTerracciano

Dear Plex User,

We have recently experienced a security incident that may potentially involve your Plex account information. We believe the actual impact of this incident is limited; however, action is required from you to ensure your account remains secure. What happened An unauthorized third party accessed a limited subset of customer data from one of our databases. While we quickly contained the incident, information that was accessed included emails, usernames, and securely hashed passwords. Any account passwords that may have been accessed were securely hashed, in accordance with best practices, meaning they cannot be read by a third party. Out of an abundance of caution, we recommend you immediately reset your password by visiting https://plex.tv/reset. Rest assured that we do not store credit card data on our servers, so this information was not compromised in this incident. What we're doing We've already addressed the method that this third party used to gain access to the system, and we're undergoing additional reviews to ensure that the security of all of our systems is further hardened to prevent future attacks. What you must do We kindly request that you reset your Plex account password immediately by visiting https://plex.tv/reset. When doing so, there's a checkbox to "Sign out connected devices after password change," which we recommend you enable. This will sign you out of all your devices (including any Plex Media Server you own) for your security, and you will then need to sign back in with your new password. We understand that this means a little more work for you, but it will provide additional security to your account. Additional Security Measures You Can Take We remind you that no one at Plex will ever reach out to you over email to ask for a password or credit card number for payments. For further account protection, we also recommend enabling two-factor authentication on your Plex account if you haven’t already done so. Lastly, we sincerely apologize for any inconvenience this situation may cause you. We take pride in our security systems, which helped us quickly detect this incident, and we want to assure you that we are working swiftly to prevent potential future incidents from occurring. For step-by-step instructions on how to reset your password, visit: https://support.plex.tv/articles/account-requires-password-reset Thank you, The Plex Team

After I reset my password i had a problem to reclaim my unraid plex server, after some googling this worked for me:

I ended up having to do a plex.tv/claim and then used the new claim code via plex docker console with the following:

curl -X POST "http://localhost:32400/myplex/claim?token=YOUR_CLAIM_TOKEN_HERE"

20 hours ago, Reisga said:

Dear Plex User,

We have recently experienced a security incident that may potentially involve your Plex account information. We believe the actual impact of this incident is limited; however, action is required from you to ensure your account remains secure. What happened An unauthorized third party accessed a limited subset of customer data from one of our databases. While we quickly contained the incident, information that was accessed included emails, usernames, and securely hashed passwords. Any account passwords that may have been accessed were securely hashed, in accordance with best practices, meaning they cannot be read by a third party. Out of an abundance of caution, we recommend you immediately reset your password by visiting https://plex.tv/reset. Rest assured that we do not store credit card data on our servers, so this information was not compromised in this incident. What we're doing We've already addressed the method that this third party used to gain access to the system, and we're undergoing additional reviews to ensure that the security of all of our systems is further hardened to prevent future attacks. What you must do We kindly request that you reset your Plex account password immediately by visiting https://plex.tv/reset. When doing so, there's a checkbox to "Sign out connected devices after password change," which we recommend you enable. This will sign you out of all your devices (including any Plex Media Server you own) for your security, and you will then need to sign back in with your new password. We understand that this means a little more work for you, but it will provide additional security to your account. Additional Security Measures You Can Take We remind you that no one at Plex will ever reach out to you over email to ask for a password or credit card number for payments. For further account protection, we also recommend enabling two-factor authentication on your Plex account if you haven’t already done so. Lastly, we sincerely apologize for any inconvenience this situation may cause you. We take pride in our security systems, which helped us quickly detect this incident, and we want to assure you that we are working swiftly to prevent potential future incidents from occurring. For step-by-step instructions on how to reset your password, visit: https://support.plex.tv/articles/account-requires-password-reset Thank you, The Plex Team

After I reset my password i had a problem to reclaim my unraid plex server, after some googling this worked for me:

I ended up having to do a plex.tv/claim and then used the new claim code via plex docker console with the following:

curl -X POST "http://localhost:32400/myplex/claim?token=YOUR_CLAIM_TOKEN_HERE"

Thank you, thank you, thank you. I spent hours trying to reclaim server.

On 9/9/2025 at 7:42 AM, Reisga said:

Dear Plex User,

We have recently experienced a security incident that may potentially involve your Plex account information. We believe the actual impact of this incident is limited; however, action is required from you to ensure your account remains secure. What happened An unauthorized third party accessed a limited subset of customer data from one of our databases. While we quickly contained the incident, information that was accessed included emails, usernames, and securely hashed passwords. Any account passwords that may have been accessed were securely hashed, in accordance with best practices, meaning they cannot be read by a third party. Out of an abundance of caution, we recommend you immediately reset your password by visiting https://plex.tv/reset. Rest assured that we do not store credit card data on our servers, so this information was not compromised in this incident. What we're doing We've already addressed the method that this third party used to gain access to the system, and we're undergoing additional reviews to ensure that the security of all of our systems is further hardened to prevent future attacks. What you must do We kindly request that you reset your Plex account password immediately by visiting https://plex.tv/reset. When doing so, there's a checkbox to "Sign out connected devices after password change," which we recommend you enable. This will sign you out of all your devices (including any Plex Media Server you own) for your security, and you will then need to sign back in with your new password. We understand that this means a little more work for you, but it will provide additional security to your account. Additional Security Measures You Can Take We remind you that no one at Plex will ever reach out to you over email to ask for a password or credit card number for payments. For further account protection, we also recommend enabling two-factor authentication on your Plex account if you haven’t already done so. Lastly, we sincerely apologize for any inconvenience this situation may cause you. We take pride in our security systems, which helped us quickly detect this incident, and we want to assure you that we are working swiftly to prevent potential future incidents from occurring. For step-by-step instructions on how to reset your password, visit: https://support.plex.tv/articles/account-requires-password-reset Thank you, The Plex Team

After I reset my password i had a problem to reclaim my unraid plex server, after some googling this worked for me:

I ended up having to do a plex.tv/claim and then used the new claim code via plex docker console with the following:

curl -X POST "http://localhost:32400/myplex/claim?token=YOUR_CLAIM_TOKEN_HERE"

This worked dude, been at it all morning until I came across this post, cheers!

On 9/9/2025 at 2:42 AM, Reisga said:

Dear Plex User,

We have recently experienced a security incident that may potentially involve your Plex account information. We believe the actual impact of this incident is limited; however, action is required from you to ensure your account remains secure. What happened An unauthorized third party accessed a limited subset of customer data from one of our databases. While we quickly contained the incident, information that was accessed included emails, usernames, and securely hashed passwords. Any account passwords that may have been accessed were securely hashed, in accordance with best practices, meaning they cannot be read by a third party. Out of an abundance of caution, we recommend you immediately reset your password by visiting https://plex.tv/reset. Rest assured that we do not store credit card data on our servers, so this information was not compromised in this incident. What we're doing We've already addressed the method that this third party used to gain access to the system, and we're undergoing additional reviews to ensure that the security of all of our systems is further hardened to prevent future attacks. What you must do We kindly request that you reset your Plex account password immediately by visiting https://plex.tv/reset. When doing so, there's a checkbox to "Sign out connected devices after password change," which we recommend you enable. This will sign you out of all your devices (including any Plex Media Server you own) for your security, and you will then need to sign back in with your new password. We understand that this means a little more work for you, but it will provide additional security to your account. Additional Security Measures You Can Take We remind you that no one at Plex will ever reach out to you over email to ask for a password or credit card number for payments. For further account protection, we also recommend enabling two-factor authentication on your Plex account if you haven’t already done so. Lastly, we sincerely apologize for any inconvenience this situation may cause you. We take pride in our security systems, which helped us quickly detect this incident, and we want to assure you that we are working swiftly to prevent potential future incidents from occurring. For step-by-step instructions on how to reset your password, visit: https://support.plex.tv/articles/account-requires-password-reset Thank you, The Plex Team

After I reset my password i had a problem to reclaim my unraid plex server, after some googling this worked for me:

I ended up having to do a plex.tv/claim and then used the new claim code via plex docker console with the following:

curl -X POST "http://localhost:32400/myplex/claim?token=YOUR_CLAIM_TOKEN_HERE"

I love this community. Thank you for providing the solution!!

how do i ssh and apply curl -X POST "http://localhost:32400/myplex/claim?token=YOUR_CLAIM_TOKEN_HERE"

12 hours ago, coblck said:

how do i ssh and apply curl -X POST "http://localhost:32400/myplex/claim?token=YOUR_CLAIM_TOKEN_HERE"

You don't need to use ssh, you can press plex docker menu and choose console and type it there, it takes maybe 20sec to pass.

Just a quick heads up for those who reset their password - After resetting my password and getting my server up and running, found my son could no longer connect as a guest user (he has Library access and has been using my server for several years). We tried a bunch of troubleshooting fixes, and found out if you are using an older release of Plex Server that Plex is blocking remote users (server owner can still connect).

Solution is to update to the latest server version - 1.42.1

As a follow-up to the original report and in an abundance of caution due to a population of servers still on an affected Plex Media Server version (versions 1.41.7.x to 1.42.0.x), we have made adjustments for access to affected servers. Specifically, other users to which the server owner has granted access to the server will not be able to connect to it while the server is running an affected version. Once the server is updated to a fixed version, other users will be able to access again. Server owners will still be able to access the server as normal.

Again, we strongly recommend that everyone have their Plex Media Server updated to the most recent version as soon as possible, if you have not already done so.

Source: Plex Media Server - Security Update - Announcements - Plex Forum

Over the weekend I've run into an issue with the docker IMG filling up like a lot of other people have been reporting prior to this. I narrowed it down to a specific directory within the Plex container, /run/plex-temp, please note I have not made ANY changes to this system, docker container or anything until this issue began. I use appdata backup to restore the XML file.

The /run/plex-temp directory fills up with CreditDetection thumbnails and eventually crashes docker, if not the entire array and requires a hard power off to resolve.

I tried rolling back the version to the one prior since the issue started after an upgrade and it still exhibits the same behavior. As a temporary bandaid I've turned off credits detection to stop it from crashing docker/the array. I'm wondering what the methodology would be to change the path for /run/plex-temp to a drive directory so I can see if maybe it just needs extra space temporarily to get an entire scan done or what.

create a path variable for /run/plex-temp and point it to an array/cache path?

EDIT: adding in my plex.xml for current settings.my-plex.xml

Edited September 22, 2025Sep 22 by DeadChimi

On 9/22/2025 at 12:47 PM, DeadChimi said:

Over the weekend I've run into an issue with the docker IMG filling up like a lot of other people have been reporting prior to this. I narrowed it down to a specific directory within the Plex container, /run/plex-temp, please note I have not made ANY changes to this system, docker container or anything until this issue began. I use appdata backup to restore the XML file.

The /run/plex-temp directory fills up with CreditDetection thumbnails and eventually crashes docker, if not the entire array and requires a hard power off to resolve.

I tried rolling back the version to the one prior since the issue started after an upgrade and it still exhibits the same behavior. As a temporary bandaid I've turned off credits detection to stop it from crashing docker/the array. I'm wondering what the methodology would be to change the path for /run/plex-temp to a drive directory so I can see if maybe it just needs extra space temporarily to get an entire scan done or what.

create a path variable for /run/plex-temp and point it to an array/cache path?

EDIT: adding in my plex.xml for current settings.my-plex.xml

Hi @linuxserver.io - This is an urgent matter that needs to be fixed. Thanks in advance.

I have been plagued with this issue for over 2/3 weeks now (havent nailed it when it started but I have been having crashes since then). Something has changed which annoys me way more than it should. I had to destroy my docker.img file twice as it was crashing all containers and server eventually. I could not go into the container to check what was taking so much space, so then I switched to docker folders to investigate this. Today I have the receipts.

This is the bloated folder - Over 67G (67G --> ./c411fe64e3325eae2da44368f02627ba7b12c197d2f15010db4e178140640e47)

/mnt/cache/system/docker/overlay2/c411fe64e3325eae2da44368f02627ba7b12c197d2f15010db4e178140640e47/
├── diff (33G)
│   ├── ...
│   ├── run (33G)
│   │   └── plex-tmp (33G)
│   │       └── PlexCreditsDetection-de8cedc6-e9c0-448d-bd02-ffc962f4181e (33G)
│   ├── ...
├── ...
├── merged (34G)
│   ├── ...
│   ├── run (34G)
│   │   └── plex-tmp (34G)
│   │       └── PlexCreditsDetection-de8cedc6-e9c0-448d-bd02-ffc962f4181e (34G)
│   ├── ...
│   ├── ...
└── ...

I have got these sizes from du -sh ./* command for all folders.

Here is my Plex template. I am mapping the Transcoder temporary directory - /transcode to RAMDISK and Downloads temporary directory - /tmp to TEMP folder on the Plex config drive.

root@Tower:/boot/config/plugins/dockerMan/templates-user# cat my-plex.xml
<?xml version="1.0"?>
<Container version="2">
  <Name>plex</Name>
  <Repository>linuxserver/plex</Repository>
  <Registry>https://hub.docker.com/r/linuxserver/plex/</Registry>
  <Network>host</Network>
  <MyIP/>
  <Shell>bash</Shell>
  <Privileged>false</Privileged>
  <Support>https://forums.unraid.net/topic/40463-support-linuxserverio-plex-media-server/</Support>
  <Project>https://www.plex.tv/</Project>
  <Overview>Plex organizes video, music and photos from personal media libraries and streams them to smart TVs, streaming boxes and mobile devices.&#xD;
&#xD;
Nvidia GPU Use&#xD;
Using the Unraid Nvidia Plugin to install a version of Unraid with the Nvidia Drivers installed and&#xD;
 add --runtime=nvidia to "extra parameters" (switch on advanced view) and&#xD;
copy your GPU UUID to NVIDIA_VISIBLE_DEVICES.&#xD;
&#xD;
Intel GPU Use&#xD;
Edit your go file to include:&#xD;
modprobe i915&#xD;
, save and reboot, then &#xD;
add --device=/dev/dri to "extra parameters" (switch on advanced view)</Overview>
  <Category>MediaServer:Video MediaServer:Music MediaServer:Photos</Category>
  <WebUI>http://[IP]:[PORT:32400]/web</WebUI>
  <TemplateURL>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/plex.xml</TemplateURL>
  <Icon>https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-icon.png</Icon>
  <ExtraParams>--runtime=nvidia --no-healthcheck</ExtraParams>
  <PostArgs/>
  <CPUset>12,13,14,15,36,37,38,39,16,17,18,19,20,21,22,23,40,41,42,43,44,45,46,47</CPUset>
  <DateInstalled>1758649637</DateInstalled>
  <DonateText/>
  <DonateLink/>
  <Requires/>
  <Config Name="VERSION" Target="VERSION" Default="" Mode="" Description="VERSION" Type="Variable" Display="always" Required="false" Mask="false">docker</Config>
  <Config Name="Nvidia Visible Devices" Target="NVIDIA_VISIBLE_DEVICES" Default="" Mode="" Description="Nvidia Visible Devices (Optional - Requires Nvidia GPU and Unraid Nvidia build)" Type="Variable" Display="always" Required="false" Mask="false">GPU-xxxxxxx-MASKED-xxxxxxx</Config>
  <Config Name="Media" Target="/media/" Default="/mnt/user/media/" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/media/</Config>
  <Config Name="Transcode" Target="/transcode" Default="" Mode="rw" Description="Path for transcoding folder (Optional)" Type="Path" Display="always" Required="false" Mask="false">/tmp/plex-ramdisk</Config>
  <Config Name="Webtools" Target="33400" Default="33400" Mode="tcp" Description="" Type="Port" Display="always" Required="false" Mask="false">33400</Config>
  <Config Name="Temp directory" Target="/tmp" Default="/mnt/plex_appdata/plex/tmp" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/plex_appdata/plex/tmp</Config>
  <Config Name="Appdata" Target="/config" Default="" Mode="rw" Description="Appdata" Type="Path" Display="advanced" Required="false" Mask="false">/mnt/plex_appdata/plex/</Config>
  <Config Name="Webui" Target="32400" Default="32400" Mode="tcp" Description="For access to the Plex Media Server Webui (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32400</Config>
  <Config Name="Plex Companion" Target="3005" Default="3005" Mode="tcp" Description="For controlling Plex Home Theater via Plex Companion (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">3005</Config>
  <Config Name="Roku via Plex Companion" Target="8324" Default="8324" Mode="tcp" Description="For controlling Plex for Roku via Plex Companion (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">8324</Config>
  <Config Name="Plex DLNA Server" Target="32469" Default="32469" Mode="tcp" Description="For access to the Plex DLNA Server (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32469</Config>
  <Config Name="Plex DLNA Server" Target="1900" Default="1900" Mode="udp" Description="For access to the Plex DLNA Server (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">1900</Config>
  <Config Name="GDM network discovery" Target="32410" Default="32410" Mode="udp" Description="For current GDM network discovery (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32410</Config>
  <Config Name="GDM network discovery" Target="32412" Default="32412" Mode="udp" Description="For current GDM network discovery (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32412</Config>
  <Config Name="GDM network discovery" Target="32413" Default="32413" Mode="udp" Description="For current GDM network discovery (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32413</Config>
  <Config Name="GDM network discovery" Target="32414" Default="32414" Mode="udp" Description="For current GDM network discovery (No effect in host mode - reference only)" Type="Port" Display="advanced" Required="false" Mask="false">32414</Config>
  <Config Name="PUID" Target="PUID" Default="" Mode="" Description="PUID" Type="Variable" Display="advanced" Required="false" Mask="false">99</Config>
  <Config Name="PGID" Target="PGID" Default="" Mode="" Description="PGID" Type="Variable" Display="advanced" Required="false" Mask="false">100</Config>
  <TailscaleStateDir/>
</Container>

Also, to add the actual mapped /tmp and /transcode folders are completely empty.

root@Tower:/mnt/plex_appdata/plex# du -sh ./*
230G    ./Library
0       ./tmp

root@Tower:/tmp# du -sh ./*
... more folders
0       ./plex-ramdisk
... more folders

Edited September 25, 2025Sep 25 by Unraid-arr
clarity, more info

This needs to be reported to Plex. We do not have control where plex dumps it's temp files for credit detections/sonic analysis.

7 hours ago, j0nnymoe said:

This needs to be reported to Plex. We do not have control where plex dumps it's temp files for credit detections/sonic analysis.

Done. Thanks

https://forums.plex.tv/t/plex-server-dumping-temp-files-for-credit-detections-sonic-analysis-inside-container/931758

On 9/25/2025 at 12:58 PM, j0nnymoe said:

This needs to be reported to Plex. We do not have control where plex dumps it's temp files for credit detections/sonic analysis.

So, @j0nnymoe it turns out it is not a Plex issue rather a LSIO issue. 'TMPDIR=/run/plex-temp' is specified by your build process.

Look at what I found on your build - https://hub.docker.com/layers/linuxserver/plex/latest/images/sha256-9170109a442498630befe62f8236c68ddd7da21cf66c606f9a390dacf931a6e2

TMPDIR=/run/plex-temp

ENV DEBIAN_FRONTEND=noninteractive PLEX_DOWNLOAD=https://downloads.plex.tv/plex-media-server-new PLEX_ARCH=amd64 PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR=/config/Library/Application Support PLEX_MEDIA_SERVER_HOME=/usr/lib/plexmediaserver PLEX_MEDIA_SERVER_MAX_PLUGIN_PROCS=6 PLEX_MEDIA_SERVER_USER=abc PLEX_MEDIA_SERVER_INFO_VENDOR=Docker PLEX_MEDIA_SERVER_INFO_DEVICE=Docker Container (LinuxServer.io) TMPDIR=/run/plex-temp

This was first added to 1.41.0 - https://hub.docker.com/layers/linuxserver/plex/1.41.0/images/sha256-dff1f3af12fc385eb3a13901480ce62cd6b2e64f74897cc7d6a13a2922bf5f5a

Before that the last image without this TMPDIR variable is 1.40.5 - https://hub.docker.com/layers/linuxserver/plex/1.40.5/images/sha256-55ca5b9bb96ded7a0ea54f6579ad8285cec7822869f86c88a1bfedd3cf4febcd

I am assuming this makes it so that the docker variable for temp folder gets ignored as well. Please fix thanks.

Edited September 29, 2025Sep 29 by Unraid-arr
more info

Good spot - we'll look into it.

Side note, why plex think it's a good idea to use the TMPDIR for stuff that they know is going to use a large amount of space rather than the user configurable path (like transcoding etc) is an absolute mystery.

We could move it back to the default /tmp but the same thing will happen unless users have mounted /tmp to tmpfs (but that will then break read-only and non-root operation)

Worth adding too, while whatever fix we put in place, you're still going to need storage somewhere & it won't fix the fact that plex is creating these large files which then sometimes don't get removed when finished with.

Edited September 29, 2025Sep 29 by j0nnymoe

1 hour ago, j0nnymoe said:

Good spot - we'll look into it.

Side note, why plex think it's a good idea to use the TMPDIR for stuff that they know is going to use a large amount of space rather than the user configurable path (like transcoding etc) is an absolute mystery.

We could move it back to the default /tmp but the same thing will happen unless users have mounted /tmp to tmpfs (but that will then break read-only and non-root operation)

Worth adding too, while whatever fix we put in place, you're still going to need storage somewhere & it won't fix the fact that plex is creating these large files which then sometimes don't get removed when finished with.

Thanks for acknowledging the issue and helping to resolve it. I cannot say for others but what I do is what has been preached by all YouTubers who make UnRaid content (not naming anyone specific). This is my config that is relevant and is how it's been told to do it for ages now. I transcode to RAM and put temp data to a folder in config directory. Ideally, I expect all this data to be deleted by Plex as it is done processing and especially on container restart if it crashed and restarted. But regardless the ram disk will be cleared if the machine is restarted.

Whenever Plex fixes their end of the issues and tmp folder works as intended, I would switch that to RAM disk as well. There is no reason for me to have it on persistent storage. It is literally called temp folder.

  <Config Name="Transcode" Target="/transcode" Default="" Mode="rw" Description="Path for transcoding folder (Optional)" Type="Path" Display="always" Required="false" Mask="false">/tmp/plex-ramdisk</Config>
  <Config Name="Temp directory" Target="/tmp" Default="/mnt/plex_appdata/plex/tmp" Mode="rw" Description="" Type="Path" Display="always" Required="false" Mask="false">/mnt/plex_appdata/plex/tmp</Config>
  <Config Name="Appdata" Target="/config" Default="" Mode="rw" Description="Appdata" Type="Path" Display="advanced" Required="false" Mask="false">/mnt/plex_appdata/plex/</Config>

👇🏻This below is absolutely on Plex, who know if they will even listen to me. They have been ignoring customer feedback for a while now. I did create the issue on their forum as you suggested. If you would like to add your investigation to it, please be my guest. Plex Forum Link

1 hour ago, j0nnymoe said:

Worth adding too, while whatever fix we put in place, you're still going to need storage somewhere & it won't fix the fact that plex is creating these large files which then sometimes don't get removed when finished with.

👇🏻I used to do it this way before, but to investigate I replaced with the above config and stuck with it. I have 128GB RAM so that is not an issue for me.

  <ExtraParams>--runtime=nvidia --mount type=tmpfs,destination=/tmp,tmpfs-size=17179869184 --no-healthcheck</ExtraParams>

Thanks 🙂

Edited September 29, 2025Sep 29 by Unraid-arr
clarity

How to fix date 'date added' for movies in Plex webUI after moving all my movies to a different host path?

What I changed:

Old docker host path for movies: /mnt/user/media/movies

New docker host path for movies: /mnt/user/data/media/movies

(I did not change the docker container path or the path in Plex, it has always been: '/movies'

After moving all my movies files using the 'mv' command via Unraid CLI, updating the host path as noted above, and restarting the Plex docker; I noticed all my movies show a "date added" value of the day I moved the data. In this case it shows added "2 days ago" or 9/28/25 if I hover over it.

As a result, this changed my "continue watching" section on the home screen and skewed sorting in general.

I am working on a PHP script to fix this by updating the "date added" value either from the actual file created timestamp or from another field in the Plex DB.

I started this post on the Plex forums below and shared the script. But I need help determining the right field to update so the Plex webUI "date added" is restored to the correct value.

https://forums.plex.tv/t/change-movies-date-added-to-file-creation-date/931969