Core component error

[McWanke]

Appreciate the information here! We are still working on it and this helps!

[curtis.bishop]

I was just doing a clean install on linux and had this issue. I switched to a windows install and the issue persists. It is happens on localhost, specific ip and app.plex.tv all the same. Once clicked through the server seems working fine, but it does appear every time.

[seabound64]

Me too- first timer here with new install on MacBook Air/Monterey

Sorry cannot find log files anywhere!

[centavi]

Today I installed Proxmox 9 and I’m also getting this error. At first, I thought it was a Promox issue, but it doesn’t work on Ubuntu either. I’m here to check on the forum to see that many people are having problems with the new version of PLEX.

[tom80H]

see the linked support article – you can either download the server logs from the server settings in the web app, or find them in your local file system.

[shibber]

Plex Media Server Logs_2025-08-09_22-48-39.zip (361.7 KB)

ran into the same issue, tried to reinstall on unRAID server, still doesn’t work… relegated to reading this evening. Here are my logs.

[Sinoraptor]

I have been scratching my head for an hour before finding this thread, so let me add my experience:

• I am running Proxmox VE 8.4 with kernel 6.11.11-2-pve (opt-in) on an x86-64 AMD server
• I am installing Plex in a container based on their (Proxmox provided) debian-12-standard_12.7-1_amd64.tar.zst template.
• I am creating an unprivileged container with nesting support enabled (to make systemd namespaces happy).
• I am installing plexmediaserver_1.42.1.10054-f333bdaa8_amd64.deb (sha1:8969768c34b365d7eb481101ada401cbd9627e79)
• This is a new install, and I have reproduced it multiple times on fresh containers
  • Another server I run, running PVE 8.3 with kernel 6.8 (on an Intel x86-64 platform), in a Debian 12 LXC container configured the same way, was able to be upgraded to 1.42.1.10054 (via the apt/deb repo) and is not giving me this problem so far

Edit: To clarify my experience with the bug:

• During initial setup, I get the core component error message
• I can skip past it by clicking the 1st tab of the setup, and I can finish setup even, add libraries, stream media, etc
• Every time I go to the web UI (/web/index.html), however, I am met with the setup page again
  • I still get the core component error
  • And I can still click into the tabs and get past it

However, clearly there is some internal state that is messed up…

IMO this installer should be pulled until it’s fixed

[Sinoraptor]

Thanks for providing that link Keir- I can confirm dropping plexmediaserver_1.41.9.9961-46083195d_amd64.deb into my Ansible playbook solved my issue and the server installed without getting stuck.

(I will not be upgrading via apt until a fix is released, however, because I have sunk enough time into this tonight.)

[patrik_2199]

Server Version#: v.1.42.1.10054-f333bdaa8
Player Version#: 1.42.1.10054
With a fresh Debian 13 install, I have an issue where Plex falls back to the setup wizard screen with an error “A problem has been detected with a core component of Plex Media Server”
The server works if I press finish-done, but upon refreshing the web page, it falls back to the same setup wizard with this error. I have attached the logs.

Plex Media Server Logs_2025-08-10_11-20-26.zip (46.4 KB)

MOD EDIT: Moved your post to this thread, as it is the same issue. @FordGuy61

[igor_assis]

@ChuckPa - Anything for Windows x64 by any chance? I’m facing the exact same issues with Windows 11 IoT LTSC, thanks.

[ChuckPa]

ALL:

This is top priority for Engineering.

As soon as they have a working resolution which is stable,

I will post here and provide upgrade links.

[stinkbug55]

For you redhat/fedora people, here is their previous version link for “Fedora (27+) / CentOS (7+) / SUSE (15+) - Intel/AMD 64-bit” :

Edit: NVM, support says not to use this version (1.41.9.9961-46083195d) although it’s working fine for me

[ChuckPa]

I have the steps to get over the Core Component Error.

It’s a hiccup in Plex/web talking to PMS as it starts.

Specifically, it faults when PMS launches the Setup Wizard.

You can get around it by invoking the Setup Wizard manually.

1. install PMS
2. Open it in the web browser
3. Sign in
4. Get the “Got it”
5. At this point, you will see the error
   
   

Invoke the Setup Wizard

1. Click “Name”
2. Now proceed normally through the Setup Wizard

[avoidwork]

That doesn’t solve the issue. If you reload the page it’s back at the server setup window.

Could you provide links for the previous version?

[bbtr44]

I have the exact same problem I just installed debian 13 it fails with same error. i have installed it many time on many different versions of linux no issues even Ubuntu 25.10 snapshot 3 worked like a charm.. This time I tried in on M4 macMini just to see it was just debian 13 but no it happens on Tahoe 26 beta as well hope this helps

PLEASE DISREGARD I just re-read and clicking on name seems to have worked.

Apologies

[dklogic]

Plex Media Server Downgrade – Ubuntu LXC container under Proxmox

Verify Current Installation

Check your current Plex version and status:

# Check service status
sudo systemctl status plexmediaserver

# Check installed package version
dpkg -l | grep plexmediaserver

Important Notes

• This procedure will temporarily stop your Plex server

• Consider backing up your Plex configuration before proceeding

• Configuration location: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/

Step 1: Stop Plex Service

sudo systemctl stop plexmediaserver

Step 2: Download Target Version

Download the specific 1.41.6 release package:

wget https://artifacts.plex.tv/plex-media-server-stable/1.41.6.9685-d301f511a/debian/plexmediaserver_1.41.6.9685-d301f511a_amd64.deb

Note: This download link was sourced from the Plex community forums thread addressing core component errors.

Step 3: Install Downgraded Version

Use dpkg to install the older version:

sudo dpkg -i plexmediaserver_1.41.6.9685-d301f511a_amd64.deb

Expected output should show:

dpkg: warning: downgrading plexmediaserver from 1.42.1.10054-f333bdaa8 to 1.41.6.9685-d301f511a
...
PlexMediaServer install: PlexMediaServer-1.41.6.9685-d301f511a - Installation successful.

Step 4: Start Plex Service

Restart the Plex service with the downgraded version:

sudo systemctl start plexmediaserver

Verification

Check Service Status

Verify the service is running correctly:

sudo systemctl status plexmediaserver

Look for:

• Active: active (running)

• Version string showing 1.41.6.9685-d301f511a

• Multiple plugin processes loaded successfully

Verify Version

Confirm the downgrade was successful:

# Check service output for version string
sudo systemctl status plexmediaserver | grep "server-version"

Should show: --server-version 1.41.6.9685-d301f511a

Test Web Interface

Access your Plex web interface to confirm functionality:

http://your-server-ip:32400/web

Prevention (Optional)

Hold Package Version**#**

To prevent automatic updates back to the problematic version:

sudo apt-mark hold plexmediaserver

Remove Hold (When Ready to Update)

When you want to allow updates again:

sudo apt-mark unhold plexmediaserver

[ChuckPa]

Folks,

Having chatted with Engineering, here is the official workaround while they fix the problem.

PMS v1.42.1 Core Component Error Workaround and Information

Hi everyone!! Wanted to create a centralized place for communications around the status of this issue as it is popping up in a bunch of places. First - we have a solid understanding of what is causing this issue and will be working to validate a new build that addresses this over the next few days. First - this is a bug that was introduced in the beta version 1.42.0 (we have successfully replicated this in this version) and is only related to the embedded web client and most are now seeing it …

Closing this thread in favor of the centralized thread.