Issue with version numbering on PR4100

[John_Y128]

Besides WDC it’s, Feb 12 and still being offered under ‘Downloads’ is;
Plex Media Server for Windows
1.14.1.5488-cc260c476
December 14, 2018

[edbrown]

For those that have alerting setup on the PR2100 or PR4100 this issue can be quite obnoxious.
Everyday getting the alert that there is an incredibly old version of Plex that is ready to download.

There does not seem to be any meaningful concern except for the occasional post meant only only to pacify anyone actually needing a fix.

How many people have downgraded their Plex to a very buggy version due to this ignored error?
This issue will not be going away anytime soon.

[NAS-PR4100]

The problem and still available even with the latest version Beta 1.15.1.7xx

[corwin_x]

@chrisallen 3 version updates and 2 months later, this is still not fixed… Srsly, either change the version number format back or start kicking WD (yes I know they are bunch of lazy monkeys, but still). I am getting tired of getting update notifications every day. You broke it with version number format change, so would you please fix your sh*t?

[John_Y128]

Evidently WDC could care less, I taken to ignoring the issue.

[et_tu_Brute]

The sa mne crap has just happe n ed to me last Wednesday. To add salt to the wound, Plex now says this device is offline, yet everything else can still access it (kodi, spmc, vlc, archos, mx player etc). My other WD NAS I use just as a music and image server is iperating fine. Hard ro believe that they still can’t resolve this lobg outstanding issue.

[corwin_x]

@tobiashieta @chrisallen ETA on the fix please?

[chrisallen]

I have reached out to Western Digital for an update on the changes needed to be made on their side. When I have something to share i’ll let you know

[corwin_x]

@chrisallen Okay, so seeing how long it takes, I have decided to investigate myself. And found the cause in an hour, most of the time trying to find how to unpack that goddamn bin file. Are you guys serious that you are not able to change one line in apkg.rc in 2 months? just replace Version: 1.15.3.858 with Version: 11538580 and rebuild the package.
There. Issue fixed.
For whoever gets plagued by this, here is the link to my gdrive to download fixed package:
https://drive.google.com/open?id=1V3mGBxwzamJ9_dABT01Rhi56NjSzKWKP

For PR4100 only, Plex should rebuild it for other units, I am not doing any more of their work.

[chrisallen]

The change from a single monolithic version number 11538580 to the correct version style as per the WD SDK is intentional. the issue is that the version in their app store is still 1.7.2 which uses a the monolithic version string. We have given WD builds of PMS 1.14.1 that have the correct version style and there QA team are working on approving them and having them in their AppStore.

We will not be going back to a monolithic version string.

[corwin_x]

I get it, but for the time being, the point should be fixing the numbering so people does not accidentally downgrade (and we get rid of the notification). Then you can haggle with WD for how long you want.

[corwin_x]

…or do nothing. Who cares about the paying customers anyway, right? Instead doing the quick hotfix, let the user fight problem you have created.
Guys in this thread seem to be enjoying this approach: Western Digital MyCloud Pro PR2100 Plex update Loop
@chrisallen, this illustrates quite nicely what I hate on Plex. You create problem that can be fixed in 20 seconds, but instead of doing so, you go full ■■■■■■ headbutting WD QA for more than 2 months and no light at the end of the tunnel. Users are stuck in the middle and no one cares.

[danieletorelli]

@corwin_x could you please explain how did you unpack and repack the .bin file? I’m going to apply this workaround myself too since I had to temporarily disable my NAS notifications because of this.

[corwin_x]

It is ugly but working - For the BIN, use 7zip - looks like gzip compression, but I was not able to unpack it with anything else. Inside is a standard tar, this needs to be unpacked on WD device - for some reasons I run into some failures unpacking it on debian and ubuntu, too lazy to investigate why. Then you edit that one line and use WD packager from SDK to repack to BIN file, again on WD NAS - more info here, registration required:
https://developer.westerndigital.com/develop/wd/sdk.html

[danieletorelli]

Thanks!

@chrisallen do you have any update on the fix?

[corwin_x]

@chrisallen, @elan. Seriously. Either give some reasonable estimate on the fix, or admit that you screwed this one, go back to monolithic versioning as you call it and work it out with WD in the background, then change it back once done.
Below are threads with people complaining about this issue, only what I was able to find with a quick search.
Funny enough, all these posts have one thing in common - not a single reply from plex staff, not even acknowledging the problem.

Update issue on NAS WD PR4100 with Plex Media Server 1.15.3.858

Hi. I use Plex Media Server on my NAS WD PR4100 with last firmware: 2.31.174 I’ve installed the latest version of Plex Media Server : 1.15.3.858 In the NAS menu, Plex Media Server reports that it needs to be updated at version 1.7.2.3878 – May 26, 2017 It is clear that there is an error… I also tried reinstalling Plex Media Server but nothing changed How can I solve the problem? Best regards, Max

