Where is the "true" latest Plex Media Server for DSM identified?

NAS: Synology DS418play
NAS OS: DSM 7.1.1-42962 Update 8 (indicated latest version available)
Plex Media Server Version#: 1.40.4.8840-70008840 (installed & indicated newest online version)
macOS Player Version#: 1.108.1.307-dd5b87aa

Plex Player indicates a new Plex Media Server version 1.41.6.968 is available for my NAS.

Which is correct?

Which recommendation should I always follow?

TIA!

The latest version is always available at plex.tv.

The version in Synology Package Center is almost always out of date.

Thank you!

Is there any additional verification performed to assure compatibility on the NAS?

If you download the wrong version (ex: ARM vs Intel or DSM 6 vs 7), then it will not install or run.

Thank you!

I did download the variant appropriate to the processor and DSM version.

From your reply, it seems that there is no further validation performed to ensure compatibility and that the recommendation in DSM truly just lags.

Therefore, I shall update my Plex Media Server on my NAS to that identified from the website as you recommend.

Part of my motivation for this question are some issues (eg: media libraries no longer lists although the source media still exists, no longer able to access Plex from my phone or tablet or outside the house, etc). I thought there may have been an issue with Plex Media Server.

In the event the issues remain, I’ll raise more specific topics to attempt to resolve them.

Thank you again!

PS: Can you point me towards something that defines Plex system nomenclature and how the subsystems interact? (Eg: Plex Media Server (that I get), Plex and Plexamp clients, etc.) I’m wrestling with re-designing my system and referring to things as “…that Plex thingy that does this function…” is embarrassing… :slight_smile:

Thanks again!

Plex makes all updates available to Synology. The version available in Synology Package Center lags because Synology refuses to update it to the current version.

As far as validation goes, Plex does that when they create the packages (spk files).

There is Plex Media Server and the various Plex clients.

Plex Media Server performs functions such as scanning media files, downloading metadata, streaming media to the clients, transcoding when needed, etc.

The Plex clients play the media files streamed to them by Plex Media Server.

To what other Plex Thingies are you referring?

Plex (the company) runs some backend services such as server registration (claiming), sourcing metadata and feeding it to your server, remote access registration, etc. But other than account management functions you never directly interact with those systems.

Plex makes all updates available to Synology. The version available in Synology Package Center lags because Synology refuses to update it to the current version.

Understood.

As far as validation goes, Plex does that when they create the packages (spk files).

Understood. The packages on the Plex site are the canonical trusted variants. I’ve used the latest there to update my Plex Media Server. Tx!

There is Plex Media Server and the various Plex clients.

Plex Media Server performs functions such as scanning media files, downloading metadata, streaming media to the clients, transcoding when needed, etc.
The Plex clients play the media files streamed to them by Plex Media Server.
To what other Plex Thingies are you referring?

My notional system design is as follows:

  • Media repositories (ie: directories somewhere on the network);
  • Plex Media Server that performs the functions you list but also have a variable number of subsystems known Plex Libraries each of which contains the metadata for the media in the repositories to which they point;
  • Plex clients of two classes as listed below.

Plex clients:

  • A fairly robust and full-featured client that allows editing the library metadata; it just seems to be called “Plex” on my Mac; and,
  • A lightweight client (“Plexamp”) whose purpose seems to be solely a player that can connect to other Plexamp clients on different machines.

So, the model I have in my mind is that there could be:

  • Multiple Plex Media Servers pointing to multiple media repositories (some pointed to by different Plex Media Servers).
  • Multiple Plex clients each of which connect to a single(?) Plex Media Server which, in turn, interacts with various Plex Libraries pointing to various media repositories.
  • All of these subsystems may be on different machines (although I suspect Plex Media Servers must be on the same network as the media repositories they point to).

Where is the media metadata of a Plex Library stored? If that data are just filesystem objects, can they be “reused” by multiple Plex Media Servers?

Can a Plex client connect to a multiple Plex Media Servers?

Can multiple Plex clients on different machines but all using the same user simultaneously connect to a Plex Media Server?

Plexamp seems to be a different beast allowing a single Plexamp client interact with the Plex Media Server to play to a directly connect audio system; let’s call that client the Plexamp Master. Now, it seems other Plexamp clients can connect to and control the Plexamp Master.

