I should have clarified; Plex shows as installed under “Installed” but does not appear under Synology’s “All Packages”.
I understood you.
It shows up for me.
This means something is amiss.
- Your diskstation can’t connect to the Syno Package Center server
-or- - The Package Center internal mechanism is damaged (corrupted) somehow.
Both of those warrant getting their assistance. (I can hammer my way through it but you’d want finesse)
Okay; weird!
I’ll get on to Synology.
In case anyone else experiences this, I thought I’d report back. DSM 7.0 was not auto-updating correctly so I needed to install a couple of manual updates before being able to update Plex.
I have not updated to DSM 7.1 until we get the okay on Plex compatibility. The new Discover and Watchlist features are fantastic.
Update to 7.1.
Stop Plex first just to be safe.
OK. revisiting this thread only now as all the updates were going to spam… Oops
To confirm, this is the DSM version I’m on
This is the version of Plex I’ve been running for ages now (despite repeated attempts to update each time a new package is announced).
This is the server upgrade announcement I get when I go to the web interface.
This is the file I downloaded
With the Plex server stopped this is what happens when I attempt a manual install of the downloaded file.
This behaviour’s been like this for the last (at least) three server updates and prior to that, I was able to manually update without any issue.
Ralph
I was hoping someone would suggest a genius solution to this conundrum… No one got any ideas for a workaround?
Have you tried to download using incognito mode then install while in that incognito window?
DSM will only complain if there is corruption somewhere.
I’m sorry, do you have a question? I’m not following.
Are you asking about the upgrade process?
If your concern is it not responding, It’s not possible to know the cause without logs
Apologies if I wasn’t clear. The question is, I guess, how do I successfully get DSM7 running on a Synology DS214play to accept server updates for Plex?
If you look at my initial and subsequent posts on this thread you’ll see that I’ve diligently attempted manual updates as and when they became available.
Those updates used to install with no issues. However, now they just fail every time and I have no idea what may have changed (if anything) to cause this update process to falter?
I am wondering if the most straightforward course of action would be to just uninstall Plex and reinstall from scratch? Or should I just ignore the updates until the Plex server breaks… it is, after all, still running. I’m not even sure what benefits I’d get from the subsequent updates I haven’t been able to implement…
Cheers
Ralph
Thanks, Chuck. Just curious if this combination is stable. Watching this thread for confirmation is all.
I’ve not changed the packaging since 1.24.2 when DSM 7.0 became final release and I was able to finally add the “PlexMediaServer” shared folder for us.
If you’re comfortable with the command line, attempting to install the package and then examining /var/log/synopkg.log will tell us what’s happening.
If you’re not comfortable with mucking around the shell as root, it’s easy to have a scheduled task cat out the file and email it to you. (your preference)
If we can see that log, we’ll get a better idea what it’s not liking.
DSM 6 will be supported until either:
- Syno drops DSM 6 support
- DSM 8 is released (not likely anytime soon).
If you’re happy where you’re at, Stay There 
My DS1815+ is , and will remain, on DSM 6 until I retire it.
How do I schedule the task you’re suggesting?
Or just walk me through how I can open the command line and change to the relevant folder to send you the log… Happy to give it a go
cheers
R
After a few minutes, you should receive an e-mail with the contents of synopkg.log in the message body (it took 7 - 8 minutes on my DS918+).
Save the information to a text file and post it to the thread.
Hello,
I was in the same case as many people and in the same DSM and Plex version.
The problem does not come from Plax but from the DSM 7.0.-41882 version.
I did a manual update of the DSM to 7.0-42218 and the installation went well.
In fact, version 41882 does not handle the “certificate” problem and displays the message “invalid file format”.
Version 42218 reports that the package is not certified but accepts the installation.
I hope this information will solve your problem and help many others.
Sorry for my English, I’m French.
