500 on POST to /myplex/claim

This morning I had to reinstall Plex to my NAS in my instance the most up to date package from the Plex site is (Synology):

PlexMediaServer-1.23.0.4497-a1b1f3c10-x86_64_DSM6

I am attempting to claim my own server. I am signed in with my Plex account (lifetime pass). When I click on the claim server button the following request is made and throws a 500:

Request URL: http://<NAS IP ADDRESS>:32400/myplex/claim?token=claim-<TOKEN HERE>&X-Plex-Product=Plex%20Web&X-Plex-Version=4.55.1&X-Plex-Client-Identifier=ice8zwta33i64xtfnfj2lazq&X-Plex-Platform=Chrome&X-Plex-Platform-Version=90.0&X-Plex-Sync-Version=2&X-Plex-Features=external-media%2Cindirect-media&X-Plex-Model=bundled&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=2560x1240%2C2560x1440&X-Plex-Language=en Request Method: POST Status Code: 500 Internal Server Error Remote Address: <NAS IP ADDRRESS>:32400 Referrer Policy: strict-origin-when-cross-origin

Has anyone run into this before and fi so how did you get it to work?

After going through the steps listed above the 500 still occurs when making the POST to http://NAS_IP_ADDRESS:32400/myplex/claim

it’

It’s the request the server makes. when trying to claim. see first post. (assuming they blocked out address for privacy)

@Luchadeer is the computer/device you are using to claim it on the same local network (subnet) as the NAS

@BigWheel Yes my NAS is on the same local network. In this instance the plex server is on my NAS at 192.168.x.x and I am using a web browser on my PC that is also on 192.168.x.x.

I’m going to uninstall everything and try again from scratch.

May I ask if this was done in curl at the NAS shell prompt or some other means?
If using curl, what is the exact command line ?

(Remember RFC-1918 addresses may be safely shown)

@BigWheel and @trumpy81

Here are the results from my most recent attempt:

  • Signed out of everything: plext.tv, forums, phone, and Roku
  • Uninstalled Plex android app from phone
  • Uninstalled Plex amp from phone
  • Uninstalled Plex server from Synology NAS
  • Deleted all files from /Plex/
  • Restarted router
  • Installed PlexMediaServer-1.23.0.4497-a1b1f3c10-x86_64_DSM6.spk via manual install.
  • Verified that plex is running on the Synology NAS
  • Went to http://192.168.x.x:32400/web and signed in with my username:password
    [the following behavior occurs with both username:password / SSO auth]

After login I am taken to http://192.168.x.x:32400/web/index.html#!/setup/fe75df828359612e4c83a6859c30ee0e3442a4a8
and the brower hangs.
In the background I can see repeated requests to the following URLs that are erroring out:

http://127.0.0.1:32400/media/providers?X-Plex-Product=Plex%20Web&X-Plex-Version=4.55.1&X-Plex-Client-Identifier=<ID HERE>&X-Plex-Platform=Chrome&X-Plex-Platform-Version=90.0&X-Plex-Sync-Version=2&X-Plex-Features=external-media%2Cindirect-media&X-Plex-Model=bundled&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=2560x960%2C2560x1440&X-Plex-Language=en

And

http://127.0.0.1:32400/?X-Plex-Product=Plex%20Web&X-Plex-Version=4.55.1&X-Plex-Client-Identifier=<ID HERE>&X-Plex-Platform=Chrome&X-Plex-Platform-Version=90.0&X-Plex-Sync-Version=2&X-Plex-Features=external-media%2Cindirect-media&X-Plex-Model=bundled&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=2560x960%2C2560x1440&X-Plex-Language=en

Apologies there are no HTTP status-codes with these requests

If I refresh the browser I while it is in this state then I am taken to the “How Plex Works” and I appear to be authenticated.

On the “Server Setup” page I added a new name with “allow me to access my media outside my house” selected.

After clicking next on that screen an error is thrown stating that there was an issue claiming the server.

All subsequent attempts to claim are met with the same 500 error that was originally reported.

Logs.zip (103.3 KB)

@BigWheel / @trumpy81 logs from my most recent install.

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