Can't seem to support local media with Plex for Synology

Plex Media Server NAS & Devices
1

Server Version#:1.41.5.9522
Player Version#: Web

Synology Version: DSM 7.2.2-72806 Update 3

When I log into the Plex web app (or any plex app, really), I can’t see any of my media stored on my Synology NAS.

Things seem to have gone wrong after a network upgrade, which changed the server IP.

Even when I log into Plex on the Synology http://foobar.lan:32400/web/index.html#!/, and I click on “Your Media”, it just displays the “Get Plex Media Server”.

How can I fix this?

Edit: I tried uninstalling and reinstalling the Synology server. I copied the claim code, and repair failed with:

“Could not complete dialog with Plex.tv. Unable to claim”.

2

Check the DNS and gateway settings on the Syno to confirm they point to your modem/router.

I looked at Plex.tv using the username you’re using here in the forum.
There are no servers registered under this email.

3

The DNS and gateway addresses are correct.

I had uninstalled Plex on the Synology using the ‘Sign Out and Unclaim this server’ option originally.

I next tried uninstalling Plex with the ‘Uninstall only’ option. This “succeeded”, but now when I visit http://foobar.lan:32400/web I get “Not Authorized”.

The support article doesn’t talk about how to fix things on Synology, and while I could find the Preferences.xml, it doesn’t have any of the PlexOnline tokens in it.

4

Preferences.xml will not contain tokens until after you have connected the server to https://plex.tv.

Reboot your modem/router and everything connected to it, including any wireless devices.

Then open Plex/Web using http://NAS-IP-Address:32400 and go to Plex Settings > Authorised Devices and remove all entries listed under Server.

Then close and reopen Plex/Web and make sure you sign in with the correct Plex credentials.

Go To Plex Settings > Server > General and make sure the server is claimed.

To view your media, go to the Plex/Web Home page and click on More > (bottom of the flyout menu on the left of screen).

Locate the libraries you wish to display on the Home page and then Pin them.

Return to the Home page and you should now see the libraries you pinned on the flyout menu on the left.

The process is similar in most Plex apps as well.

Don’t forget to customise and enable viewing the libraries etc. in Plex Settings > Server > Libraries > Manage Recommendations.

Note: > Server > is a reminder to select the correct server in Plex Settings, assuming you have more than one Plex server. You may ignore that instruction if you only have one Plex server.

5

I rebooted the Synology, the modem, and the UniFi router. There are too many devices on the network to individually reboot each one.

I opened Plex/Web using http://NAS-IP-Address:32400 and I get “Not Authorized”. So I can’t remove the authorized devices from the NAS. I did go to Plex/Web on my desktop (https://app.plex.tv/desktop/), but there were no server devices listed there.

6

This, https://app.plex.tv/desktop/ is Plex/Web Remote and it is hosted by Plex.
Your server will not appear there, until after you connect your server to https://plex.tv.

You should always open Plex/Web Local when dealing with network issues such as this.

That said you need to make sure the NAS and your Plex Server are able to access the internet.

The “Not Authorized” message is telling you that you are not signed in and there is no connection to the internet.

Check all network settings on the NAS and in your modem/router etc.

To set the NAS back to default network settings, see this page:

7

I would love to access Plex from my NAS. But I CAN’T. I select my user and immediately get Not Authorized.

The NAS can see the internet JUST FINE. QuickConnect works, cloud sync works, everything works.

EXCEPT PLEX.

8

There is a race condition when plex is not claimed and you use QuickConnect.

When you click QuickConnect to connect to your server

  1. The request goes out to Synology in Taiwan, sending your QuickConnect domain and username

  2. Synolgy becomes a proxy back to your server
    – It connects to your server using the synology FQDN

  3. When unclaimed, PMS is very strict about what it allows to connect. The is done to protect your server & media from unauthorized claiming by someone outside you home in the case where it’s unclaimed.
    – Connections from the local LAN (your subnet & same as the Syno IP) are allowed
    – Connections using, or including, a FQDN (which is what Synology is doing) are refused.

Earlier you stated:

  1. You can’t use a FQDN in the URL for the reasons above
  2. Have you tried the: ?
    – Uninstall Only
    – Install again using “Plex Claim Token” method
  3. If you have internet working, this will succeed
    – It prints your username and email as verification in the popup at end of installation.

The procedure is here, in the FAQ

9

I did get it to reinstall properly (using a FQDN, because my router resolves the .lan prefix) using the Uninstall Only/Plex Claim Token method. I’m not sure what the purpose of Sign out and unclaim server is, but you can’t reclaim the server using a Plex Claim Token, so (IMO) it’s misleading.

10

I’m the author of the Synology packaging scripts & menu system.

  1. Uninstall only – Removes only the code. Data is not touched
  • DSM stores PMS code in /var/packages/PlexMediaServer/target
  • Your server data is assigned to the PlexMediaServer shared folder
    which is universally addressable as /var/package/PlexMediaServer/shares/PlexMediaServer

2.. Sign Out and unclaim performs two operations

  • Removes the package (#1 above)
  • Edits the Preferencs.xml file and removes your credentials from it. This allows you to reclaim it under a different account when you next install the package.

  1. Normal installation installs the software again – ASSUMING the server is claimed or new (and can be claimed by opening using http://LAN.IP.of.Syno:32400/web )

  2. When not able to claim the server using its LAN IP (meaning the LAN IP is not RFC-1918 compliant) or wonky modem/router firewall or ISP, the Plex Claim Token method takes the token you give it and does the handshake with Plex.tv for you as it’s installing the package. (Normally the browser Plex/Web would do this … but RFC-1918 LAN addressing is required and FQDNs are not allowed.

The purpose of the Plex Claim Token method is for maximum flexibility.
it will work even when your NAS has a public IP address (Common for college students who take their NAS with them)

11

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