Claim Server is not working synology diskstation DS218+

Plex Media Server NAS & Devices
1

Have you checked the Plex knowledge base and searched on the sub and Google: Yes

Server version: 1.11.3.4803

OS: Linux

Clients, w/ versions, if applicable: trying to claim server via http://ip_of_nas:32400/web/

What you did? Trying to claim server on network.

What happened? Nothing I can see the Request is made:

Request URL:https://plex.tv/api/claim/token?X-Plex-Product=Plex%20Web&X-Plex-Version=3.31.1&X-Plex-Client-Identifier=aih7s9likku8s5ln9xqgnws9&X-Plex-Platform=Chrome&X-Plex-Platform-Version=64.0&X-Plex-Sync-Version=2&X-Plex-Device=Windows&X-Plex-Device-Name=Plex%20Web%20(Chrome)&X-Plex-Device-Screen-Resolution=1080x1789%2C1080x1920&X-Plex-Token=F5oa89FcxMb8Xuy91dxH&X-Plex-Provider-Version=1.1
Request Method:GET
Status Code:200 OK
What you expected? Claim server would work

What are your (relevant) settings? Default install of 1.11.3.4803 nothing fancy other than that.

Link to logs (optional but recommended): gist.github.com/anonymous/98c0e44f66f802ae492c11361f66dfb6

2

What are you trying to do?

Normal first-run setup is via the browser http://ip.addr.of.syno:32400/web
Sign in
click Got It
Proceed with First-run setup wizard

3

When I sign in I am not presented with First-run setup wizard. Is there a way to invoke it? This is my first time using plex so I do not know my way around the UI. When I sign in I am presented with

While signed in if I hit http://ip.addr.of.syno:32400/web again I get:

If I then click on claim server nothing happens. Logs from this mornings attempt:
gist.github.com/anonymous/3b76e95d58da8672602c64a532106e04

4

@ChuckPA said:
What are you trying to do?

Normal first-run setup is via the browser http://ip.addr.of.syno:32400/web
Sign in
click Got It
Proceed with First-run setup wizard

As stated in the OP I am trying to use claim server Request and it is not working.
Please see above post for further details, and log files form this morning.

5

In order to define libraries (load media) as you show above, you had to have claimed it at some point.

Based on the screen shots you have included, look at the grayed figurine in the upper right corner.
Click it.
Click Sign In

6

@ChuckPa said:
In order to define libraries (load media) as you show above, you had to have claimed it at some point.

Based on the screen shots you have included, look at the grayed figurine in the upper right corner.
Click it.
Click Sign In

I have signed in and attempted to claim the server again.

the result is:
Request URL:http://192.168.0.11:32400/myplex/claim?token=claim-ijxPD23EGNAT4wPYdp4k&X-Plex-Product=Plex%20Web&X-Plex-Version=3.31.1&X-Plex-Client-Identifier=aih7s9likku8s5ln9xqgnws9&X-Plex-Platform=Chrome&X-Plex-Platform-Version=64.0&X-Plex-Sync-Version=2&X-Plex-Device=Windows&X-Plex-Device-Name=Plex%20Web%20(Chrome)&X-Plex-Device-Screen-Resolution=2560x1309%2C2560x1440&X-Plex-Provider-Version=1.1
Request Method:POST
Status Code:500 Internal Server Error
Remote Address:192.168.0.11:32400
Referrer Policy:no-referrer-when-downgrade

token:claim-ijxPD23EGNAT4wPYdp4k
X-Plex-Product:Plex Web
X-Plex-Version:3.31.1
X-Plex-Client-Identifier:aih7s9likku8s5ln9xqgnws9
X-Plex-Platform:Chrome
X-Plex-Platform-Version:64.0
X-Plex-Sync-Version:2
X-Plex-Device:Windows
X-Plex-Device-Name:Plex Web (Chrome)
X-Plex-Device-Screen-Resolution:2560x1309,2560x1440
X-Plex-Provider-Version:1.1

So at this point is there any solution other than uninstalling and starting over again?

7

Uninstall Plex
Reboot DSM
Reinstall Plex

A server 500 error indicates something is missing/wrong with the installation of the software.

8

@ChuckPA said:
Uninstall Plex
Reboot DSM
Reinstall Plex

A server 500 error indicates something is missing/wrong with the installation of the software.

Attempt 1:
Uninstalled 1.11.3.4803
rebooted the DSM
Installed 1.11.3.4803 again
Went to http://ip.addr.of.syno:32400/web
Signed in
Result: Claim server not working.

Attempt 2:
Uninstalled 1.11.3.4803
Rebooted the DSM
Installed 1.10.0.4523 from Package Center
Went to http://ip.addr.of.syno:32400/web
Signed in
Result: Claim server not working.

9

So I am completely clear:

  1. Are you using the native Plex application or Plex in Docker on Synology?
  2. If Docker, a "CLAIM’ token is only valid, for a limited time
  3. If the native application, the CLAIM token has no validity and will cause this problem.

What am I missing about how you’re using Plex?

10

@ChuckPA said:
So I am completely clear:

  1. Are you using the native Plex application or Plex in Docker on Synology?
  2. If Docker, a "CLAIM’ token is only valid, for a limited time
  3. If the native application, the CLAIM token has no validity and will cause this problem.

What am I missing about how you’re using Plex?

  1. This is the native Plex application package installed on the Synology DS218+
  2. N/A
  3. OK. So does that mean that the claim server functionality is unnecessary?

