Plex won't update on Synology NAS 1520+

Server Version#: 1.18
Player Version#: N/A

I have a Synology 1520+ NAS. I am using Plex on it (version 1.18). I am trying to update Plex to the latest (1.21). I supply the file and all I get is a “Please wait…”. I waited for an hour for this to work. Didn’t work. Nothing was updated. I have tried:

  • Restarting the NAS, then update
  • Stopped Plex, then update
  • I have used Firefox instead of Chrome to download and update
  • I have uninstalled plex, reinstalled (via synology package manager), then update
  • I have uninstalled plex, and then manually installed plex via the manual update in the package manager
    Nothing seems to work. Does anybody have an idea as to what the issue is?

When you attempt to update the package,

  1. Is Plex running at the time?
  2. Are there any other ‘CPU heavy’ apps running?
  3. What does DSM report ? (does it get stuck in the installer?)
  4. If you manually open the Plex share in file station, navigate down into Library until you see the Logs directory, can you right click Logs and Compress to Logs.zip then attach that ZIP file here?

No, there are no other graphics heavy apps running at the time of the update attempt. Yes it get “stuck” at the following screen


See the attached logsLogs.zip (2.6 MB)
I really appreciate your help with this.

Thank you.

I found it.

Jan 23, 2021 22:27:42.848 [0x7fd104855700] DEBUG - Skipping over directory 'Library/Application Support/Plex Media Server/Plug-in Support/Caches/com.plexapp.agents.localmedia/HTTP.system/db', as nothing has changed; removing 0 media items from map.
Jan 23, 2021 22:27:42.848 [0x7fd104855700] DEBUG - Activity: updated activity 0f243a8a-2474-4a6c-b916-11d3a8c43859 - completed 94.4% - Scanning Music
Jan 23, 2021 22:27:42.848 [0x7fd104855700] DEBUG - Scanner: Processing directory /volume1/Plex/Library/Application Support/Plex Media Server/Plug-in Support/Caches/com.plexapp.agents.localmedia/HTTP.system/ea (parent: yes)
Jan 23, 2021 22:27:42.848 [0x7fd104855700] DEBUG - Skipping over directory 'Library/Application Support/Plex Media Server/Plug-in Support/Caches/com.plexapp.agents.localmedia/HTTP.system/ea', as nothing has changed; removing 0 media items from map.
Jan 23, 2021 22:27:42.848 [0x7fd104855700] DEBUG - Activity: updated activity 0f243a8a-2474-4a6c-b916-11d3a8c43859 - completed 94.4% - Scanning Music
  1. You placed media in the Plex share. — ignoring the warnings.
  2. You then incorrectly told PMS what to scan (probably /volume1/Plex/Library ?
  3. You’ve created an infinite loop (which happens in every case)

The solution here.

  1. Stop Plex
  2. Uninstall the package
  3. Move your media out of the Plex share into new shared folders of your making.
  4. Delete the Plex share
  5. Reinstall the package.

Please read through this Guide on how to setup PMS on Synology.

I followed your directions. After I uninstalled Plex, I moved my media out of the plex folder into a different one. NOTE: I removed everything out of the Plex directory, but I couldn’t delete it at all. I reinstalled Plex. I then tried to updated it. Still stuck at the “Processing” screen. See the attached logsLogs.zip (86.7 KB)
See the logs attached.

To remove the Plex share:

As the administrative user:

Control Panel - Shared Folders - highlight the Plex share - DELETE - enter password.

Now install Plex again.

Got it deleted. Reinstalled plex. Tried to upgrade, same problem - Stuck on “Processing” screen.

What happened (what did you do) between installing and starting the first time and upgrading the package?

I ask because:

  • If you downloaded directly from Plex.tv, you’d be at the current version.
  • If you downloaded from Synology then upgraded to the version at Plex.tv, the following things would happen:
  1. PMS would be stopped
  2. The executable code removed by DSM
  3. The new version’s executable code installed by DSM
  4. DSM calls my ‘postinstallation’ routine which does:
    a. Checks username Plex exists & makes sure it is not login-capable
    b. Checks the ownership of /volume*/Plex/Library. If not ‘plex’, it forced ownership of everything it finds – suspending installation until complete.
  5. Start PMS which upgrades the database if needed (usually very minor)

This being the sequence of events, What transpired between initial installation and upgrade?

This is the sequence of events that I do:

  1. Stop PMS through Package Center
  2. From the Package Center, click Manual Install
  3. Select the package from my Downloads directory
  4. Click the Next button
    That is when I get the “Processing” screen

Do you ever see this display?

The screenshot won’t display for some reason. My browser says that image could not be loaded.

it’s ok if you can’t upload a screenshot for now (new account).

Do you see that displayed by DSM ?

If you do, it confirms the package you uploaded is valid and it’s ready to install.

I finally got it to display. No, I have never seen that screen before

If you’re having that much trouble getting that far –

  1. The connection between your Synology and computer is having a lot of problems.
  2. It’s kinda up to you to figure out why. We can offer advice if we know how you set it up but … I think you know what I’m saying?

Hmmm…I have been having issues with Plex staying for more than 5 minutes. I read that the fix was to upgrade. So that has been my concern. Here is my setup:

The NAS has 4 Ethernet ports on it. I am using 2: 1 for my LAN and one that is tied to my Entertainment network using a VLAN (I have no problem with the Synology Video Station with this setup). Could this setup have something to do with my issues? FYI, I am trying to update via the LAN connection

First, PMS doesn’t like (in the initial steps) multiple LAN connections. This is because of it’s RFC-1918 subnet requirement for the home LAN.

It will always go to the first (eth0) adapter. If eth0 isn’t your default making certain you have eth1 set as the default gateway to the internet. This is because authentication for all players / clients if via Plex.tv (cloud based). Think of how apple does things. Plex uses a very similar technique.

Plex doesn’t care about VLANs (Layer 2). It does care about subnets (Layer 3).

Regarding basic installation, DSM is very lax in a lot of ways. It’s also “host centric”.
This is why I’m puzzled that you’re having trouble getting PMS to upgrade from your LAN. That entire process is DSM-centric.

You only are Plex-centric when you open http://ip.addr.of.syno:32400/web (the Plex/web client endpoint)

In my LAN, I have everything as two subnets. I use VLAN tagging for those things I don’t want to see my equipment / PMS. Everything else is on the main subnet (192.168.0.x ). The other LAN (VLAN tag 1002) is for the tablets & phones (aka. guest wifi) and only have internet access.

Make sense so far?

One thing you will find with Plex, the more invisible your switching is, the better it will like it.

e.g.

  1. NAS has a sub mask of /23 and can service two subnets from that one port (single or bonded).
  2. One ‘cluster’ of devices are on the 192.168.0.x subnet
  3. The other ‘cluster’ is on the 192.168.1.x subnet.

See what I’m saying?

What are some of the ip addresses and netmasks you are using?
(I hope to understand the topology a bit better)

LAN 10.20.0.0/22 (Another device and only that device is on 10.20.3.1)
Other networks:
VLAN 1: 10.20.20.0/24 (Personal Wireless)
VLAN 2: 10.20.25.0/24 (Entertainment Wireless)
VLAN 3: 10.20.30.0/24 (Guest/visitors)

Oh, one thing I probably should have mentioned is that I am downloading the 64bit, x86_64 version of plex for synology. I am running DSM 6.2. I shouldn’t need the 32 bit version, correct?

Running 64 bit is the best. You miss out on hardware transcoding without it.

I am a bit at odds with your subneting.

Where does the Syno sit and what is its subnet mask?

Here is from the Network section of DSM