Unable to claim server; HTTP errors in logs

Plex Media Server
,
1

Server Version#: 1.41.3.9314
Player Version#: N/A
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I am using the official PMS container from the Community Applications. Yesterday, I opened my plex app and noticed my library wasn’t available. I followed the instructions to reclaim my server (including removing the fields from Preferences.xml), but the Reclaim Server button does nothing. The PlexOnlineToken field gets added back as empty (PlexOnlineToken=“”) after each attempt. I have tried fully reinstalling PMS with a completely new config and I am still running into the same issue. Interestingly, Tautulli is also unable to log into Plex, and is giving me errors in those logs as well. I’ve attached them in case those give more helpful information.

It seems to me that my server suddenly lost the ability to authenticate with Plex’s servers, but I hadn’t changed any part of my Unraid server’s configuration, and same with Plex.

Plex Media Server Logs_2025-01-22_16-59-43.zip (2.4 MB)
tautulli_logs.tar.gz (2.4 MB)

Errors from PMS Log:
WARN - [HttpClient/HCl#1e] HTTP error requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxficate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name ‘plex.tv’)

ERROR - [Req#23e] HTTP -60 downloading url https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=8&distribution=debian&version=1.41.3.9314-a0bfb8370

INFO - [Req#23e] AutoUpdate: error getting data from plex.tv

2

When you get
SSL: no alternative certificate subject name matches target host name ‘plex.tv’
this tells us that there’s another certificate involved and a FQDN got into the communication.

Do you have your own certificate attached to the host?

3

Thank you for the response. I don’t believe I’ve issued any conflicting certificates, but I’m not quite familiar. I did recently upgrade to Unraid 7.0 but that wasn’t at the same time that I noticed the issues with Plex. Do you know how I can check?

4

If you open a terminal window on the host

hostname

If it returns a full host.domain.name reply then that’s what’s messing up PMS.

If you get into the container shell and get a similar reply to the same command then it’s happening in the container.

It’s ok to get into the container (or host shell) and see just a hostname (like this)

[chuck@lizum Season 02.2010]$ lxc exec wirepod bash
root@wirepod:~# hostname
wirepod
root@wirepod:~#
5

I opened a shell for both Unraid and the PMS docker container and they returned simply hostname with no domain or anything attached. Is there something else that may be causing the issue?

6

Another thing I’ve tried:

  • Stopped PMS, removed the PlexOnline* pairs from Preferences.xml, saved, started PMS
  • Retrieved a claim code, and used it in the following command in the Unraid shell:
curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=PASTE_TOKEN_HERE'

I also tried the server’s 192.168.x.x IP address in place of the 127.0.0.1 with no luck, and I also tried both IP options inside of the docker shell as well. All four gave me the following error message:

<html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html>

I’ve tried to do a completely fresh install of the docker container with an empty config folder and was still experiencing the same issues.

7

When you did the CURL action,

had you previously cleared out the USERNAME, TOKEN, EMAIL, and HOME fields ?

A 500 error on a fresh server means a host problem or container instantiation problem.

8

It’s a DNS issue. Change your DNS to Cloudflare 1.1.1.1 or Google 8.8.8.8.

1 Like
9

Thank you so much!! This fixed my issue! For those who are reading this in the future - I edited my PMS container’s docker template. Toggle on Advanced View, and in the Extra Parameters, I added “–dns 1.1.1.1” (without the quotation marks).

Would you mind explaining why this DNS issue might’ve suddenly cropped up? I’d like to understand what went wrong so I know for the future. Again, thank you! And thank you @ChuckPa as well, I appreciate your help.

10

Your default DNS (probably your ISP) isn’t updating their DNS record for plex.tv to point to the correct IP address. When you tried to connected to plex.tv it sent you to a different IP address that is not owned by Plex and doesn’t match the security certificate. The errors you saw means you were correctly being protected from having your internet traffic intercepted by another party.

11

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