Error starting framework core plugins

Plex Media Server Desktops & Laptops
1

Server Version#: --server-version 1.13.8.5395-10d48da0d
Player Version#: latest

Oct 07 09:34:53 jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/MoviePosterDB.bundle.
Oct 07 09:34:53 jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/HTbackdrops.bundle.
Oct 07 09:34:54 jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/TheTVDB.bundle.
Oct 07 09:37:53 jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/LyricFind.bundle.
Oct 07 09:37:53 jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/OpenSubtitles.bundle.
Oct 07 09:37:54 jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/TheMovieDB.bundle.
Oct 07 09:39:23 jupiter sh[4819]: Connection to 45.33.70.183 closed by remote host.
Oct 07 09:40:53 jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/PlexThemeMusic.bundle.
Oct 07 09:41:08 jupiter sh[4819]: Error starting framework core for /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-
Oct 07 09:43:55 jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/PlexMovie.bundle.
~
~

When using plex with a vpn,nordvpn, plex system plugins failed to start with error above. I have White listed plex ports in the Vpn setup based on info listed on plex website.
Here’s example of that:
ACCEPT udp – anywhere anywhere ctstate NEW udp dpt:32600
ACCEPT tcp – anywhere anywhere ctstate NEW tcp dpt:32600
ACCEPT udp – anywhere anywhere ctstate NEW udp dpt:32400
ACCEPT tcp – anywhere anywhere ctstate NEW tcp dpt:32400
And many more.

Plex is accessible locally but due to core plugins failed to start plex players randomly restarting or failing during media browse, resume playback etc. This also result in blank page. And of course any operation that require plugins such as retrieving media metadata doesn’t seem to work.
But simple playback always work.
Interestingly, android mobile seems to work pretty well with less chance of crashing while trying to resume, less chance of having blank page. But it’s noticeably slower load of posters. Android tv having the most terrible experience crashing the most even more than iPhone.
Without Vpn, everything works perfectly.

Just to be clear plex media server is in a box with Vpn with plex related ports white listed to enable local home network access. All plex clients do no use VPN.

All these tests are done within home network and despite using Vpn, media streaming was confirmed done within local network.

What can I do to fix this?
Is there comprehensive list of ports that plex.direct, plex plugins and core components use so that I can whitelist in my Vpn setup so that it won’t use VPN?

2

This is all you need except what a 3rd party plug-in might also require.

https://support.plex.tv/articles/201543147-what-network-ports-do-i-need-to-allow-through-my-firewall/

All other ports are internal and stay within the server to its loopback adapter.

3

Thanks but I did that already with the same errors

jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/PlexThemeMusic.bundle.
Oct 07 09:41:08 jupiter sh[4819]: Error starting framework core for /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-
Oct 07 09:43:55 jupiter sh[4819]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-10d48da0d/PlexMovie.bundle.
Oct 07 10:58:11 jupiter sh[4819]: Connection to 184.105.148.104 closed by remote host.
Oct 07 10:58:11 jupiter sh[4819]: Connection to 184.105.148.104 closed by remote host.
Oct 07 12:01:22 jupiter sh[4819]: Connection to 192.155.93.49 closed by remote host.
Oct 07 12:05:03 jupiter sh[4819]: Connection to 172.104.29.70 closed by remote host.
Oct 07 12:12:59 jupiter sh[4819]: Connection to 184.105.148.104 closed by remote host.
Oct 07 12:59:33 jupiter sh[4819]: Connection to 184.105.148.104 closed by remote host.

I also think that link is not all. It doesn’t list 32401 for instance.
As I use my pms more with Vpn, it appears that everything works except anything that require plex system plugins. I do not use third party plugins. Somehow plugins can’t work behind Vpn. Why is that?
Plex will not do proper scanning and matching media while on Vpn.
While browsing and media playback is stable enough, there’s a notable delay to open movie or tv show episode detail page compared to when Vpn is off. But I can see all traffic is internal between plex server and client.

This leads me to think that plex core plugins do some tunneling or something that breaks with the use of vpn. Or stuff in general becomes shower when plexmediaserver Relay doesn’t work, which is acceptable because it’s behind Vpn and my Vpn doesn’t support external port forward.
What is not acceptable is why it also somewhat break when playing it inside home network.

4

Port 32401 is a Plex internal-use-only port. There are no external connections to it.

The published ports are those which are to be allowed.

Your error implies a corrupt installation.

I would like to see the rest of the logs (Settings - Server - Help - Download Logs) as well as the journalctl -xe logs for that same time period.

Diagnosing from a fragment is insufficient.

5

I do not think it is corrupt installation unless this is caused by auto update plex latest update. In fact, everything works perfectly all this time without Vpn. I only noticed this when I start using Vpn.

I have to disable Vpn just to download logs because server settings are not accessible in plex Web. See attached.

6

The plug-ins are failing because of the database.

SLOW QUERY means PMS, and the plug-ins, cannot access the DB in time.
Without the DB operating smoothly, nothing will work.

Please Opimize the database then restart PMS.

