Deleted my server, recreated it. "Not authorized, You do not have access to this server."

I just built a brand new Plex server. Just to start off with a clean slate, I deleted my old server from authorized devices. I stopped/deleted the old pms-docker and config directory. I created a new pms-docker container. When I goto http://server:32400/web I keep getting, “Not authorized, You do not have access to this server.”

I looked in here: https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/

… but I don’t think it’s applicable because it’s just pms-docker (completely brand new instance) and I’m using a browser to try to access http://server:32400/web

I’ve tried:

  • Changing password and forcing all authorized devices to logout
  • Trying different claim numbers
  • Turned off 2FA
  • Dumped browser cache

Any pointers? I have a feeling something might be hosed on Plex’s authorization backend when I deleted my old server from authorized devices.

I figured it out. Grepped “setup” URL in debug logs. Reconfigured Docker to use host networking (instead of bridge).

PMS Plugin Logs/com.plexapp.system.log.2:2023-03-17 21:15:52,272 (blah) :  DEBUG (peerservice:214) - Ignoring blah because host != 127.0.0.1 (172.19.0.2)

My previous setup started off as host networking, then I moved to bridge networking.

I encountered the same error “Not authorized - You do not have access to this server”, after I migrated Plex from my Synology to QNAP today.

The root cause was because on Synology I used the 192.168.0.xxx, on QNAP 1288x I use the Thunderbolt network interface (169.254.x.x) to install the Plex, which is running under different network interface! And it seems this upsets the Plex logon authorization, which doesn’t seem to be happy with installing Plex server on multiple network domains.

To resolve this, I did this:

  • Uninstalled the plex server on my QNAP via the current Thunderbolt interface (169.254.x.x) logon

  • Reinstalled the plex server on my QNAP via the normal Ethernet interface (192.168.0.xxx) logon

  • Retried to connect the Plex server and it worked

It was a big hassle for me to DIY to investigate the issue, whilst there is no chance for me to open a support ticket to engage Plex to help, expect DIY effort by scrambling to scout the online forum.

I just purchased the Plex Pass, and straight away I had this problem and had to save myself by DIY effort, not a good experience from Day 1.

However the Plex works very well on my QNAP now. I hope it would not disappoint after this ordeal.

PS.: Just found the way to enable my Thunderbolt network interface access to the Plex server:
Need to go:
Settings > Network >

List of IP addresses and networks that are allowed without auth:
{put your IPs here with comma as delimiter}

Comma separated list of IP addresses or IP/netmask entries for networks that are allowed to access Plex Media Server without logging in. When the server is signed out and this value is set, only localhost and addresses on this list will be allowed.

Now, all sorted.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.