Hence, I can:

  • Have my Plex Libraries and the Plex Media Server reside on my NAS;
  • Use the Plex client on a client machine to curate a Plex Library and edit its metadata;,
  • Separately use the Plexamp master on a machine connect to a sound system to play media; while,
  • Using other Plexamp clients on other machines to control the media play via the Plexamp master.

Did I get that right?

Sorry if I’m rambling, it’s been a challenging week and I’m tired. I prefer drawing UML or SysML diagrams when discussing these things…

Plex (the company) runs some backend services such as server registration (claiming), sourcing metadata and feeding it to your server, remote access registration, etc. But other than account management functions you never directly interact with those systems.

Agreed. I don’t think the backend will be of much interest here.

Again, thank you for your patience!

BTW, for your interest, the underlying issue I’m attempting to resolve and for which I will most likely post a second question is the following: I upgraded DSM 6 to DSM 7 and subsequently my Plex Media Server. Unfortunately, the Plex Libraries associated with my initial DSM 6 Plex Media Server seemed not have migrated to the DSM 7 Plex Media Server. I’m hoping to find a way to recover the metadata contents of the lost Plex Libraries since I made many updates to the metadata (eg: artists, titles, etc). (The Plex system seems to not recognize a significant fraction of my media. I’m old with weird, eclectic tastes… :slight_smile: )

Media files can be stored locally on the Plex Media Server or on networked storage such as a NAS using SMB or NFS. Plex Media Server does not know if the files are local or remote. It simply follows a directory path to the files (ex: You’ve movies in /media/movies. Plex doesn’t know (or care) if that is a local drive, a NFS mount, or whatever. It just follows the path.).

Not exactly.

Plex Libraries are how you access the media files. For example, you create a movie library, then add the directory paths so Plex Media Server knows where the files are located.

Items such as metadata, chapter thumbnails, the Plex database, etc. are stored in the Plex Data Folder. On Synology DSM 7 systems, this is the PlexMediaServer shared folder. Never place media files in the Plex Data Folder. Doing so can cause server instability.

Plex Media Servers are independent of each other, even when claimed by (assigned to) the same account. They do not communicate with each other (there is some backend synchronization with plex.tv for items such as watched state and ratings).

The Plex Data Folder cannot be shared, synchronized, etc. between multiple Plex Media Servers. For example, if you change a movie’s sort title on one server, it will not be synchronized with other servers.

Not exactly.

Use Plex Web or Plex Desktop (the native Mac/Win/Linux app) to administer the Plex Media Server. You can also use them to play media files on your PC.

If using other devices - SmartTV, streaming box/stick, etc. - you would use the Plex app for that device.

Plexamp is for streaming music files. Plex Photos is for streaming photos.

You can “cast” or “fling” media between Plex clients. This is using one client to control another. The media stream flows from the server directly to the controlled client. See Plex DocumentationCasting, Flinging, & Remote Control.

You can have multiple servers, but most people do not need to do so. A single server can stream videos, music, and photos to multiple Plex clients, both local and remote.

Plex clients can stream media from multiple servers. Those servers can be yours or shared with you by others.

Yes, as long as the user has been granted access by the server owner (the server owner/admin always has access since it is their server).

Plexamp plays music streamed from the Plex server. There are Plexamp apps for mobile and desktop.

One Plexamp app can cast/fling music to another Plexamp app on the same network (as mentioned above).

For connecting to an audio system, you may want to check out Plexamp Headless. It is a “receiver only” client that runs on a Raspberry Pi. Connect the RPi to your audio gear via your desired method - HDMI, USB DAC, Toslink, etc. To listen to music, switch to the proper audio input, then cast to the Pi from Plexamp on your PC, phone, etc.

Yes.

Use Plex Web or Plex Desktop on a PC/workstation/etc.

Make sure you follow Plex naming requirements. Doing so will cut down on the amount of metadata editing for movies and shows (see Your Media).

Yes.

There really isn’t a “master” Plexamp. You can fling from any Plexamp app to another.


I think I answered everything. Let me know if I missed something or didn’t explain it well enough.

Do you still have the /Plex shared folder?

Are the database files still present in /Plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases?

If so, it is possible to recover your old server. However, if you’ve created a new server since updating to DSM 7, the new server will be wiped out.

Here’s the process:


Please read all of this before proceeding.

Synology forced Plex to make a lot of changes for DSM 7. Unfortunately, it is not possible to simply update DSM and have Plex work.