Oct 07, 2018 09:31:10.556 [0x7f7c62bfa700] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.0.15 to 239.255.255.250: Operation not permitted
Oct 07, 2018 09:31:20.556 [0x7f7c643fd700] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.0.15 to 239.255.255.250: Operation not permitted
Oct 07, 2018 09:31:25.669 [0x7f7c57bf9700] ERROR - Timeout or error reading status line from plug-in pipe [com.plexapp.agents.lastfm], we're killing it.
Oct 07, 2018 09:31:25.669 [0x7f7c57bf9700] ERROR - Error received reading configuration for com.plexapp.agents.lastfm
Oct 07, 2018 09:31:25.672 [0x7f7c573f8700] ERROR - Timeout or error reading status line from plug-in pipe [com.plexapp.agents.none], we're killing it.
Oct 07, 2018 09:31:25.673 [0x7f7c573f8700] ERROR - Error received reading configuration for com.plexapp.agents.none
Oct 07, 2018 09:31:25.676 [0x7f7c57bf9700] WARN - SLOW QUERY: It took 3030.000000 ms to retrieve 1 items.
Oct 07, 2018 09:31:25.676 [0x7f7c573f8700] WARN - SLOW QUERY: It took 3040.000000 ms to retrieve 1 items.
Oct 07, 2018 09:31:25.676 [0x7f7c56bf7700] ERROR - Timeout or error reading status line from plug-in pipe [com.plexapp.agents.imdb], we're killing it.
Oct 07, 2018 09:31:25.676 [0x7f7c56bf7700] ERROR - Error received reading configuration for com.plexapp.agents.imdb
Oct 07, 2018 09:31:25.680 [0x7f7c56bf7700] WARN - SLOW QUERY: It took 2460.000000 ms to retrieve 1 items.
Oct 07, 2018 09:31:30.557 [0x7f7c663ff700] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.0.15 to 239.255.255.250: Operation not permitted
Oct 07, 2018 09:31:40.557 [0x7f7c63bfc700] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.0.15 to 239.255.255.250: Operation not permitted
Oct 07, 2018 09:31:40.687 [0x7f7c643fd700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2018 09:31:40.688 [0x7f7c643fd700] ERROR - Error parsing content.
Oct 07, 2018 09:31:40.689 [0x7f7c643fd700] ERROR - Exception caught while updating system agent list: Error parsing file
Oct 07, 2018 09:31:42.653 [0x7f7c4e3fe700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2018 09:31:42.711 [0x7f7c64bfe700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2018 09:31:42.728 [0x7f7c5bbfe700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2018 09:31:43.059 [0x7f7c4ebff700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2018 09:31:43.147 [0x7f7c583fa700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2018 09:31:43.172 [0x7f7c53bf1700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2018 09:31:50.558 [0x7f7c63bfc700] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.0.15 to 239.255.255.250: Operation not permitted
Oct 07, 2018 09:31:53.187 [0x7f7c533f0700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2018 09:31:53.225 [0x7f7c523ee700] ERROR - Error issuing curl_easy_perform(handle): 28
7

I just did last night for 3 times before considering making this thread.

I did again just now just for you. Sama symptoms. Server settings page is still inaccessible while on Vpn on local IP access.
Here’s updated logs and journals for proof.

But when Vpn is off no more error. The fact that I can browse and playback within my home network shows that plex core framework somehow fails only when using Vpn…

Also, if it is because of slow DB QUERIES why then the error and the symptoms are gone by turning off VPN. somehow it doesn’t make sense…

8

If you cannot access the server when the VPN is enabled, clearly the VPN config is wrong.

The most common VPN configuration error is when it creates the TUN adapter and forces ALL traffic through it. It cannot do this. It must allow your Local LAN (255.255.255.0 netmask) and not be all encompasing (0.0.0.0 netmask)

As example, here is my VPN to the lab at Plex.

[chuck@lizum ~.66]$ netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         dsl             0.0.0.0         UG        0 0          0 enp14s0
10.0.0.0        10.0.20.1       255.255.240.0   UG        0 0          0 tun0
10.0.20.0       0.0.0.0         255.255.255.0   U         0 0          0 tun0
69-95-210-113-s dsl             255.255.255.255 UGH       0 0          0 enp14s0
192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 enp14s0
dsl             0.0.0.0         255.255.255.255 UH        0 0          0 enp14s0

Notice tun0 is only applicable to that subnet. Also notice (most imporant) 192.168.0.0 still goes to the LAN adapter.

10

The server won’t let you access Settings when:

  1. Not signed in to the same account your Plex/web browser is signed in to.
    or
  2. The server is not yet claimed to your account AND your PC and the server are not on the same RFC1918 network.

Once it is claimed, you can access it from any WAN IP address, VPN or not.

12

I am sorry but I will have to let you to resolve this one yourself.
Given PMS works without it but fails when the VPN is enabled, that’s clear.
I thought I could help but we don’t support configuring VPNs so this is where i must stop.

It’s also 3am Sunday morning for me.

Hope you understand.

13

Thanks. No worries. Obviously it would help if you can share the setup to make sure “” tun0 is only applicable to that subnet. Also notice (most imporant) 192.168.0.0 still goes to the LAN adapter.""

In my opinion my netstat -r looks exactly like yours.

This is also my lab server. My nvidia shield tv server works perfectly

14

What you see from me is a stock OpenVPN configuration. No rocket science there. (Gnome NetworkManager)

15

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.