Media Settings Option Gone after fix for DSM 7.1.1 Update 7

Server Version#: 1.41.3.9314-a0bfb8370-x86_64_DSM7
Player Version#: N/A
Synology DS-918+
DSM: DSM 7.1.1-42962 Update 7

I got caught in the issue mentioned in previous posts where Package Center was blank and my media was unreachable.

I applied the following fix provided in the Synology forum which made Plex accessible again via Package Manage.
I’m also able to reach it via https://ds918_fqdn:32400/web/index.html#!/

This is where it all goes wonky.
When I go to ‘Settings’, there is no ‘Library’ settings at all. I’ve got headings for my account and for ‘Plex Web’ but nothing else.
When I’m at the home page, there’s a pinned heading “+ Your Media Files” but when I click on this is tells me to download Plex Media Server.

I’ve already verified permissions on the PlexMediaServer folder, Plex folder, Music, Video and Photos folders. All looks good. I even expanded some of these from being Read/Write to full Admin just in case.

I’ve uninstalled and reinstalled. I’ve re-started the app. The only thing i haven’t done is a full uninstall and reinstall; meaning blown away the PlexMediaServer folder. I’d like to avoid this if possible but whatever needs doing.

Attaching a few log files:
Plex Media Server.log (366.3 KB)
Plex Media Server.2.log (526.9 KB)
com.plexapp.system.log (32.8 KB)

Any help troubleshooting what’s going on is appreciated.

Thanks for the logs.

Your description plus the logs shows your server got signed out.

Do you have Package Center working again (the patch applied) ?

If so, you can do the following:

  1. Uninstall the PMS package
  2. Reinstall the same SPK file – EXCEPT
    – Use the Plex Claim Token option
  3. Click “Get Plex Claim Token”
  4. COPY the token from the browser tab which opens
  5. PASTE it into the install menu page
  6. Click NEXT NEXT DONE and let it install & claim for you

For reference, here’s the FAQ

That fixed it!

The fix I applied was the one from the Synology forum:

I created a task in Task Scheduler and applied this:

cp -af /usr/syno/synoman/webman/modules/PkgManApp/PkgManApp.js /usr/syno/synoman/webman/modules/PkgManApp/PkgManApp.js.bak

rm /usr/syno/synoman/webman/modules/PkgManApp/PkgManApp.js.gz

sed -i ‘s/SYNO.SDS.htmlEncode/Ext.util.Format.htmlEncode/g’ /usr/syno/synoman/webman/modules/PkgManApp/PkgManApp.js

When I first reinstalled it I saw the token options. I did a little googling trying to figure out if I needed a token or not. In the past I don’t remember having to do this. Just login with my account and that is it.

So, the token ties the server to my account. I’ll remember this in the future.

Curious, what was the reasoning behind implementing using a token for the server?

When the credentials get confused / messed up., that (re)install option clears out the current values from Preferences.xml and writes fresh (using the claim token you give it)

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.