Cannot claim server - shows as PlexMediaServer 1.1 in Authorized Devices

Plex Media Server
,
1

Server Version#: 1.43.0.10492-121068a07 (linuxserver docker)
Player Version#: Plex Web (Chrome on macOS)

I have a Plex Media Server running in Docker on Ubuntu.

Current behavior:

  • Server is reachable locally at http://192.168.1.22:32400/web

  • Setup completes locally and libraries are visible

  • Claim/sign-in either fails or appears to succeed briefly

  • Server does NOT show correctly in Plex Web

  • In Authorized Devices it appears as:
    “PlexMediaServer” version “1.1”
    instead of the actual server name/version

Troubleshooting already performed:

  • Multiple fresh claim tokens

  • Reset Preferences.xml

  • Ran UserCredentialReset utility with correct Docker path

  • Cleared browser sessions and cookies

  • Removed devices from Authorized Devices

  • Restarted container multiple times

The server consistently comes back as the incorrect generic identity.

This appears similar to the “ghost/soft-deleted server” issue described here:
https://forums.plex.tv/t/local-plex-server-stuck-in-shared-server-state-cannot-be-claimed-or-made-visible/935086

Can someone from Plex reset or remove the backend server identity tied to this account so it can be claimed cleanly?

2

Can you post a copy of your server logs to see if anything else may be at fault?

3

Sorry, are you only a regular user? I’m looking for the plex team.

4

If you want to be a pompous PITA, Ill forgo providing any assistance and forwarding the results to the relevant staff. Instead of being a Karen take the help when offered.

5

Oh, no, I’m just concerned about what might be in those logs. I’m worried their might be a token or something exposed.

6

The only thing exposed in logs is going to be your email and your public IP address. Tokens or anything account private will censored. The logs are designed for public posting and troubleshooting.

7

I would start with a couple of points. I would set your docker to host mode, and turn off/disable the other network cards in the container.

Then I would look at your network settings, as I am seeing Allowed Network (Subnet) in your logs suggesting you have non-default network configurations.

8

Thank you, I’ll try those. Have you ever seen an authorized device show up like the attached picture? That is what I get when I use the UserCredentialReset utility. The utility runs fine.

Screenshot 2026-04-07 at 6.28.30 PM
Screenshot 2026-04-07 at 6.28.30 PM1072×606 33.4 KB

9

@BigWheel any chance you can take a look at the backend? logs dont show anything glaring.

10

Are there any additional steps I can take while we are waiting? I’ve tried everything I can find.

11

@OttoKerner any chance you can take a look at the back end?

12

Thank you for all the help. I figured it out.

It was Tailscale. One of my servers containers was trying to use Tailscale as it’s NIC. I stopped Tailscale, started Plex, authorized perfectly. I set to advertise my IP in docker compose hoping it will avoid this in the future (it was trying to use 100.100.100.100).

This problem was driving me nuts. Hopefully it helps someone else in the future.