Unable to install/update Plex

Plex Media Server NAS & Devices
1

NAS is a Synology DS1821+ DSM 7.2-64570 Update 1 firmware

I was running PlexMediaServer-1.32.5.7349-8f4248874-x86_64_DSM7 fine but it said there was an update and I’ve updated fine in the past. However - like someone who posted back in Sept 2021, all I get is it sitting there and “Processing. Please wait…” and that’s it.

I ignored it, waited for another version which apparently released 3 days ago, downloaded that and same thing happened. Uninstalled Plex, tried both of them, same thing happened.

Tried to install the version I was originally running - same thing happened.

Installed the “default” version that is part of the Synology options - which is 1.29.2.6364-7000 and it installed fine.

Tried to install a newer version again - same thing - just sits there “Processing” and doesn’t give me a dialog option.

Installed an update of another package - no issues.

I’m - no pun intended - perplexed by this as it’s been fine before but 7468, 7516 and now 7557 won’t install on the DS1821+

Even more peculiarly, my DS1416 - while it |S the ARM processor version - same DSM, has updated to 7557 without any issues.

So any ideas why the DS1821+ goes “nah yeah nah” and the DS416 is like “yeah mate no problems” ?

2

How long did you wait and how big is your database? There are a number of updates that get performed, that message says, hay Im working on the update of your database please wait.

I have heard reports of it taking several days to a week depending on the library size.

3

I’ve left it for hours - but when I installed from the Synology packages, it took seconds to give me a dialog box and that included the databases as I left the data when I uninstalled.

My database isn’t that huge and the DS1812 is way nippier than the DS416 which also only took a couple of seconds to show me the dialog box.

4

@ChuckPa thoughts?

5

Can you access the Plex Media Server?

If so, go to Settings → Troubleshooting, download the log files and post the zip file to the thread.

If you cannot access Plex server settings:

  1. Stop Plex Media Server
  2. In File Station, navigate to the Plex Data Folder.
  3. Right click on the Logs directory and choose “compress to Logs.zip.”
  4. Download the zip file and post it to the thread.
6

Logs.zip (2.9 MB)
Here ya go.

7

giphy

8

Thanks for the logs.

I did not see any glaring problems in the log files.

There were no database corruption messages. A corrupt database can interfere with upgrading/downgrading Plex Media Server.

There are two things to look at before trying to update Plex. Neither should interfere with updating Plex, but they are easy to change, so best to to take them off the table.

  1. Multiple network interfaces on the same subnet can confuse Plex and other applications.
    Temporarily disconnect one of the interfaces.
    Alternately, you could bond the interface, presenting a unified interface to the network.

  2. Check for DNS Rebinding Protection in your router. If enabled, disable it.
    Also, configure the NAS to use a public DNS server such as 1.1.1.1 (Cloudflare), 9.9.9.9 (Quad9), or 8.8.8.8/8.8.4.4 (Google).

  3. Uninstall Plex Media Server
    After the “are your sure” window, you will be presented with three options. Choose the first, Uninstall Only and keep all settings.

  4. Now download and install the current public release, 1.32.6.7557 (DSM 7, Intel/AMD 64-bit version).

If DSM refuses to install PMS or the installation does not complete, please note when it failed, take screenshots of any messages, etc. That will help when trying to troubleshoot the failure.

If the installation completes OK, try to access Plex Media Server using the IP address of the server (http://syno_ip_address:32400/web).

If you see the “503 maintenance” message, wait 5 - 10 minutes and try again. Plex is updating the database structure for the new version of PMS.

The web page does not auto-refresh, so close the browser window then try again.


DNS Rebinding

Plex is failing to lookup plex.direct names.

Sep 28, 2023 11:47:15.648 [0x7f3a2f49eb38] ERROR - [EventSourceClient/pubsub/139.162.215.242:443] getaddrinfo(192-168-0-6.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -2
Sep 28, 2023 11:47:15.648 [0x7f3a2f49eb38] DEBUG - [EventSourceClient/pubsub/139.162.215.242:443] Network: 192-168-0-6.abcdefghijklmnopqrstuvwxyz012345.plex.direct failed to resolve to 192.168.0.6 but instead yielded ""

Some routers have DNS rebinding protection enabled. If you can access your router and see such an option, disable it.

The alternative is to use a public DNS server.

See the DNS Rebinding section of How to Use Secure Server Connections for additional info.


Network Interfaces

You have two interfaces active on the same subnet. This can cause problems for Plex and other applications.

It would be best to bond the interfaces together, to present a single interface to the network.

To bond the interfaces, go to Synology Control Panel → Network → Network Interface.
The type of bond will depend on the capability of your switch (if it supports 802.3ad)

If you do not want to bond the interfaces, disconnect one of them, at least temporarily.

9

Literally had a HUGE response - but reconnected to the NAS and thought I’d try again (I’d watched something on it otherwise I’ve not touched it since this morning) and it updated.

I mean I feel a touch of an idiot but I’d literally removed it (as you suggested) and tried installing 4 different versions including the one that was working on it originally and nothing, rebooted it, nothing, put the old, DSM version on, working, tried to update, nothing. 9 hours later, I try again and does it instantly.

WTAF… Oh well. It’s working so that’s something, but I have no idea why as nothing has changed.

Ho hum.

10

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