Nope, I did not. Like I said above, I deleted the package (but on DSM 7, not DSM 6).
Well, this time the migration is supposed to have been done. I got the confirmation pop-up…
Everything is now working perfectly fine. Plex is now running with all my libraries like it was running on DSM 6. BUT… I’m just surprised that all the data stayed in the \Plex\ folder. It never migrated/moved to \PlexMediaServer\ . Only the \Library\ folder has been removed from \Plex\ .
I’m now not in the case of a fresh install any more. If I delete the package again asking to delete all the data as well, I’m concerned this time it’s the master data in \Plex\ that will be deleted.
Here is the migration log:
Plex Media Server migration to DSM 7 started: Tue Sep 28 23:46:31 CEST 2021
=== Tue Sep 28 23:46:31 CEST 2021 === Start: Change ownership
=== Tue Sep 28 23:46:32 CEST 2021 === Completed: Change ownership
=== Tue Sep 28 23:46:32 CEST 2021 === Start: Convert symbolic links
=== Tue Sep 28 23:46:32 CEST 2021 === Completed: Convert symbolic links
=== Tue Sep 28 23:46:32 CEST 2021 === Start: Migrate Plex Media Server
=== Tue Sep 28 23:46:39 CEST 2021 === Completed: Migrate Plex Media Server
=== Tue Sep 28 23:46:39 CEST 2021 === Completed: Migrate Plex Media Server
=== Tue Sep 28 23:46:39 CEST 2021 === Start: Clean /volume1/Plex
=== Tue Sep 28 23:46:39 CEST 2021 === Completed: Clean /volume1/Plex
Also, any answer regarding the Kaspersky warnings? I keep on receiving some more.
But I have a doubt, I don’t know if it’s not coming from the website plex.tv and not the Plex app on the NAS as when I got the last one, I could not save my answer in this thread until I accepted to continue the SSL connection.
Look, under DSM 6 the file structure was the following…
So 1 shared folder (\Plex) and server software & data (media) were in the same shared folder.
Since the upgrade/migration, the file structure is the following…
There’s now 2 shared folders. The \Plex\ shared folder is still there but a new \PlexMediaServer\ shared folder has been created with the new version of the Plex server inside and all the data (media files) has been left in the \Plex\ shared folder.
At this point my comments were just:
1/ My Plex is now running fine but the data has not been moved from the old Plex shared folder. Is it normal ? I thought they were supposed to be transferred and we could even delete the old \Plex\ folder?
I’m just surprised that all the data stayed in the \Plex\ folder. It never migrated/moved to \PlexMediaServer\ . Only the \Library\ folder has been removed from \Plex\ .
So after reading “DSM 7 - Packaging 2.0 (PMS 1.24.2.4973) - Release information” I understand I probable misunderstood something in the information topic regarding the migration as “no”, media files must not be transferred into the new \PlexMediaServer\ shared folder. So it’s normal that the migration process left them where they were under DSM 6.
Moving your media would break everything Plex knows about the media so it makes perfect sense to leave it in the “Plex” share .
This is the reason we abandoned it. There are so many “YouTube expert videos” who disregard the warning files and everybody follows them so I moved Plex itself.
In the future, if DSM 7 changes, and the app permissions get restructured, any media in the wrong place might be lost forever.
This is another reason why I warn so loudly as to not place media files in Plex’s operation area
Hello. I am using plex with DSM 7 since early release days. That time recommended way was to use “beta” package from DSMPackageManager(build 3744). there was some flaws, but all of them were solved. And in this days I read new information on this forum that this beta is deprecated and I need to install latest version from website.
So I did what was recommended. (I’ve used forum thread where were described how to update plex on DSM7). But after update i could not log to plex with direct link and server disappeared from account(offline). If I manually delete “latest” versions and install package from DSMPackageManager. So it works on beta(3744). And it does not on 5033. In package manager it says it started (Package [Plex Media Server] has been successfully updated., System successfully started [Plex Media Server].)
Could you please guide me to where I can find correct way to update from beta to latest release (PlexMediaServer-1.24.3.5033-757abe6b4-x86_64_DSM7)?
Thank you.
PS. in Plex media server log I have found this lines in case it could help:
Sep 28, 2021 19:27:51.051 [0x7fa92cc0cb38] INFO - Plex Media Server v1.24.3.5033-757abe6b4 - Synology DS920+ x86_64 - build: linux-x86_64 synology-dsm7
Sep 28, 2021 19:27:51.052 [0x7fa92cc0cb38] INFO - Linux version: DSM 7.0.41890-0, language: en-US
…
Sep 28, 2021 19:27:51.380 [0x7fa9302a9258] ERROR - [CERT] PKCS12_parse failed: error:23076071:PKCS12 routines:PKCS12_parse:mac verify failure
S
Sep 28, 2021 19:27:51.380 [0x7fa9302a9258] ERROR - [CERT] Found a certificate, but couldn’t install it.
Sep 28, 2021 19:27:51.380 [0x7fa9302a9258] DEBUG - MyPlex: mapping state set to ‘Unknown’.
…
and it somehow connected to Plex-Issued Server Certificate Error
Good evening. Just bought the DS220j and having trouble getting it up and running.
I have the 1.4GHz 4 CPU core version of the DS220j.
I have installed DSN 7.0-41890.
I can see the drive on my network fine and run a media file I manually placed on it - connection works.
I downloaded the Plex Media Server for Synology (DSM 7). file x86_64 etc.
In package center, I tried manually installing the 64-bit file but got an error message about an incompatible version. “This Package is not supported on the platform of Synology NAS or is incompatible with the Current DSM version”.
I see other threads here saying to make sure to use the 64 bit version on my model hence i throw myself at the mercy of the very knowledgeable Forum people!
Thanks. Progress. Have installed and ‘claimed’ by server, but now I get the 400 Bad Request error. That’s what I originally got on the Beta which led me to the forums to start with and I read to do the install from plex.
Nowadays it’s pretty strange not to use one. My SSL is set automatically by DSM and I have option to auto redirect every http to https. I use Lets Encrypt for SSL. Do i need to reissue one? And main question is why I do have a problem with 5033 and do not have with 3744.
add. So I disable http/2 and server reply as nginx. Now it allow me to load http (no ssl is definitely bad). And i got redirect to setup page. Why do I need any setup if I have all working.
How to migrate from this beta to 5033 without losing any data? Now I will roll back to 3744 to have server running without problems.
Steps.
Fresh reboot.
In explorer, I can see my network including the NAS. I can play a video over the network.
I check Plex media server is running. I click Open.
Website opens: http://[servername].sg3.quickconnect.to:32400/web
Hmmm… can’t reach this page [servername].sg3.quickconnect.to took too long to respond
If I go to file server, I can see the drive. I can download files. Attached are the logs.Logs (1).zip (90.2 KB)
I have Plex running on a NUC (Ubuntu). My media is on the NAS, and after upgrading to DSM7, Plex is saying 'Please check the file exists and the necessary drive is mounted.