Plex on VPS stuck on “Not Authorized”

Plex Media Server
1

Server Version#: v.1.43.0.10492-121068a07
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

Hi everyone,

I’m trying to set up Plex Media Server on a Windows VPS (Provider: Wealth Proxies) , but I keep running into issues with authorization and the web interface not loading properly.

Here’s what’s happening:

  • When I open http://127.0.0.1:32400/web, I either get:

    • “Not authorized”, or

    • A blank page that just keeps spinning

    • When I log in and want to connect the media serve software, it instructs me to download it again

What I’ve tried so far:

  • Installed Plex Media Server on the VPS (Windows)

  • Generated claim tokens from https://plex.tv/claim

  • Started Plex using Command Prompt with the claim token:

    set PLEX_CLAIM=claim-XXXX
"C:\Program Files\Plex\Plex Media Server\Plex Media Server.exe"

  • Made sure to:

    • Stop all Plex processes before starting with a new token

    • Use a fresh token (within expiration time)

  • Deleted the config folder:

    C:\Users\Administrator\AppData\Local\Plex Media Server

  • Cleared cache folders

  • Tried multiple browsers and incognito mode

  • Verified Plex is listening on port 32400 using netstat

  • Confirmed firewall allows inbound connections

  • Verified the VPS public IP matches what Plex sees

Network behavior:

  • Test-NetConnection to port 32400 succeeds

  • Port 32400 shows as LISTENING

  • Accessing via VPS public IP loads Plex but shows “Not authorized”

Additional context:

  • I was able to install and run Plex successfully on my personal PC with no issues

  • The problem only happens on the VPS

  • At one point, the server seemed to connect to my home PC libraries, which was unexpected and confusing

What I need help with:

  • Why does the server remain “Not authorized” even when using a valid claim token?

  • Is my VPS compatible?

  • Is there something different about VPS environments that requires additional setup?

2

I’m not aware that the Windows version of PMS can use claim tokens. That is a Linux thing, AFAIK.

If they are just a Hetzner reseller, then it won’t work anyway.

3

Don’t run Plex server under an Admin user account. There is no need for it, and security is tighter if you use a dedicated restricted user account.
Admittedly, this is only really viable if you also run PMS as a Windows system service: PMS as a service

4

I’ll definitely move to a dedicated user and run Plex as a service once I get the server fully working.

I confirmed with the VPS provider, they are not a Hetzner reseller.

5

Is your public IP listed under the Hetzner scope? Even if they are not a reseller they may be renting IP space.

6

How can I find that out without asking them?

7

Did you follow the first link I dropped above?

8

When you log into the server go to https://whatismyipaddress.com/ and see what it shows

9

Yes I did try that method, when I opened the setup plex html, the website kept spinning and I believe it said initializing server. Sorry did this last night, so not sure about the exact wording. But it was not working.

10

It shows D Stream Group FZ LLC

11

Can I get a copy of your server logs?

12

Plex Media Server.log (142.5 KB) Here You go.

13

Normally we ask for the entire zip, but in this case I think we got lucky.

Mar 19, 2026 14:15:09.798 [11172] DEBUG - Network interfaces:
Mar 19, 2026 14:15:09.798 [11172] DEBUG -  * 13 VNet {D1CF5637-48B8-4F79-A874-761AB1B80F2C} (45.155.xxx.xx) (00-05-36-AF-F8-A4) (loopback: 0)

I censored the full public IP, but this is an unusual case. Most server sit on a RFC-1918 compliant subnet. Which is what Plex expects and requires to log into a server. It doesnt want someone randomly claiming a server over the internet in case the server accidentally gets unclaimed during an update or other situation.

Not sure what the best route forward here is.