The Plex Data Folder is now /PlexMediaServer instead of /Plex. Also, PMS runs under the PlexMediaServer username instead of Plex.

The normal process is covered in FAQ 27 - Migrating an existing PMS from DSM 6 to DSM 7.

Your system is basically halfway migrated. You need to back up a few steps, then start the migration again.

The process is straightforward - set some permissions, uninstall PMS, then re-install it and let it migrate. It will delete the new instance of Plex Media Server and migrate your old server.

Question: Do you still have the /Plex shared folder with the database and other files?

In /Plex/Library/Application Support/Plex Media Server/ you should see many folders for Logs, etc. The database files are in …/Plug-in Support/Databases.

IMPORTANT: IF THE ANSWER TO ABOVE IS NO, THEN STOP.

Question: The NAS has the new /PlexMediaServer shared folder as well, correct?

If Yes to both, then the migration from Plex on DSM 6 to Plex on DSM 7 failed. Your old server is still there (in /Plex), but the files did not migrate.

Here’s how to proceed:

NOTE: This will completely remove the new instance of Plex Media Server, then restore your old server.

Step 1: Login to the NAS. User must have admin rights.

Step 2: Control Panel → Security. Set logout timer to a large value such as 3600. You can change it back when finished.

Step 3: Give user PlexMediaServer full control of the /Plex shared folder.

Control Panel → Shared Folder. Select Plex and Edit.

On Permissions Tab, change Local User to System Internal User.

For user PlexMediaServer, select Custom. Select all boxes - Admin/Read/Write. Click Done.

IMPORTANT: You will be back at the Edit Shared Folder window. Check the box to “Apply to this folder, subfolders, and files.” Save.

Step 4: Give user PlexMediaServer permission to access your media files. Repeat step three for the shared folders holding your media. Give either read-only or read-write access. Admin rights are not needed.

Note: Read only is sufficient for Plex Media Server. Read-write is needed if you are recording using LiveTV/DVR, creating optimized copies, etc.

Step 5: Completely remove the new server from your system.

Launch Package Center and uninstall Plex Media Server.

When prompted, choose “Erase all of Plex Media Server from this system (Not Recoverable).” This removes the new server from your system (your media files are not touched).

When the uninstall finishes, use File Station and look in /PlexMediaServer. If there are any files there, delete them. The folder must be empty.

Step 6: Re-install Plex and start the migration.

Re-install Plex Media Server. When prompted, choose a “Normal” not Claim Token installation. Suggest you use the current public release available at plex.tv. The version available via Synology Package Center is usually several versions out of date.

This will start the migration. The installer will move the files from /Plex to their correct location in /PlexMediaServer.

The installation will take some time. A rough estimate is 1 minute for every 1000 media files on the server (movies/shows/etc).

If possible, do not logout. It won’t hurt anything, the migration will continue, but you will not be able to see the progress. This is the reason for increasing the logout timer earlier.

Step 7: When complete, claim the server.

When the process completes, /Plex should be empty except for a migration.log file.

From a system on the same network, login using the IP address of the NAS. For example, if the NAS’ IP address is 10.1.2.3, use http://10.1.2.3:32400/web.

Do not use app.plex.tv, a domain name, click the Open button in Package Center, etc. Those methods cannot be used for claiming. Once claimed, then they’re OK.

Once claimed, you should see your libraries, etc.

Regret delay in responding…

Thank you for your very detailed instructions but I’m afraid I’ve done something wrong.

My old /Plex shared folder was still populated with many files including the database files and I had the new /PlexMediaServer folder so it appears I had the “failed” upgrade situation you described.

I granted the PlexMediaServer user the permissions as described then used Package Center to uninstall Plex Media Server erasing all of the previous server. I confirmed that /PlexMediaServer folder was now empty.

I then re-installed Plex Media Server using image PlexMediaServer-1.41.6.9685-d301f511a-x86_64_DSM7.spk which was, I believe, the latest Plex Media Server for my Synology DS418play.

Package Center indicated the installation was complete approximately 8min after starting and displayed a dialogue with the following text:

Plex Media Server - DSM 6 → 7 upgrade on Tue May 6 13:53:50 EDT 2025.

Migrated existing Plex Media Server installation from

‘/volume1/Plex’.

The migration log is available for review: /volume1/Plex/Migration.log

