Can not claim server suddenly after having no problem for over a year

Plex Media Server
,
1

Server Version#:Version 4.147.1
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

Running Plex on Terramaster with no problem for a year, suddenly last week I am unable to access the server. Get a message to claim my server, when I try nothing happens the button is still asking me to claim. Have uninstalled and reinstall a number of times with no luck. nothing is working.

Plex Media Server Logs_2025-08-13_21-12-39.zip (445.2 KB)

Plex Media Server Logs_2025-08-14_06-15-58.zip (454.1 KB)

Plex Media Server Logs_2025-08-14_08-38-51.zip (532.6 KB)

2

I would start with a copy of your server logs, and if you havent tried GitHub - ChuckPa/UserCredentialReset: User Credential Reset utility for Plex I would suggest giving it a try.

3

Hi Dbirch

Thank you for your solution, I tried it but seeing the technical steps needed to follow rather than a click or delete solution has put me off trying since I am not too techinal when it comes to amending codes. Is there any other options I can try.

4

You can try and contact your ISP and ask them why they are blocking Plex domains.

There is nothing illegal about Plex and all the streaming offers are perfectly licensed. Please tell them this, if they claim that plex is illegal.
It would be very helpful to find out the source of these allegations. This could help other users in your country or on this particular ISP as well.

5

Hi

I don’t believe it is blocked, I believe it is Plex software itsself locking onto my previous IP and not releaseing it, now I am unable to link my new IP because the old one is tied to the email/account. No idea how to get it released, or to get Plex to reset the IP

6

Plex doesnt lock anything to your IP. My next suggestion would be to restart plex wait 90 seconds and get a copy of your server logs.

Could be DNS, LAN settings or a dozen other things.

7

Hi

I thought that Plex locks the server IP to an account? I have uploaded my server logs hopefully this will help track down the problem and provide a solution. Thank you so much for your time.

8

Nope, when the plex server starts it reaches out to Plex and tells Plex what your Public IP is so that clients can connect.

So you disabled debug logging which means most of the useful stuff in your logs is not there.

However I think you have a network issue:
Aug 13, 2025 21:10:16.466 [140508127415096] WARN - [HttpClient/HCl#24f] HTTP error requesting GET ``https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxe`` host name) (Could not resolve host: plex.tv)

Your NAS cant resolve plex.tv. Please check its IP/DNS settings and re-enable debug logging.

9

Hi

I have just uploaded the extended version of the log. Thanks

10

At a minimum, restart Plex Media Server, wait two minutes, and recollect the logs and upload them.

Optimally, restart the NAS completely, wait enough time for it to start all its services, and then collect and upload the logs.

The logs you’ve provided suggest that PMS hasn’t been restarted, at the earliest, since 8/12 at around 8 PM.

11

Hi

Okay, I have rebooted my NAS then enable Plex and got a new log. Good luck and thank you for looking into this.

12

Thanks for the updated logs. Can you try disabling the second interface on your NAS, since it is apparently not being used? (And reboot and test again.)

Aug 14, 2025 08:35:40.108 [140448336878224] DEBUG - Detected primary interface: 0.0.0.0
Aug 14, 2025 08:35:40.108 [140448336878224] DEBUG - Network interfaces:
Aug 14, 2025 08:35:40.108 [140448189139768] DEBUG - Perfect cache hit, we don't need to start [com.plexapp.agents.localmedia] yet.
Aug 14, 2025 08:35:40.108 [140448336878224] DEBUG -  * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Aug 14, 2025 08:35:40.108 [140448336878224] DEBUG -  * 10 eth0 (192.168.1.21) (6C-BF-B5-03-E4-35) (loopback: 0)
Aug 14, 2025 08:35:40.108 [140448336878224] DEBUG -  * 11 eth1 (169.254.202.201) (6C-BF-B5-03-E4-99) (loopback: 0)

The second interface is being assigned a link-local address (169.254.0.0/16). It may be that the system is treating that as the default route, preventing a connection to plex.tv (which is prevalent in the logs). The latest logs don’t appear to show any DNS host lookup errors.

13

Disconnected the second ethernet (it was one I always used to access the NAS directly from the computer), rebooted the PC and logged into Plex again after logging out. Still no luck, unable to claim the server.

14

Can you provide updated logs, please?

15

Great news, finally sorted, turns out it was a NAS problem so had to reinitial and now I am back. Thank you so much for your time and help.

16

Hello, I have exactly the same issue since today. Could you please give more details on how you solved it?

17

Am not sure if it will work for you, but my problem was caused by my Terramaster NAS, the latest update for the NAS must have messed up the settings so I re-initialised the NAS and that sorted out the problem.

18

Hello, I’m also using a Terramaster NAS and I think I have this issue since the upgrade to TOS 6.0.770. I think solved the issue by forcing my docker container to use a public DNS (cloudflare) instead of the host DNS.

19

Good to get confirmation I was not the only one affected by the latest TNAS upgrade. I did not use a docker, I just ran Jellyfin as standard on the tv and pc but direct the directories to the NAS. That works for me. Hope your solution works over the long term. So far mine is fine after I reinitialised the NAS.