You are not missing anything, I have been supplying as much information as possible considering that this is my first time ever using Plex.

I have tried installing Plex via Synology’s package manager application and first had installed 1.10.0.4523. After that install was done I logged into Plex via http://ip.addr.of.syno:32400/web. That was the first time I encountered the claim server notification.
At some point on this initial install I completed the setup process because [as you could see earlier] I have created libraries for some shows and my music collection thus far.
When my first attempt to claim the server failed I noticed that a newer version of Plex was available. I downloaded that Intel - 64-bit (DSM +6.0) version 1.11.3.4803.
I then uninstalled the previous version and installed 1.11.3.4803 manually via the package manager again.
When I encountered the same issue with 1.11.3.4803 I started seeking out the cause / solution.

Please let me know if there is anything else I can provide that will help us sort this out.

11

Re: item 3. It is not only not necessary, it is causing PMS to behave as if using docker when it is running native. This causes compound confusion of the authentication.

You must have been authorized and recognized as ‘owner’ at some point else you would not have been able to add music libraries

There is a direct and easy way to resolve this but does take a few steps; This is a soft reset

  1. sign everything about Plex (including your browser )
  2. stop PMS
  3. Control Panel - Shared Folders - Edit the Plex share
  4. Add your username to the R/W Permissions tab
  5. Open File Station
  6. Navigate Plex/Library/Application Support/Plex Media Server
  7. Find and rename Preferences.xml to Preferences.xml.old
  8. Close FileStation
  9. Start PMS
  10. Open http://ip.addr.of.syno:32400/web in a fresh browser tab
  11. Sign in and click through the “Got It” page
  12. Begin to setup a new server
  13. DO NOT create any new library sections. They have been preserved. Skip this step
  14. Complete normal steps through the setup wizard and arrive at the dashboard
  15. Now your server and your browser will show you signed in.
  16. If not , Open FileStation again, Navigate down into the Plex share again and right click on Logs then Compress to Logs.zip and Attach that zip with your next post
1 Like
12

@ChuckPa said:
Re: item 3. It is not only not necessary, it is causing PMS to behave as if using docker when it is running native. This causes compound confusion of the authentication.

You must have been authorized and recognized as ‘owner’ at some point else you would not have been able to add music libraries

There is a direct and easy way to resolve this but does take a few steps; This is a soft reset

  1. sign everything about Plex (including your browser )
  2. stop PMS
  3. Control Panel - Shared Folders - Edit the Plex share
  4. Add your username to the R/W Permissions tab
  5. Open File Station
  6. Navigate Plex/Library/Application Support/Plex Media Server
  7. Find and rename Preferences.xml to Preferences.xml.old
  8. Close FileStation
  9. Start PMS
  10. Open http://ip.addr.of.syno:32400/web in a fresh browser tab
  11. Sign in and click through the “Got It” page
  12. Begin to setup a new server
  13. DO NOT create any new library sections. They have been preserved. Skip this step
  14. Complete normal steps through the setup wizard and arrive at the dashboard
  15. Now your server and your browser will show you signed in.
  16. If not , Open FileStation again, Navigate down into the Plex share again and right click on Logs then Compress to Logs.zip and Attach that zip with your next post

Thank you for this suggestion however it did not work. Just for reference I am on version 1.10.0.4523-648bc61d4 [installed from the package center] as I have been trying to get this to work for 3 hours. Please see screenshots as reference:

I followed the above steps. After I log in and get past the got it page I close out the plex pass dialogue box and proceed to the setup wizard.
I am unable to get past that first screen and an error message stating ‘there was a problem saving these settings’ is displayed.


In my console I can see a few failed Requests most notably

Request URL:http://192.168.0.11:32400/myplex/claim?token=claim-kyPYbJVZSTAsApiugWgi&X-Plex-Product=Plex%20Web&X-Plex-Version=3.27.1&X-Plex-Client-Identifier=aih7s9likku8s5ln9xqgnws9&X-Plex-Platform=Chrome&X-Plex-Platform-Version=64.0&X-Plex-Device=Windows&X-Plex-Device-Name=Plex%20Web%20(Chrome)&X-Plex-Device-Screen-Resolution=1485x1280%2C2560x1440&X-Plex-Token=F5oa89FcxMb8Xuy91dxH
Request Method:POST
Status Code:500 Internal Server Error
Remote Address:192.168.0.11:32400
Referrer Policy:no-referrer-when-downgrade

Logs are attached as you requested.

I’m at a loss at this point, and quite frustrated.

13

Fix the DNS in your network configuration . Your server cannot see Plex.tv anymore

Feb 28, 2018 23:52:04.685 [0xf0fffb40] ERROR - Error issuing curl_easy_perform(handle): 6
Feb 28, 2018 23:52:04.685 [0xf0fffb40] WARN - HTTP error requesting GET https://plex.tv/api/photos/profile (0, No error) (Couldn't resolve host 'plex.tv')
Feb 28, 2018 23:52:04.686 [0xf0fffb40] ERROR - AutoTagging: unable to retrieve updated word lists
Feb 28, 2018 23:52:04.861 [0xed159b40] ERROR - Error issuing curl_easy_perform(handle): 6
14

Thanks very much for sticking with me on this. I configured the DNS to use 8.8.8.8

2 Likes
15

All is now right with the world? (well
 PMS at least? :slight_smile: )