I am having this exact same issue, I haven’t found anything in the logs that points to the server losing connection, and I don’t even see anything in the logs when I reclaim the server either, so I’m not sure what’s missing here. I posted 4 days ago ( Plex Server Keeps getting unlinked ) but haven’t heard anything.
Your server is making so many requests, Plex.tv is now throttling you.
It’s unclear if the server is claimed or not so let’s (re)claim it anyway
Aug 23, 2025 20:35:27.217 [139815010605880] DEBUG - [Notify] Now watching "/volume1/video/watched/film/She's Out of My League (2010) DVDRip XviD-MAXSPEED"
Aug 23, 2025 20:35:27.217 [139815070362424] DEBUG - [HttpClient/HCl#11] HTTP/1.1 (0.1s) 422 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx (reused)
Aug 23, 2025 20:35:27.217 [139815003986744] DEBUG - MyPlex: Published Mapping State response was 422
Aug 23, 2025 20:35:27.217 [139815003986744] DEBUG - MyPlex: Got response for f046b42ec0297c6d024531d3dd6ac5a1e172bb5b ~ registered :0
Aug 23, 2025 20:35:27.217 [139815003986744] DEBUG - MyPlex: updating mapped state - current state: 'Unknown'
Aug 23, 2025 20:35:27.217 [139815003986744] DEBUG - MyPlex: mapping state set to 'Mapped - Publishing'.
Aug 23, 2025 20:35:27.217 [139815003986744] WARN - MyPlex: attempted a reachability check but we're not yet online.
To remedy
Stop PMS
Uninstall the SPK
Reinstall the same SPK – HOWEVER –
– Use the Plex Claim Token option
– Click the hyperlink to get the token from Plex.tv
– Copy into your browser
– Paste it in the box on the Package Center installation page.
– Click NEXT NEXT DONE
After it starts, wait 30 seconds (to prevent DB corruption)
STOP PMS
Wait 30-60 minutes for Plex.tv to remove the throttle.
Start PMS normally.
However I also see a 422 in my logs, mine is deployed via k3s/apps on Truenas SCALE, I will check my folder permissions though and follow those same instructions.
I think I have solved my problem, but only time will tell I had to ensure that plex could see my server securely and that meant setting up a certificate for it. There are some instruction on the web about how to do this, but it took some fiddling as certain things were missing and website they link to have changed so not obvious which packages to download ect.
If it all works, will report back here and might do a set of instruction that are more idiot proof than those I found on the web.
This is not correct (from what your server reports to Plex.tv:
‘https’ is not a hostname / domain name.
Local Addresses: 192.168.1.32, https
I found two references to the server ( by name ) on Plex.tv.
I removed the old one which had not been seen in some time.
Regarding seeing your servers securely,
Plex/web will report it cannot connect securely when it can’t connect at all.
It’s a red herring. It doesn’t know if it’s unable to connect (can ping) or simply can’t get HTTPS to sync up. I’ve asked for the error message to be changed but it’s never been.
You’ll get that message if PMS isn’t running or isn’t claimed (which has nothing to do with being secure or not.
When Plex brokers the connection for you (Remote Access & Sharing control) then the connection is always secure.
The only requirements on your part are
Make certain port 32400 (on the PMS server itself) is open
Make certain the external port is open and forwarded to port 32400 of your Plex server (modem routers often use “Virtual Server” or similar features to set this up)