Cleaned ‘/volume1/Plex’.

Installation Successful!

Note: If Plex cannot access your media, verify user PlexMediaServer is granted permission in Control Panel.

Set access to your media share(s) by performing the following steps:

  1. Open Control Panel and select Shared Folder
  2. Select the share which contains your media and click

Edit

  1. Click the Permissions tab
  2. Change the dropdown from Local Users to System internal user
  3. Check the Read/Write checkbox for the PlexMediaServer user
  4. Click Save to confirm the new permissions
  5. Repeat steps 2-6 for each share you want Plex Media

The /Plex folder was now empty except for Migration.log:

Plex Media Server migration to DSM 7 started: Tue May 6 13:53:50 EDT 2025
=== Tue May 6 13:53:50 EDT 2025 === Start: Change ownership
chown: cannot dereference ‘/volume1/Plex/Library/Application Support/Plex Media Server/Cache/va-dri-linux-x86_64/iHD_drv_video.so’: No such file or directory
=== Tue May 6 13:54:09 EDT 2025 === Completed: Change ownership
=== Tue May 6 13:54:09 EDT 2025 === Start: Convert symbolic links
=== Tue May 6 13:54:50 EDT 2025 === Completed: Convert symbolic links
=== Tue May 6 13:54:50 EDT 2025 === Start: Migrate Plex Media Server
=== Tue May 6 13:58:51 EDT 2025 === Completed: Migrate Plex Media Server
=== Tue May 6 13:58:51 EDT 2025 === Completed: Migrate Plex Media Server
=== Tue May 6 13:58:51 EDT 2025 === Start: Clean /volume1/Plex
=== Tue May 6 14:00:00 EDT 2025 === Completed: Clean /volume1/Plex

(Hmmm… Suspicious completion date of 14:00:00 exact…)

The /PlexMediaServer folder now contains 11.47GB (12,319,436,165 Bytes) in 28237 files and 31199 folders.

Thinking the migration complete, I attempted to access the Plex Media Server via Safari at http://my_NAS_IP_addr:3400/web) which resulted in the following page:

> This XML file does not appear to have any style information associated with it. The document tree is shown below.
> 
> <Response code="503" title="Maintenance" status="Plex Media Server is currently running startup maintenance tasks."/>

Now, my media source folder contains 703.79GB (755,691,606,301 Bytes) in 88512 files and 17032 folders. Naturally, not all of the files are media (some are cover art, etc), but let’s use the file count as an upper bound of the number of media files.

Assuming the file count is processed at 1min per 1000 media files and that the ~89k files are all media files => ~89min processing => ends ~14:00 + 0:89 = ~14:00 + 1:29 = ~14:00 + 1:30 => ~15:30 hours.

I assumed Plex Media Server was now busy cataloguing my media files I continued waiting. I also confirmed that user PlexMediaServer has the appropriate perms for my media source folder.

Unfortunately, it’s now 16:41 hours and Safari returns the same page as described above.

Any thoughts?

Thank you for your perseverance and assistance!


Mod Edit: Formatted to make “503 maintenance” visible. @FordGuy61

You did everything right. The migration is complete. Otherwise you would not have the migration.log file in /Plex.

The 503 Maintenance message is normal. Plex is updating the database structure to match the new version of PMS.

Let the process run. If you stop it, it will just start over. It may take minutes or hours depending on the size of the database files, NAS CPU speed, and the amount of database changes.

The web page does not auto-refresh. Either refresh it manually or close & re-open the window.

Give it a couple more hours to complete.

If you still have the same message write back and we’ll take some other steps.

Unfortunately, it’s almost 24hrs since the migration completed (now Wednesday 13:35 hours the next day) and the web page (new browser instance so it’s fresh) is still displaying the same message.

Reference “Let the process run.” I assume that in order to stop the process I would have to take some active steps (eg: use Package Center to stop Plex Media Server). Package Center indicates that Plex Media Server is still running.

DSM Resource Monitor Services tab indicates Plex Media Server is using 0% CPU 11.8MB memory and Processes tab indicates both Plex Media Server & Plex Scripting Host are sleeping.

“Try turning it off and on again.”? (Brit TV series ‘The IT crowd’ reference for humour… :slight_smile: )

Stop, uninstall, reinstall while maintaining the databases?

Let me know… And thank you again for your perseverance and assistance!

