Hi! I’m running Plex Media Server 1.43.5.11029-6bf8af3f0 on Windows 10.
My local server is running, but accessing http://127.0.0.1:32400/web always returns “Not authorized,” even after signing in again or using an incognito window.
What I’ve confirmed:
/identity returns HTTP 200 with claimed=“1”.
Local API requests to / and /library/sections return HTTP 200 using the stored Plex token.
Plex account API requests succeed, but my server is missing from /api/servers and /api/resources.
The logs show the device update returning HTTP 200, but server registration fails:
POST https://servers.plex.tv/servers.xml → HTTP 422
The log then reports registered :0 and the mapping state remains Unknown.
I also tried removing the Plex account credentials from the Windows registry and signing in again, but the problem persisted. I backed up the registry before making those changes.
What could cause the server registration to return HTTP 422 while authentication and local API requests succeed? How can I fix this without losing my server configuration?
Thanks!
Disable any VPN software while doing the following:
This worked perfectly, i followed all steps; i wish for your pillow to be always fresh, your beverages the right temperature and your food perfectly seasoned 
There is still something weird about your server. Is it connected directly to the Internet? it appears so.
(maybe you added it to the DMZ in the settings of your router)
That might be because of my Internet provider? They don’t give access to the router; i hope it doesn’t give me issues in the future!! I remember a few years ago i had to ask for a static IP address cause i was having issues with Plex
In light of that, I think you’ll have to revise the connection settings back to “public”.
Then grant Plex server permission to get contacted from the outside on port 32400, in the Windows firewall settings.
(only this one port!)
Google says this: https://www.google.com/search?q=allow+plex+server+through+the+windows+firewall
Staying at “private” would be a higher risk of getting attacked from the outside, because the Windows firewall is much less restrictive when in “private” mode.
