Unable to Claim Fresh Plex Server Installation - "Setup is not allowed for shared servers" Error

Plex Media Server
1

Hey all,

I’ve been banging my head against this for about a week now and could really use some insight or guidance. I’m trying to set up a Plex Media Server fresh on Ubuntu 24.04 LTS (kernel 6.8), but the server never seems to fully claim under my account. It just throws “Setup is not allowed for shared servers” or “Not authorized” errors in the web UI.

Here’s the rundown:

  • Plex Server Version: 1.42.2.10156-f737b826c

  • OS: Ubuntu 24.04.3 LTS minimal install

  • Client: Plex Web on Chromium/Linux, with 2FA on my Plex account (which I suspect might factor into this)

  • NAS mounted via CIFS, fully reachable and stable on /mnt/plex

  • Tried:

    • Completely purging Plex (apt remove --purge + /var/lib/plexmediaserver wiped) and reinstalling with official repo and updated signing keys

    • Clearing browser cache, using Incognito/private sessions

    • Removing all authorized devices and servers from my Plex account dashboard

    • Injecting claim tokens via /etc/default/plexmediaserver environment or manually running Plex as plex user with PLEX_CLAIM set

    • Waiting intervals of 10-15 mins between removals and reinstall attempts

Despite all that, the Plex Web UI still refuses a fresh claim and behaves as if this server is pre-claimed or shared, essentially blocking setup progress. Logs show no sign of token acceptance or claim processing.

I’ve double-checked the machine isn’t in my Plex account’s servers list, only devices for my web sessions. The UI prompt for expired credentials and 2FA hints there may be some session or account state messing with the claim process.

Has anyone run into a similar weird “ghost” registration or stale server state that won’t clear? I’m wondering if Plex Support has to manually unlink some machine identifiers or if there’s a hidden config I’m missing that ‘shares’ the server?

Any advice on how to break this persistent loop and claim the server cleanly? Feel free to ask for logs or configs — I’m happy to provide!

Thanks!

2

Plex Documentation → Installation and Basic Setup → Installation

Are you local to or remote from the server? Remote = on a different network, not geographical distance.

If remote, you’ll need to set up a SSH tunnel. See the On a Different Network section of the Installation document linked above.

You can also try the User Credential Reset utility, whether local or remote.

3

I am technically remote however I have full access from my desktop to the host.
But even if it was a remote access issue, wouldn’t using claim tokens rule that out?
I have completely uninstalled the plex server and reinstalled after purging the plex dir so I didn’t think that any configuration would persist.

4

I have also tried claim codes and confirmed that I have full outbound access to the internet and I’ve even created explicit rules to allow outbound access.
Wouldn’t that bypass any issues with a connection between my desktop and the host?

5

Not sure exactly what you’re doing with that.

Either use a SSH tunnel or use the User Credential Reset utility.

7

PMS does not use /etc/default/plexmediaserver since pre-Ubuntu 16 days.
Ubuntu 16 introduced systemd.

9

Quick question who is your host? See Not Allowed to use Hetzner

10

I must have been running off bad instructions then, I was able to get the server back online and registered under myself, but now I cannot share it out.

So, here’s some more info and an explanation of where I’m at now-
I am on a local home network. My desktop and network devices are on one vLAN and the NAS hosting the media and the server hosting plex are on their own vLAN.
I have direct access rules from my devices to these hosts, I have opened things up more with no change, and it was working fine before I reset my password and forgot all authorized devices (which started this whole thing because of the notification Plex sent having data exposed and advising to change passwords)

I went at it fresh this morning and uninstalled the plex application following plex documentation, reinstalled following plex documentation, and then followed the directions for the credential reset and that got it working.
However now I am having an issue where I cannot share out the server to my friends.
This could be something that needs a reboot or just more time to sync, but it is odd that I seem to have full control over the server but I cannot share it out.

image
image1699×649 57.2 KB

11

Please notice:

  1. Workstation/desktop on “VLAN A” (Subnet A)
  2. NAS with media on “VLAN B” (Subnet B)
  3. PMS running on “VLAN B” (Subnet B)

The fundamental fact they are on different subnets was the problem.
This is because broadcast packets do not cross subnet boundaries,.
PMS sees the request coming from a different subnet and says “NOPE, FOREIGN” .

The UserCredentialReset tool ignores ALL that.

As you ran it on the PMS host, it only cared about its IP address and Plex.tv.
When you gave it the claim token, It forwarded that to Plex.tv on your behalf.

Plex.tv authenticated the token and sent back the login info (your info).

The tool then took that information and wrote it into Preferences.xml for you

When PMS next started, it found all the credentials present and valid.
“Everybody happy” and off it went

12

I was able to invite friends once I rebooted the server and let is sit for a minute.

Thank you for the help, the credential reset coulda probably helped me when I first had issues then and I was running on old information.