Thanks for the update. The IT Crowd is hilarious. I need to re-watch it. :rofl:

Yeah, should have finished by now.

Let’s take a look at the log files and see if they show anything.

  1. Use Package Center to stop Plex Media Server.
  2. In File Station, navigate to the Plex Data Folder. Right click on the Logs directory and choose Compress to Logs.zip.
  3. Attach the zip file to this thread.

Question: Are you familiar with the Linux command line and accessing the server via SSH? May or may not be needed, depending on what is in the log files.

Thanks for the update. The IT Crowd is hilarious. I need to re-watch it. :rofl:

Yup!

Let’s take a look at the log files and see if they show anything.

  1. Use Package Center to stop Plex Media Server.
  2. In File Station, navigate to the Plex Data Folder. Right click on the Logs directory and choose Compress to Logs.zip.
  3. Attach the zip file to this thread.

Logs.zip (769.5 KB)

Here you go. I took a quick look and saw lots of errors, etc. Sigh…

Question: Are you familiar with the Linux command line and accessing the server via SSH? May or may not be needed, depending on what is in the log files.

Well, I’m a retired software engineering manager which means I know enough to be dangerous around code… :slight_smile: I haven’t played with SSH in years but I can (with plenty of googling) work my around bash, so you may need to hold my hands from time-to-time.

As Buckaroo Banzai said:

No, no, no, don’t tug on that. You never know what it might be attached to.

As alway, thank you!

Thanks for the log files.

Good news is the database migrations completed and there are no signs of database corruption.

However, it looks like the server is now unclaimed (no longer linked to your account). It also looked like the NAS had trouble communicating with hosts at plex.tv.

First, double check the network settings on the NAS. Make sure the IP address, mask, and default gateway are correct. Synology Control Panel → Network → Network Interface tab.

Second, synchronize the NAS with a public NTP server. Synology Control Panel → Regional Options. The NAS time needs to be close to real time for claiming to succeed (not down to the second, but it can’t be hours off either).

Third, Follow FAQ 31: Reset / Reclaim PMS on DSM 7 (Not Authorized - Locked Out) to reclaim the server. You’ll uninstall PMS, then re-install the same version (1.41.6.9685), using the Plex Claim Token method. This is only the application. The PlexMediaServer folder and media files are not touched.

If successful, you’ll see a “successfully claimed by” message.

Then try and login directly to Plex using the NAS IP address, http://ip_address:32400/web. Hopefully you can login, reach server settings, see your libraries, etc.

If the claiming fails note any error messages on-screen and pull a new set of log files.

FYI, I saw all the MediaProviderManager error messages. Not sure what is causing those. It could be that the server is unclaimed and/or having problems communicating with plex.tv.

Good news is the database migrations completed and there are no signs of database corruption.

Yay!

First, double check the network settings on the NAS. Make sure the IP address,

Confirmed correct.

mask

Subnet mask is 255.255.0.0 which, I believe, is correct.

default gateway…

Set to the IP address of my primary mesh access point to which my NAS is connected by cabling via a couple of switches in series. In turn, the access point is wired to my cable modem connected to my ISP.

Second, synchronize the NAS with a public NTP server. Synology Control Panel → Regional Options.¬

Connected to time.google.com, status = Normal.

Third, Follow FAQ 31: Reset / Reclaim PMS on DSM 7 (Not Authorized - Locked Out)

Consulted

to reclaim the server. You’ll uninstall PMS,

Uninstalled “Uninstall only”.

then re-install the same version (1.41.6.9685), using the Plex Claim Token method.…

Done.

If successful, you’ll see a “successfully claimed by” message.

Seen. Claimed by my Plex persona.

Then try and login directly to Plex using the NAS IP address, http://ip_address:32400/web. Hopefully you can login, reach server settings, see your libraries, etc.

Logged in. Can play music using the Plex for Max and the Plexamp for Mac clients. Yay! A few issues detailed below in ‘New observations’.

If the claiming fails note any error messages on-screen and pull a new set of log files.

No error messages observed.

FYI, I saw all the MediaProviderManager error messages. Not sure what is causing those. It could be that the server is unclaimed and/or having problems communicating with plex.tv.

Q: Since I’ve got the new Plex Media Server claimed and I can play media files locally, may these historical error messages now be ignored?

New observations

