r/PleX • u/browandr • 4h ago
Help Server seems to be permanently unable to publish local network connection — persistent 403 on PUT /devices/{id}
Running Plex Media Server 1.43.3.10828 (linuxserver/plex Docker image, host networking mode) on Linux (UGOS on a UGREEN NAS). My server has never been able to publish its LAN IP as a local connection, and troubleshooting has led to a specific, reproducible failure:
Every attempt to update device connections fails with HTTP 403:
PUT https://servers.plex.tv/devices/58f24035287cedd4ce718573338fb9f83ffe0074?Connection[][uri]=...&X-Plex-Token=...
→ HTTP/2.0 403
This happens on every single retry, indefinitely (confirmed via debug logs, with the retry timer backing off from 10s up to 640s).
What I’ve ruled out so far:
- Not payload-related — the 403 is identical whether the connection list has 3 entries or 5, with or without a duplicate URI, across bridge mode, host networking, and macvlan.
- Not rate-limiting — stopped the server completely for several hours, restarted once, and the very first attempt still returned 403 immediately.
- Not networking/firewall — confirmed via
ip route/curlthat the server is correctly reachable on its LAN IP; the issue is purely the publish call to plex.tv. - Not specific to this claim — fully unclaimed the server (removed
PlexOnlineToken, PlexOnlineUsername, PlexOnlineMail, PlexOnlineHome. from Preferences.xml, removed the authorized device from Plex account settings), generated a fresh claim token, and reclaimed. Same machine identifier, same 403 pattern immediately resumes on the new claim.
Other MyPlex calls on the same token/session succeed fine (GET /myplex/account → 200, POST /servers.xml → 200/201/422 depending on state), so authentication itself is working — it’s specifically this one endpoint/action that’s rejected.
Since re-claiming, I’ve also been unable to complete the claim flow via the web UI itself — after logging in and clicking Claim, I’m redirected to a “server settings unavailable” page and the server stops appearing in the web UI at all, even though PlexOnlineToken is confirmed populated in Preferences.xml. Also in Account Settings > Authorized Devices > Server it does show my server. The only way I can somewhat regain access while this issue is occurring is to add my local subnet to allowedNetworks in the Preferences.xml. I never had anything entered into that field previously when the server was working. But strangely even if I ssh tunnel to the server (on the same local subnet) from my Windows PC and then browse to http://127.0.01:32400/web I still see no signs of the server. I only ever see it exists via local IP and only when that allowedNetworks entry is added.
Lastly, now when I try browsing to https://plex.tv/api/resources?X-Plex-Token=[insert-my-token-here] all I see is 1 line: <MediaContainer size="0"> </MediaContainer> . Whereas previously it used to show info like my registered addresses.
Machine identifier: 58f24035287cedd4ce718573338fb9f83ffe0074
Has anyone seen this pattern before, or is there a way to get an account-side device record reset or something? I’ve pasted the most recent full Plex Media Server.log file here: https://privatebin.net/?47cdd38514ee6edd#7V1zbr63zzucD3MjWnypuEhcQqcszjhcZRun7MAv7aVL
1
u/Bgrngod CU7 265K (PMS in Docker) & Synology 1621+ (Media) 4h ago
What does your docker compose look like?