Cannot claim server after PMS update

Plex Media Server
1

Server Version#:1.22.0.4136
Player Version#:NA

Hello. PMS recently updated to 1.22.0.4136 and since then I have been unable to claim the server. Prior to that I have been running PMS on this computer for a few years without issue or any changes other than PMS auto updates.

I have tried doing a full uninstall/delete folders/clear registry as following this article and the issue persists. If I open 127.0.0.1:32400/web or localhost:32400/web from the PC running the server I can see the server listed but when I try to claim the server the wheel spins for a minute and nothing happens. The server version also shows “Something went wrong. Please install manually” after the version number. I have tried a full uninstall and reinstall and that error also persists.

I have tried searching through similar issues and I have tried the following

  • I updated the DNS on both my router and server PC to 8.8.8.8 / 8.8.4.4.
  • From the server PC I am able to ping “app.plex.tv” and the packets show as sent and received with an average of 21ms time.
  • Windows firewall shows all Plex software as being allowed through the firewall

Not sure what to poke at next.

Logs are attached.

Thanks!

Plex Media Server Logs_2021-03-04_11-58-11.zip (161.0 KB)

2

Verify that your hosts file is clean.

Disable any VPN software. Some may even require you to uninstall it.

When trying to claim the server, use either an "incognito bowser tab, or disable browser add-ins. (particularly those add-ins which manipulate web site content)

3

Thanks for the quick reply. I checked the hosts file and it does not contain anything aside from the default comments. I also tried connecting using an incognito browser tab from chrome which has no add-ons and I get the same issue. There is not any VPN software running on the server.

I did notice that there was a new version of PMS out there (1.22.0.4145) and tried installing that but still seem to have the same issue.

Thanks!

4

Try doing it this way: How To Windows · ukdtom/ClaimIt Wiki · GitHub
It prints some insightful status and error messages while it’s doing its thing.

5

Here is the error I get with ClaimIt 1.1.0.0 running on the PC that is running PMS

I tried both 127.0.0.1 and the IP for the server and both return the same error.

Error

Thanks!

7

Please try the version mentioned in this issue, and also please report back, so I know if it’s working or not:

8

I tried the version mentioned in that post. I got a different error this time.

Error2

I took a look at the steps for Error 500 on github and this is a clean install, no changes have been made to the preferences.xml file. I tried the ping test and there were no issues there. My DNS on the router and PC are both set as 8.8.8.8 / 8.8.4.4.

Thanks!

9

Error 500 is an internal PMS error code, so what’s in the PMS logs?

10

Here you go

Plex Media Server Logs_2021-03-07_08-17-41.zip (265.4 KB)

11

According to your logs, there’s a lot of timeout errors

Mar 06, 2021 10:15:52.442 [15768] DEBUG - HTTP requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxsDjrSd
Mar 06, 2021 10:16:05.573 [15768] ERROR - Error issuing curl_easy_perform(handle): 28
Mar 06, 2021 10:16:05.573 [15768] DEBUG - HTTP simulating 408 after curl timeout
Mar 06, 2021 10:16:05.573 [15768] DEBUG - MyPlex: Did token exchange for claim (returnCode: 408)

So it seems like comm. towards plex.tv isn’t working properly

Are you perhaps running some kind of AntiVira solution, that inspect http trafic?

And can you from the box browse towards plex.tv?

12

That computer is just running windows defender. I am able to navigate to plex.tv from that computer without issue.

I threw in the towel and did a clean windows install on the server and I am now able to connect to plex without issue from both the server PC and a different PC.

Thanks for the help!

1 Like
13

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