If your Plex server shows “not claiming to account” or the Claim Server button simply spins and does nothing, the fix is almost always to connect to Plex Web locally first, confirm you are signed into the correct account, and then clear out any blocked ports or old server entries before trying again. This guide is for anyone running Plex Media Server on a home PC, mini PC, NAS, or server box who cannot get a new or newly reinstalled server linked to their Plex account.

Key takeaways

  • ✓A Plex server fails to claim mainly because of blocked ports, firewall rules, or a stale authorised device entry
  • ✓Always open Plex Web using the server's local IP address before trying to claim it
  • ✓Removing an old or missing server from Authorized Devices in your Plex account often fixes claiming failures
  • ✓Wrong system date or time on the server machine can break the secure connection needed to claim
  • ✓NAS users generally need to claim the server from a separate device on the same network, not from the NAS itself

A Plex server not claiming properly is one of the more common setup headaches, and it almost never means the install is broken. It usually comes down to a network block, an outdated authorisation record, or trying to claim from the wrong device. Work through the steps below in order and you should have it sorted without needing to reinstall anything.

What you’ll need

  • A working Plex account and its login details
  • Plex Media Server installed and running on the target machine
  • The local IP address of the machine running Plex (found in your router’s device list or the server’s network settings)
  • Access to your router or firewall settings, in case ports need adjusting
  • Another device on the same network if you’re claiming a server running on a NAS or headless machine

Why a Plex server not claiming happens

Plex ties a server to your account through a secure handshake over the internet, so anything that interrupts that connection can cause the claim to fail. The usual culprits are a firewall blocking outbound traffic, a leftover “ghost” server already registered to your account under the same name, an incorrect system clock on the server machine, or simply trying to claim remotely instead of from the local network. Plex generally expects the claim to happen while you’re on the same network as the server, which trips up a lot of first-time NAS users in particular.

Step-by-step fix

  1. Find the local IP address of the machine running Plex Media Server, then open a browser on a device on the same network and go to a URL in the format http://server-local-ip:32400/web, for example http://192.168.1.25:32400/web. If you’re sitting at the actual server, http://localhost:32400/web or http://127.0.0.1:32400/web also works.
  2. Sign in with your Plex account when prompted, then look for a Claim Server button on the setup screen and select it.
  3. If the button spins and returns without claiming, check that your firewall allows outbound traffic on port 443 and that Plex’s own port, 32400, is reachable on your local network. On Linux servers this often means adding a rule to UFW or whatever firewall tool is running.
  4. Open the Plex account sign-in page in a separate browser tab, go to your account settings, and switch the Authorized Devices filter from “All” to “Server”. If you see an old or missing server listed under the same name you’re trying to claim, remove it. This won’t delete your library metadata or server configuration.
  5. Go back to the local Plex Web address and try the Claim Server button again. Removing the stale entry is often what unblocks a claim that previously just spun and failed.
  6. Check that the date and time on the server machine are correct and synced automatically. A clock that’s drifted out of sync can break the secure certificate check Plex relies on during claiming.
  7. Restart the Plex Media Server service or application, then reload the local Plex Web page and attempt the claim once more.
  8. If none of the above works, update Plex Media Server to the latest available version for your platform and repeat the process, since older builds occasionally have known claiming bugs that later updates resolve.

Claiming a server running on a NAS

If Plex is installed on a NAS such as a Synology, QNAP, or Asustor device, you typically cannot claim it from a browser on the NAS itself. Instead, open the NAS’s local IP address with the Plex port from another computer, phone, or tablet on the same network. The same rule applies to headless servers and mini PCs tucked away without a monitor, including small form-factor machines like a Ryzen 9 9950X3D mini PC running Plex as a dedicated media server, or a laptop such as an HP ZBook doubling as a home server. You simply need any second device on the local network to complete the claim, since remote claiming isn’t supported unless you’ve already set up a private tunnel such as a VPN back to your home network.

Tips and troubleshooting

  • Always attempt the first claim locally. Remote access via plex.tv only becomes reliable once the server is already claimed and properly configured.
  • If you’ve moved Plex to new hardware with a new local IP address, treat it like an unclaimed server and follow the Authorized Devices removal step above.
  • Double-check you’re signed into the same Plex account in both the local Plex Web session and at app.plex.tv. Mismatched accounts are a surprisingly common cause of failed claims.
  • If the server logs mention connection issues on port 443, confirm your router or ISP isn’t blocking outbound HTTPS traffic, and temporarily disable any VPN or proxy software that might be intercepting the connection.
  • For ongoing connection drops once the server is claimed, a dedicated look at troubleshooting Plex server connection timeouts covers follow-up fixes.

Frequently asked questions

Why does my Plex server say “not claiming to account”?

This usually means the secure handshake between your server and your Plex account is being blocked, often by a firewall, an outdated app version, or a leftover server entry already registered under your account. Working through the local-access and Authorized Devices steps above resolves most cases.

Can I claim a Plex server remotely?

Generally no. Plex expects the initial claim to happen while you’re connected to the same local network as the server, unless you’ve already established a private connection back to that network, such as a VPN. Try claiming from a device on your home network first.

Do I lose my libraries if I remove a server from Authorized Devices?

No. Removing a missing or duplicate server entry only clears its registration with your Plex account. Your media libraries, metadata, and server settings stay intact on the machine itself, and you can reclaim it under the same name.

What port does Plex use for claiming a server?

Plex Media Server primarily listens on port 32400 for local access, while the claim process itself also relies on outbound HTTPS traffic over port 443 to communicate with Plex’s servers. Both need to be reachable for claiming to succeed. See the official guide to opening Plex Web for more detail on accessing your server directly.