Can't claim server

Plex Media Server
1

Server Version#: 1.32.6.7468 on Debian Linux
Player Version#: Any

I had to restart my server on friday, and after that my server “disappeared”. I couldn’t reach it at all. Among other things, I tried removing it from authorized devices and connecting via ssh to localhost interface - then I could see my server, and all content, but it had a status of needing to be claimed.

If I do that, the interface either does nothing - just refreshes after a login - or it waits awhile, and then tells me I am not authorized to access, and the server “disappears” again, but is added back to authorized devices.

I have tried a ton of suggestions and help articles, including changing DNS and doing a complete fresh install - but the issue persist. I don’t see anything on the status page, about claiming servers being down, am I the only one with these issues?

2

When turning on debug, I see things like

Sep 17, 2023 17:39:28.956 [140469797968696] ERROR - [Req#71/ViewStateSync] MyPlex: Error 403 requesting XML from: https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
Sep 17, 2023 17:39:28.956 [140469797968696] DEBUG - [Req#71/ViewStateSync] No user tokens found; stopping
...
Sep 17, 2023 17:47:37.720 [140469814770488] ERROR - MyPlex: Error 403 requesting XML from: https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx
Sep 17, 2023 17:47:37.720 [140469823208248] ERROR - MyPlex: Couldn't get list of access tokens from myPlex.

I don’t know if thats related

3

@VenomousPizza

Can you please provide the DEBUG logs which capture this?

Can’t tell what’s happening from just a couple line excerpt other than it can’t complete ViewStateSync

4

Ehm, yeah - but I see that the log also show my email address … soo, I’d rather not leak that?

5

@ChuckPa I have redacted my email, but here it is
Plex Media Server.log (138.4 KB)

6

I don’t know if this is your environment or PMS 1.32.6 failure. I suspect 1.32.6

Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: Entity: line 12:\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: parser\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: error :\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: EntityRef: expecting ';'\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML:                                           ^\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: Entity: line 27:\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: parser\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: error :\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: Specification mandates value for attribute crossorigin\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML: <link rel="preconnect dns-prefetch" href="https://fonts.gstatic.com" crossorigin\00
Sep 17, 2023 19:07:52.185 [139654082865976] ERROR - [MediaProviderManager] XML:

Please also do yourself the favor of dumping 1.32.6.7468. It has been rescinded.

PMS 1.32.5.7349 is again Public.

7

@ChuckPa Same result.
Plex Media Server.log (136.1 KB)

8

I just moved the whole thing to a machine at home, and it started up as claimed right away - So I am guessing you guys didn’t wait with until next month, and have already blocked Hetzner - good to know!

9

Is that what’s happening?

:roll_eyes:

I will go poke someone.

11

@ChuckPa I can’t find any other explanation. This is really poor handling of an already bad decision, on your guys part.

12

@VenomousPizza

I got feedback from the team.

There was indeed an error in the plex.tv software.
They are fixing it now.

13

Same problem here with hetzner server, I thought the ban was only next month.

14

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