I now have two sets of libraries (each having a “music” & an “audiobook” libraries) corresponding to libraries created before the DSM update (set A) and another created after the DSM update (set B). Set A is operational while set B is not (as expected).

Q: How do I remove the libraries in set B from the Plex & Plexamp apps?

Libraries in set A seem not to have “noticed” the new media files added during the inter-regnum. Reading Scanning vs Refreshing a Library and noticing that ‘Plex for Mac / Settings / <my_server> / Settings / Library’ has ‘Scan my library automatically’ enabled and ‘Scan my library periodically’ (with interval ‘daily’) leads me to the assumptions that the new media folders:

  1. Aren’t watched by the automatic scan subsystem (since the new media “snuck in” and wasn’t registered); and,
  2. Will be scanned during the periodic daily scan.

Q: Are my assumptions correct? If not, please clarify.

Q: Am I correct in understanding that audio libraries can no longer be accessed via the Plex for iOS & Plex for iPadOS apps and instead can only be accessed via the corresponding Plexamp apps? If so, an interesting spec decision…

Again, as always, thank you so very much for your assistance!

(BTW: Do you get the reference to BensonArizona? :slight_smile: )

Good to hear things are up and running again.

Look in Authorized Devices. Delete any non-existent servers. If you accidentally delete the wrong one nothing horrible happens. It just unclaims the server and you have to re-claim it.

You may also need to unpin the libraries from the home page on your various clients.

You’ll also see your clients listed. You can delete old entries if desired. If you delete a current client it just unauthorizes it and you’ll have to sign in again.

Yes.

I do not know why Plex did not pick up the new media files.

Plex Media Server should pick them up both when it starts and automatically. It scans all libraries when it starts. It also picks up the notifications from Linux when the file system changes (files added/deleted/etc.).

Manually scan the libraries. If it does not pick up the files, then something is amiss. It is usually, but not always, permissions or naming & organization. Start with Why is some of my content not found. If none of that helps, write back and we’ll figure it out.

Going forward, Plex should definitely pick up media as you add it to the server.

I have Plex running on my DS918+. When I copy files from my PC to the NAS, Plex always scans and adds them to the system.

Yes. Plex for videos. Plexamp for music. Plex Photos for photos.

Must admit that I do not. There’s the town Benson, Arizona, but I don’t know anything about it.

Look in Authorized Devices. Delete any non-existent servers. If you accidentally delete the wrong one nothing horrible happens. It just unclaims the server and you have to re-claim it.

You may also need to unpin the libraries from the home page on your various clients.

You’ll also see your clients listed. You can delete old entries if desired. If you delete a current client it just unauthorizes it and you’ll have to sign in again.

It seems the entries for the old libraries have disappeared overnight so problem solved!

However, I do have questions about the ‘Authorized Devices’ page:

  1. I have two server entries for my Plex Media Server on my NAS, both with the info (eg: PMS version, HW model, DSM version) except one is dated “20 hours ago” while the other is “3 days ago”. Am I correct in assuming the older is prior to re-installation of PMS and can be deleted while the new is the current PMS authorized?
  2. Likewise, I have multiple entries for Plex for Sonos, Plexamp for iOS & iPadOS, etc with different dates. Am I likewise correct in assuming I can delete all the older duplicates while the authorization of the latest is retained?
  3. I have entries for “Plex Mediaverse”, “Plex Auth App (Safari)” (independant of a lone entry for “Safari” for Plex Web which I assume is the Safari client for PMS). What are Plex Mediaverse & Plex Auth App? Can they be deleted?

I do not know why Plex did not pick up the new media files.

Plex Media Server should pick them up both when it starts and automatically. It scans all libraries when it starts. It also picks up the notifications from Linux when the file system changes (files added/deleted/etc.).

I have Plex running on my DS918+. When I copy files from my PC to the NAS, Plex always scans and adds them to the system.

Yes, this is also the way my system used to work.

The periodic daily scan (which I assume would be scheduled for overnight) did not run.

Manually scan the libraries. If it does not pick up the files, then something is amiss. It is usually, but not always, permissions or naming & organization. Start with Why is some of my content not found. If none of that helps, write back and we’ll figure it out.

I manually ran the scan and it seems to have picked up all the missing tracks. It’ll take a couple of days to confirm and, if any are missing that I can’t add, I’ll advise.

Going forward, Plex should definitely pick up media as you add it to the server.

