Same problem here, on an 1815+. Simply installing PlexMediaServer-1.13.4.5251-2e6e8f841-x86_64.spk over the top of PlexMediaServer-1.13.4.5251-2e6e8f841-x86.spk fixed it right up, no apparent settings or data lost.
2 Likes
People always said why didnāt you allow automatic updates for Plex on YouTube when I had a video for how to update Plex.
I havenāt updated to the next version still on the older version. I have a Plex pass and I am using Ubuntu server.
After using Ubuntu web server I knew automatic updates was something you just donāt do. And I had a problem with Plex in the past update so I leaned to hold off to update
thanks thatās works for me !
1 Like
Thanks its working perfectly 
Can the 32bit version (from the store) be updated long term though? This situation happening royally screwed me over. Not only because of Plex, but the update did a few other things that caused networking problems.
Ideally, Iād like to limit the number of packages I have to install manually from the package center. Mostly because I want to be able to update the programs without having to manually do it each time. On the other hand, if Plex was willing to create Synology update packages as their core app is updated, Iād be fine with manually updating. Iād like to stay more current than Synology allows. But, if Iām forced to stay around the same version, Iād rather updates be automatic as much as possible.
For now, I reset my synology, which put it back to 6.2 without the updates. I think Iāll wait on upgrading til a new version of plex is there, or a new update from synology - one of the two teams fixing the issue.
To all:
Weāre deep in DSM right now determining the EXACT change which occurred.
Iām chatting with my colleague whoās testing our hypothesis on a lab rat DiskStation as I write this. 
If this holds true, weāre going to hotfix PMS right away and then get the backside with Synology sorted out as well.
1 Like
I am having the same issue and I think itās a Plex Vs Synology update war so best wait till they repair it or roll back your synology. Maybe a Plex admin could comment on the issue?
My NAS automaticly installed DSM 6.2-23739 Update 2 overnight.
I saw the above mentioned fix by installing the x64 bit version. Before I installed that, I was browsing my NAS, in SSH, I found out the āINFOā file had some interesting information under āarchā. It mentioned that the installed version was x86 (32) bit, and then it had some other information, my quess is that it is processor code names.
I made a copy of the file before I installed the x64 bit version:
/var/packages/Plex Media Server
sudo cp INFO INFO.old
I would then have compared the information in the āINFOā file after Iāve installed. It did change. What I did not know then, wat that the whole folder is deleted and recreated when installing/updating/upgrading. So unfortunately I cannot post the old value in the āarchā line.
I am 100% sure Iāve installed the x64 bit version. I update when the web app notify me of available updates. If I somehow have installed a x86 (32) bit, it must have linked me to the wrong one. Otherwise the DSM update must have made a change to the āINFOā file mentioned above, where it altered the āarchā line. Which made the NAS run the Plex package as a x86 (32) bit, when it actually was a x64 bit package.
However, as the others, I can confirm that installing the x64 bit version solves the issue.
TO ALL.
Iām changing the packaging now. Weāre pushing for for a hotfix now wish distributes the new binary packages to everyone (including Synology)
1 Like
Yesterday evening (17/7) my plex conection with my Synology NAS server just worked and today (18/7) it wonāt work anymore.
The server āRS-Serverā is unreachable. Make sure itās running, double check your network, and try again.
At the package center of my NAS the Plex Media Server says (uitvoeren ā¦
to carry out) . Click i on it to let it work it says after a short whileā¦ (Kon de pakket service niet uitvoeren ā¦ Could not perform the package service).
Last night there was an automatic DSM update and since that update it wonāt work.
I send the support center a message this evening about the problem but not yet a reaction.
Install the 64 bit version of PMS from plex.tv/downloads.
(uninstall the existing PMS packageā¦ your library is safe because I donāt delete it at uninstall)
1 Like
Great i tried the 64bit version and it works again.
An āupdate warā ? isnāt that bit harsh?
Weāve spent the day doing full root cause analysis of the changes introduced by DSM 6.2 Update 2, which we did not have advance notification of but thatās on us to address, and have resolved all the issues.
Yes there are a few outstanding action items but at this point all the technical issues are resolved.
Iāve made changes to how PMS is packaged to prevent this from happening in the future and to be compliant with DSM 6.2 U 2.
To everyone:
- The only 32 bit machines remaining are DS415play and DS214play. These two machines need and will get the 32 bit PMS version.
- All other Synology machines are 64 bit and will get the 64 bit PMS version.
1 Like
OK āUpdate conflictsā. Plex and Synology had updates within 24hr. My issue turned out to be Plex linked me to the 32bit version download and not the 64bit version(I think). I reloaded the 64bit version and Plex is working.
Just updated Synology DS1515+ to DSM 6.2-23739 Update 2 (successfully) and am getting the same āFailed to run the packageā error message when trying to Run Plex. Stopped Plex before installing the update. Any ideas?
Download the 64 bit version from Plex.tv
What everyone is getting from Package Center is the 32 bit version.
Thatās what Iām trying to get resolved now with Synology. WHY are they pushing the 32 bit to a 64 bit computer. I suspect itās a miscommunication but I am working on that.
Confirmed that 64bit version works for my DS1815+ā¦thanks!
Since there are just two Synology NAS left that are 32 bitā¦it seems like the reasonable thing to do would be to force the 64 bit version via the Package Centerā¦if they can only do one or the other version. Determining what is correct version for the machine that is running DSM would be bestā¦obviously.
Such a decision is for Management and Synology to determine.
Weāve made changes which appear to mitigate that from happening again.
The hotfix is rolling out now. When complete, only evansport processors may install the 32 bit package.
Attempting to install the 32 bit package on a 64 bit system will return the not compatible error.
Weāre also reaching to Synology to get this out to them ASAP and make certain Package Center implements 32/64 bit selection properly on their end.
sounds like what you have done will cover the differancesā¦regardlessā¦well done.
