Can't install latest update PlexMediaServer-1.23.3.4707-ebb5fe9f3-x86_64_DSM6 or DSM7 version

Server Version#: DSM 6.2.3-25426 Update 3 & DSM 7.0-41882
I don’t know if I’ve had a ‘brain fart’ or if there’s a problem with the latest releases for Synology DSM 6 & Synology DSM 7 (beta). Up until today, I’ve had no issues installing updates to my Xpenology production box (higher spec than DS3617xs) or my DS1513+ running DSM7.0-41882.
Tonight, both updates downloaded refuse to install with same error message: "Invalid file format. Please contact the package developer. "
Not sure if I’m doing something different that causes packages not to install. Other updates that have recently updated successfully are:
DSM 6.2.3 : PlexMediaServer-1.23.1.4602-280ab6053-x86_64_DSM6.spk
PlexMediaServer-1.22.3.4523-d0ce30438-x86_64_DSM6.spk
PlexMediaServer-1.22.0.4163-d8c4875dd-x86_64.spk
DSM 7.0: PlexMediaServer-1.23.1.4602-280ab6053-x86_64_DSM7.spk
PlexMediaServer-1.22.3.4523-d0ce30438-x86_64_DSM7.spk
I have just reinstalled the DSM 7.0 Beta Version 1.21.0.3744. But now, any attempt to update to the later updates (including PlexMediaServer-1.23.3.4707-ebb5fe9f3-x86_64_DSM7.spk) will not install, giving the error message mentioned above. Any advice on resolving would be much appreciated.

Rhubarb

Update: Just tried again with the PlexMediaServer-1.23.3.4707-ebb5fe9f3-x86_64_DSM6.spk Synology DSM 6.2.3-25426. This time it worked!
I also noted that this time I got the message about trusted publishers (I 'm sure it’s the first time tonight I got that message). Perhaps my DSM wouldn’t accept the package until it gave me the warning about trusted publishers?

Still can’t update to the DSM 7.0 Beta version. No ability to accept Plex as a trusted publisher!
Would welcome practical suggestions here!

DSM 6 packaging, except for minor scripting work, has not changed in 2 years.
DSM 7 packaging, thanks to DSM 7 constantly changing, is in flux.

DSM 7.0-41222 and DSM 7.0-41882 Release Candiates (Beta 1 and Beta 2) are supported by the current PlexPass build.

DSM 7 packages cannot be signed by Plex. Synology changed the rules. Only Synology is permitted to sign packages.

With DSM 6, you can eliminate the unknown publisher message by adding Plex’s package key to the Package Center.

https://support.plex.tv/articles/205165858-how-to-add-plex-s-package-signing-public-key-to-synology-nas-package-center/

Thanks ChuckPa. Yes; I understand that Synology is totally responsible for the constantly shifting ground that is making it so difficult for the Synology client base of Plex users; as well as Synology community developers and Plex.Inc.
Despite the fact that Synology’s DSM is supposedly open source; it appears that Synology are doing their level best to identify their products as ‘high-end’ IT industry architecture. Synology’s software development cycle is shrouded in secrecy. Synology is renowned for failing to honour the company’s responsibilities to release source code. Perhaps the growth in alternative NAS brands available, is indicative of Synology’s lack of concern for their consumer grade customer base.

Yes, thanks FordGuy61. But I can’t do this with the DSM 7.0-41882 (Beta) release of DSM. You can still add the Package Sources but there’s no longer provision to add the Plex Sign key.

From where I, as a developer, sit,

  1. Create artificial user class “System Internal User” by playing with UID numbering
  2. Remove ‘root’ access from all aspects of package installation & management where the package must request access to all system services it is going to need prior to software launch
  3. Break compatibility with existing DSM 6 resources such as the “Plex” shared folder and “Plex” user.

I think you get the idea but DSM 7 forced a complete redesign and rewrite of everything. To us, DSM 7 is a “new platform” and completely distinct from DSM 6 with exception of a few pathnames like “/volume1” and users’ shared folders.

DSM 7 “Release Candidate” does not represent “final form”. More changes are coming. This is why I, as principle Synology developer at Plex, consider it to be “Beta 2”.

If you wish to read it, here is the interview. (2018)

Thanks ChuckPa for all your assistance. Because my DSM 7.0 Beta system is not my main box, I’m happy to let its Plex remain at version 1.21.0.3744 until these issues are resolved.
My main system (DSM 6.2.3-25426 Update 3) is currently running Plex v 1.23.3.4707.

My DSM 7.0 PMS is now all updated and operational now as Version 1.23.4.4712
My DSM 7.0 box (DS1513+) is still on the current version DSM 7.0-41882 (not 41890-my box tells me to contact Synology support to resolve issue of updating 41882 to DSM 7.0-41890).

Yes. But, my DSM Control Panel tells me my system is at the current version.
I saw from Plex forum that latest .pat file was for DSM 7.0-41890. I have downloaded the correct .pat file for my DS1513+ from Synology Downloads and every time i tried to install the install would fail.
I’ve tried with PMS installed and uninstalled.
I decided, because of this, and because of the error msg received, that i’d place the matter with Synology support.

That’s fine thanks. This is only a test system, my main Plex server is an Xeon system running DSM 6.2.3-25426 Update 3

I’m quite content to sit and wait to sort this matter out with the assistance of Synology tech Support.

Hi trumpy81,
today I received response on my support ticket from Synology.
On logging into my DS1513+, I saw that it was also NOW showing the Red dot in the notifications area. Control Panel was now showing that an update to DSM 7.0-41890 is now available.

I then responded to the prompts to download; then install the update.

The update process then completed successfully. My DS1513+ now appears to be operating normally @ DSM 7.0-41890.

I then advised Synology Support that as my DS1513+ appears to be operating normally that they please mark this Support Ticket as completed.

Thanks :grinning:; was strange though - because I downloaded the same update several times and tried over , and over, again. Can only assume that the source itself was corrupt.
Anyway - all’s well that ends well :grinning_face_with_smiling_eyes:

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