# \[SOLVED\] PMS - Crash Upon Refresh Metadata

**URL:** <https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561>\
**Category:** Plex Media Server\
**Tags:** server-linux, server-docker, library-management, metadata\
**Created:** [June 11, 2026, 2:45am UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561 "2026-06-11T02:45:07Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![shelfactor](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@shelfactor](https://forums.plex.tv/u/shelfactor)\
**Post date:** [June 11, 2026, 2:45am UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561/1 "2026-06-11T02:45:07Z")

</div>

Server Version#: Version 1.43.2.10687  
Player Version#: NA

I use the stable release of [LinuxServer.io](http://LinuxServer.io) Plex Media Server, currently up to date.

When I go into any TV show and click Refresh Metadata on the show page, the refresh will start then, it will go to to the page below, before being redirected back to the show page.

 ![image](https://global.discourse-cdn.com/plex/original/4X/a/d/e/adebbf7416ce9143f22431eff00dc1a900de5078.jpeg)

However, when back to the show page, the connection is effectively dropped. I need to refresh before any interaction can be made again.

\*\* This error also will drop any and all connections to the server. All user streams, all ‘arr’ stack apps. All connections need to be re-established.

---

<div class="post-metadata">

**Author:** ![shelfactor](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@shelfactor](https://forums.plex.tv/u/shelfactor)\
**Post date:** [June 11, 2026, 3:28am UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561/2 "2026-06-11T03:28:04Z")

</div>

Rolled back to PMS Version 1.43.1.10611

Issue is reproducible.

---

<div class="post-metadata">

**Author:** ![shelfactor](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@shelfactor](https://forums.plex.tv/u/shelfactor)\
**Post date:** [June 11, 2026, 3:40am UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561/3 "2026-06-11T03:40:36Z")

</div>

Back to latest stable release.

I attempted to turn on ‘require secure connections’ in the network tab. Now this error shows for the brief moment

 ![image](https://global.discourse-cdn.com/plex/original/4X/1/c/8/1c86e87d8f6949a4287d9dd8817e08553eaedc5f.jpeg)

---

<div class="post-metadata">

**Author:** ![shelfactor](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@shelfactor](https://forums.plex.tv/u/shelfactor)\
**Post date:** [June 11, 2026, 3:42am UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561/4 "2026-06-11T03:42:07Z")

</div>

This is occurring when accessing PMS via direct IP address on local network, as well as through [app.plex.tv](http://app.plex.tv)

---

<div class="post-metadata">

**Author:** ![drzoidberg33](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/drzoidberg33/32/4184_2.png) [@drzoidberg33](https://forums.plex.tv/u/drzoidberg33)\
**Post date:** [June 11, 2026, 8:54am UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561/5 "2026-06-11T08:54:54Z")

</div>

Please provide [server logs.](https://support.plex.tv/articles/200250417-plex-media-server-log-files/)

---

<div class="post-metadata">

**Author:** ![shelfactor](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@shelfactor](https://forums.plex.tv/u/shelfactor)\
**Post date:** [June 11, 2026, 4:21pm UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561/6 "2026-06-11T16:21:08Z")

</div>

[Plex Media Server Logs\_2026-06-11\_12-18-42.zip](https://forums.plex.tv/uploads/short-url/1Nk1pkcgSr7CIYv49yWxZ2Jb4NX.zip) (341.8 KB)

Thank you for taking a look!

I stopped my Plex containter.

Cleared my log folder prior to this test (just backed it up and renamed it).

Restarted plex.

Then attempted to “refresh Metadata” on a tv show.

---

<div class="post-metadata">

**Author:** ![shelfactor](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@shelfactor](https://forums.plex.tv/u/shelfactor)\
**Post date:** [June 15, 2026, 7:05pm UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561/7 "2026-06-15T19:05:25Z")

</div>

I have noticed many of my posters are not downloading fully.

Trying to refresh the metadata on the series page produces the same error mentioned above.

Even after manually selecting a ‘full’ image poster, performing a Metadata refresh will still produce the error.

 ![Screenshot 2026-06-15 at 3.02.02 PM](https://global.discourse-cdn.com/plex/original/4X/3/d/5/3d59e573e8bcaeb38cfa9415de4bee1f76865620.jpeg)

 ![Screenshot 2026-06-15 at 3.02.25 PM](https://global.discourse-cdn.com/plex/original/4X/2/2/1/221e6e04a1da614d30e85ae24bd663a1f5bcb65d.jpeg)

Updated logs attached.

[Plex Media Server Logs\_2026-06-15\_15-04-57.zip](https://forums.plex.tv/uploads/short-url/lCrBFskO683TjUPYd6P6Nmqx0nr.zip) (1.6 MB)

---

<div class="post-metadata">

**Author:** ![shelfactor](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@shelfactor](https://forums.plex.tv/u/shelfactor)\
**Post date:** [June 16, 2026, 4:09am UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561/8 "2026-06-16T04:09:33Z")

</div>

Confirmed same issue on Chrome and Safari.

Changed Docker Network interface to host, to remove any translation… Issue Persists

Updated Logs, after many issue re-creation.

[Plex Media Server Logs\_2026-06-16\_00-09-52.zip](https://forums.plex.tv/uploads/short-url/uEw4cqyUWEnOBYGX5ibjNSLoiJg.zip) (2.5 MB)

---

<div class="post-metadata">

**Author:** ![shelfactor](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@shelfactor](https://forums.plex.tv/u/shelfactor)\
**Post date:** [June 16, 2026, 5:03pm UTC](https://forums.plex.tv/t/solved-pms-crash-upon-refresh-metadata/939561/9 "2026-06-16T17:03:33Z")

</div>

**PROBLEM FOUND & SOLVED**

TLDR: There was a corrupt show/season-metadata poster item; still unsure if it’s from Plex metadata or just within my instance of PMS.

**Recap:**

What I noticed, was when refreshing any metadata, whether it be adding a show, or refreshing a match, or manually refreshing a series; Plex would show the insecure connection / not connected error page:

 ![image](https://global.discourse-cdn.com/plex/original/4X/a/d/e/adebbf7416ce9143f22431eff00dc1a900de5078.jpeg)

This would follow by a ‘dropped’ connection to plex. Even though the Plex page would retun, it wasn’t ‘connected/active’. I would have to refresh the page for the connection to restart. \*\* This also created connection issues for concurrent streams, and connections to Arr Apps.

As mentioned in the original post, I am using Unraid (7.3.1) with the LinuxServer Plex Media Sever docker app. I started noticing these **segfault** log entries in the Unraid System Logs _ **NOTE:** I don’t know if these are an ‘error’ or just Unraid noticing an issue and logging it; however it helped me to determine the time of the crash etc. I figured it was worth showing._

 ![Screenshot 2026-06-16 at 12.33.47 AM](https://global.discourse-cdn.com/plex/original/4X/b/c/8/bc8caa84a1c28c31a213e7e3491f4b042d0fa871.jpeg)

 ![Screenshot 2026-06-16 at 2.00.23 AM](https://global.discourse-cdn.com/plex/original/4X/8/8/2/882bc0c536f71b1b4b2e7d0d202a0e559d47da16.jpeg)

**Finding the solution:**  
I was looking at the logs, while the issue would cause a crash in PMS, the server would restart itself; thus creating a stop/start in the log files.

When looking at the Logs folder, the newest ‘Plex Media Server.log’ would be POST-crash PMS restarting logs. Therefore, I would also look at ‘Plex Media Server.1.log’ ; at the very bottom would be the most recent PRE-crash log data.

**Common Scan Item:**

After recreating a crash, and looking at the logs I would see the same item being mentioned:

_Jun 16, 2026 01:29:26.823 [22780692044600] DEBUG - [Req#195] Calculated media file path for path [metadata://posters/tv.plex.agents.series\_253ca1dbc53495f5f0f6525084710d20076e2303]: [“/config/Library/Application Support/Plex Media Server/Metadata/TV Shows/4/16e0da2e7e75b5ae2195861c6d3e5db45dc2a23.bundle/Contents/\_combined/posters/tv.plex.agents.series\_253ca1dbc53495f5f0f6525084710d20076e2303”]_

**Problematic Item:**

From the Unraid Logs, I saw that libfreeimage.so was part of the segfault; thus I started to assume that the issue may be an artwork issue.

I located the item mentioned above and copied it to a test location. I then renamed it to test.jpg (as my assumption was that it was a corrupt artwork of sorts). The resulting file appeared to be normal, and viewable. _Results from checking the original file as identifiable:_

 ![Screenshot 2026-06-16 at 1.37.15 AM](https://global.discourse-cdn.com/plex/original/4X/7/4/0/740e66d87e717ed17a09f669e3444cc69642b275.png)

The image showed that the TV Show in question happened to be Third Watch, Season Two poster

**Testing Solution:**

To attempt to remediate the issue, I removed the entire show folder from the TV Shows library directory. Then re-scanned the library. **The issue was gone.** I was able to refresh any show/item as many times as I wanted. Even some shows that weren’t matched and updated with metadata updated immediately.

**Further Solution Testing:**

With the show outside of PMS, I made sure that empty trash was turned on, re-scanned all libraries, re-started PMS for good measure. I performed Optimize Database (I had done this prior during earlier troubleshooting numerous times, but did it now, just for good measure), I performed clean bundles. Basically any task that I could do, to refresh PMS.

Once complete, I moved the entire show back into the library folder. **The issue returned, same as prior.** I could not update metadata for any show/season/item, without the crash occurring.

I removed the full show back outside of PMS, refreshed. And once it was removed, I added back only Season One. PMS updated immediately and added the show. _I noticed that it was matching to metadata in a foreign language, but the show was correct._

I re-matched the show to ensure it was picking up the correct information. **No Issue**

I added back Season Two, **Issue returned** … So i removed it again. **No Issue**

I added back Seasons 3-6. **No Issue**

**Obviously at this point, it appears the issue is something with Season Two**

Since my original findings had me believing that the issue was with the metadata and/or the artwork for Season Two. I found the correct artwork for Season Two, named it according to Plex naming standards. Then I added the Season Two folder AND the Season Two artwork AT THE SAME TIME. **No Issue**

**Final Conclusion:**

It appears that either my artwork for Season Two of Third Watch, as found by Plex, is causing the issue. When I removed my custom artwork, the issue returns immediately.

_This is how the Season Two poster selection shows after removing my custom artwork, with the issue present._

 ![Screenshot 2026-06-16 at 12.53.16 PM](https://global.discourse-cdn.com/plex/original/4X/c/6/6/c66bf1c816e2063046fd9e15004a14a7ac7d8e45.jpeg)

To re-eliminate the issue, I have to remove Season Two, then add it back with custom artwork at the same time.

**Future Testing:**  
I will have to use my second instance on Unraid/LIO-Plex and test to see if this is a global issue for Plex, or if there is something wrong in my database.