Plex not updating

Server Version#: Player Version#: When I log into Plex on my PR4100, it tells me there is an update. I manually install the update (1.15.4.993) and the pop up says it has installed successfully. I reboot Plex and I get the yellow bar across the top stating that there is a new update which is 1.15.4.993. I can now no longer watch 4k media and my collections no longer exist. Any help would be appreciated

Updated to PMS 1.15.3.876 on WD PR4100

but Plex is still stating that there is. server update to 1.15.3.876 I have update manually as well as through the server. If I “skip the version” then all my collections are out of whack. Any idea what is causing this?

Incorrect 'update available' message on MyCloud PR2100

Server Version#: 1.15.3.876 Player Version#: 3.83.1 The NAS is prompting for an update to server version 1.7.2.3878 (dated May 26, 2017). Following events are generated on your MyCloudPR2100 MediaServer. Event title:App Update Available Event description:plexmediaserver app has update available. Please update. Severity:warning Event code:1501 Event time:04-18-2019 04:00:04 AM Firmware version: 2.31.174 This email prompt to update has only recently started to occur, and i normally updat…

Plex Updates Keep Changing Version on WD PR4100 (now at 1723878)

Server Version#: 1723878 Player Version#: As you can see from the above server version it is far in advance of the apparently correct version, which should be 154919? Earlier this week the correct version from Plex Downloads was showing as ending 876. The 1723878 has installed correctly, but Collections is missing except by Collection name/filter. I am thoroughly confused as to how I have managed to get a ‘17*’ version. Any help appreciated Simon

Western Digital MyCloud Pro PR2100 Plex update Loop

Server Version#: Version 1.15.2.793 Player Version#: N/A When checking from the Plex interface it shows that my version is up to date. The NAS interface alerts me that there is an update available. If I update from NAS, then the Plex interface it out of date. This keeps bring me in circles when updating.

WD My Cloud PR2100 "App Update Available" alerts

I am successfully using a WDC PR2100 as my Plex Media Server and houser of all my media. I have been manually updating the PMS system as upgrades are released and am now up to current (1.15.0.659). Firmware on My Cloud is most recent (2.31.149). Just a few days ago I started receiving alerts from my My Cloud device that “An update is available for the following apps: Plex Media Server”. These alerts come once a day, sometimes more often. Problem is, when I dig down, the WDC device wants to “up…

New Plex server update issue!

https://support.wdc.com/download/notes/apps/plexmediaserver_releasenote_1_7_2_3878.html [plex] i got MyCloudEx2Ultra install plex server work great with it , untill few days with the new update (usually i download the update from my plex server , this time its tell me to update it from MyCloud , attach picture) , when i try to run a movie it say “this server isnt powerful enough” , so when i install again (PlexMediaServer-1.15.2.793-782228f99-MyCloudEX2Ultra.bin) its works great , but all the t…

[chrisallen]

Hi @corwin_x

Firstly, my apologies for not providing an update on this issue sooner. I have been head down on some other issues and tasks (not that I am excusing the lack of communication)

We are pushing WD to provide a date when they will have PMS 1.15.0 or newer in their AppStore for all current (PR2100 etc) and EOL (WD My Cloud Mirror etc) so that their old, 1.17.2 update no longer gets offered to users due to it using the wrong “monolitic” version string.

If we were to go back to a monolithic version string, we would need to pad it out so that it would still be higher than the build they offer. See the following example.

When we switched to our new CI, we started over with build numbers. This means that due to a 3 digit build number, are actually a lower version number that what WD offer.

• PMS 1.7.2.3878 = WD Version: 1723878
• PMS 1.15.0.647 = WD Version: 1150647

1150647 < 1723878 which would mean you would still be offered 1.7.2.3878 in their NAS App Store as an update.

Now I know we could just wait will we get to 4 digit build numbers and then go back to monolithic version numbers, and that might be fine for now, but that may become an issue down the road if our version numbering scheme changes, or there is another factor we haven’t thought of.

I understand the current situation is an annoying and less than ideal one, but we needed to solve this issue and move to real version numbers at some point, so we chose the move to the or new CI and build/packaging system to do it.

It is unfortunate that getting things resolved on WD’s side has taken this long, but please be patient a bit longer. We have reached out today to push for an update and dates on when this will be resolved.

[MyronS]

Whatever has happened, the issue seems to have been fixed. My NAS is no longer insisting that I upgrade to the WD app store’s lower revision of PLEX.

[chrisallen]

WD Updated PMS in their AppStore to version 1.15.3 and moved to the correct version number. This should have resolved the update notifications always being displayed when running a PMS version of 1.15.0 or newer.