Can't claim server on Synology NAS

Plex Media Server NAS & Devices
1

Server Version#: Version 1.19.4.2865
Player Version#: N/A

I’m trying to migrate my Plex server onto my Synology NAS. I manually installed the Synology package that I downloaded from plex.tv, and then opened the web interface on port 32400 and went through the basic steps (not adding any libraries yet). Then I went to the settings page where it says “This server is unclaimed and not secure.”, and then clicked “Claim Server”.

Each time I do this, it hangs for a few minutes and then does nothing. Looking at the network traffic, it hangs for a few minutes and then does nothing. I attached a screenshot of the network traffic in Brave. The requests marked (failed) seem to be failing because they’re being made to 127.0.0.1, and the server isn’t running on my local computer. However, they still failed Even when I set up a port forward from the NAS to my local machine 32400 -> 32400, they’re still marked “(failed)” and don’t receive a response.

Any ideas on what I might be doing wrong here?

Screen Shot 2020-05-31 at 11.40.48 PM

(The NAS is on the same network as my computer.)

2

Plex needs to set cookies. Try using Chrome or Firefox.

Port forwarding is not needed if your PC is local to your NAS.

Also, see Synology FAQ #15.

Installation of PMS on Synology is also a helpful read.

3

Thanks, I tried it out now in Chrome and Firefox both and got exactly the same behavior. Brave only blocks third-party cookies by default, so I don’t know of any reason why it would cause an issue here. When I close and come back to my PMS in Brave, it stores and recovered by PlexPass login session with no problems.

I know I shouldn’t need to port forward, but what I’m observing in the network history is that the Plex browser app is attempting to make requests to 127.0.0.1:32400, which are all failing because there is no Plex server on localhost. Any idea what’s going on there?

4

Also, responding with a 500 to a request because it’s missing an expected cookie is, at best, really poor form, so I’d like to imagine that there’s some other issue at play here.

5

When I try to claim it by visiting plex.tv directly, instead of by accessing the server at it’s local IP address, the server isn’t listed, so I click “Where is my server?”. One of the items in that article says that I should make sure the server is listed on my “Authorized Devices” page, which it isn’t. That item links to this article for more details, but that article appears to be 100% about getting a client device listed, and nothing on that page (as far as I can tell) makes any sense for a server installation.

I am connected to the server and signed into my PlexPass account through the server, but that doesn’t cause the server to be listed under Authorized Devices, it causes my local browser to be listed there. Is there possibly another step I’m missing?

6

Did you try Method 1 in FAQ 15?

If that does not work, try the Last Ditch method.

8

Thanks! I tried the first three methods in the FAQ. claimpms gets most of the way through and then on the final API request (the one made to the actual server being claimed) it gets the following response

HTTP/1.1 500 Internal Server Error
X-Plex-Protocol: 1.0
Content-Length: 109
Content-Type: text/html
Connection: Keep-Alive
Keep-Alive: timeout=20
Cache-Control: no-cache
Date: Fri, 05 Jun 2020 00:24:16 GMT

I attached my logs from the period when the above request was made. Thanks for your help!

Logs.zip (206.7 KB)

10

Thanks again! So I unplugged eth1 physically, and then I started Plex and set the Preferred network interface to eth0. I tried the process again and got the same 500 response, although I don’t see anything about two interfaces anymore. I deleted my logs before doing the experiment, then stopped the server and uploaded the new zipped logs folder. Would you mind taking another look and seeing what the issue might be now?

I’m still seeing

Jun 04, 2020 20:50:37.103 [0x7efcad9e9700] WARN - [AutoUpdateRequestHandler] Couldn't get update channels. Trying again soon.

I do see these error responses:

Jun 04, 2020 20:49:49.740 [0x7efcad9e9700] DEBUG - HTTP 404 response from GET http://127.0.0.1:43864/:/plugins/com.plexapp.system/resourceHashes
and
Jun 04, 2020 20:51:17.142 [0x7efcbd2d5700] DEBUG - Completed: [192.168.0.199:63305] 500 POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxxzvbHzL (7 live) GZIP 80103ms 508 bytes (pipelined: 6)
12

Logs.zip (93.3 KB)

Woops, sorry about that, here they are.

14

Thanks so much! It turns out the DNS settings on the NAS had defaulted to some random (nonexistent) local IP address, and pointing them to a real DNS server did the trick.

15

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