Concur!

I believe I’ve noticed another anomaly:

I have two libraries, eg: ‘My Music’ & ‘My Audiobooks’.

Plexamp currently shows ‘RECENTLY ADDED IN ’ (where is either ‘MY MUSIC’ or ‘MY AUDIOBOOKS’).

I believe Plex for Mac and Plex Media Server (from DSM > Package Center > Plex Media Center) previously listed the recently added for each library separately as well.

Now, however, it merges both lists into a single ‘Recently Added Music’ list.

Is this correct behaviour?

Must admit that I do not. There’s the town Benson, Arizona, but I don’t know anything about it.

It’s the song from a cult science-fiction film called ‘Dark Star’ which started as a student project by John Carpenter (of ‘Friday the 13th’, ‘The Thing’, ‘They live!’, etc) and Dan O’Bannon (of ‘Alien’, etc). A funny little film including a sentient bomb that refuses orders to stop its countdown… :slight_smile:

As always, thank you so very much for your assistance!

Yes. Delete the older listing.

Yes for Plexamp, etc. Caveat: I’ve no Sonos gear, so have never had to authorize any of it. AFAIK, it behaves like any other client. Worst case is you would have to re-authorize it.

Mediaverse is the video on demand service - live tv, ad supported movies, movie rentals (point a browser at mediaverse.plex.tv and you’re redirected to watch.plex.tv).

I don’t know all the mechanisms behind the scenes, but it is used when you add your streaming services in account settings, Plex shows “other places to watch,” and that part of Plex. It does not hurt anything to delete them.

The Authorization listings are used to allow devices/services to access Plex Media Server. For example, I use Tautulli to monitor my Plex server, and there is a Chrome authorization entry for it. I believe you’ll see similar entries if using things like Amazon Alexa integration (and maybe sonos?). It does not hurt to leave old entries, and if you delete one that is in use, you’ll just have to reauthorize things.

Settings → Manage Section → Libraries. Scroll to bottom. See setting for Merge Recently Added items. If checked, uncheck it and see if that helps.

Looks like a fun movie. Now added to my watchlist on Amazon Prime video (Also available via Plex on Demand). Thanks!


Mediaverse Followup: I searched for Dark Star in Plex. It shows listed in Plex on-demand (enabled in account settings) and Amazon Prime Video (enabled in Online Services). The “+ 18 more” shows other services that offer the movie. This is part of the Plex Mediaverse stuff discussed above.

Yes. Delete the older listing.

Yes for Plexamp, etc. Caveat: I’ve no Sonos gear, so have never had to authorize any of it. AFAIK, it behaves like any other client. Worst case is you would have to re-authorize it.

Done. I’ve deleted all the older listings for devices but retained their latest. I’ll let you know if I run into any issues with Sonos, but I believe all will be well.

BTW: My experience with Sonos in the last year or so after the debacle concerning their apps has made me rethink the entire “let’s integrate everything into one package” design concept (except for portable devices). On my project list is to create a small networked sound system that will allow me to hook up speakers (that don’t need SW or FW updates); I’m thinking of basing it on a Raspberry Pi or smaller and running Plexamp on the RPi if it’s compatible. Image: Spinning propellor on my cap…

For example, I use Tautulli to monitor my Plex server

Interesting! I’ll look into it. Tx! I don’t think my NAS has the horsepower to support Tautulli under Docker, so I may have to convince She Who Must Be Obeyed that a NAS upgrade will soon be necessary… :slight_smile:

Settings → Manage Section → Libraries. Scroll to bottom. See setting for Merge Recently Added items. If checked, uncheck it and see if that helps.

Worked! Tx!

Looks like a fun movie. Now added to my watchlist on Amazon Prime video (Also available via Plex on Demand). Thanks!

Enjoy!

Mediaverse Followup…

Tx! I’ve seen a bunch of stuff there I’d like to see after I burn off those on my CaTV STB. (My CaTV/ISP provider is about to obsolete it so…)

Well, I think that just about wrap it up. Thank you so very much for your complete & concise assistance! Is there any upvotes or such I may give you? (I’m unfamiliar with this system and if any are actually meaningful for you… I tend to limit my presence on the Internet…)

I suspect you are either an employee of Plex or the equivalent to an MVP, so “well done!”.

Again, thank you so much and have a great rest-of-weekend! Cheers!