My server as been working fine from several years without any issue, and suddenly last week I lost access to its contains. After some failed tests I have decided to reinstall it from scratch, and now I’m not able to claim my server. I’ve tried the methods described on the forum, direct and 3rd party, and the result is always the same, it ends up with the messages bellow.
May 10, 2024 17:12:17.092 [140448209476408] WARN - [HttpClient/HCl#4ff] HTTP error requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxNDHyii (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name ‘plex.tv’)
May 10, 2024 17:12:17.092 [140448181263160] DEBUG - [Req#15e2] MyPlex: Did token exchange for claim (returnCode: -60)
May 10, 2024 17:12:17.093 [140448181263160] DEBUG - [Req#15e2] MyPlex: Got a token poked, let’s act on it.
Hi, thanks for your quick reply.
I’m not aware of any own certificate or proxy assign to my Qnap, at least I never issued one… so I believe I dont. The only thing there a have, but since the beginning, is the myqnapcloud DDNS.
My Plex installation is directly on the NAS, not in a container, and I’ve already have performed a restart on the router.
I have the exact same problem with same logs since recently.
I tried to change DNS.
I tried to update time.
I tried to claim through SSL.
Rebooted server and box.
Anyone can help with that ?
I finally solved my problem after hours of searching by disabling ipv6 in qnap network settings. I’ve never touched those settings, don’t know what changed in between.
I hope it will help.
I tried your approach and disabled the IP6 in my Qnap, and I couldn’t believe that it worked to me too. I’ve finally claimed my server from the settings without any issue.
Thank you @yodu84, I was totally lost and you saved my day.
I had marked the IP6 disabling as a solution, but in fact it is not. It seems that network issues are the cause of it, and disabling the IP6 temporally fix the problem, but it returns to “this server is unclaimed” with the same log messages.
Enabling and disabling the the IP6, temporary permits that the server can be claimed with everything working fine, but minutes later it fallback to the same issue.
Edit: The temporary workaround is not only enabling/disabling the IPV6, in fact is the change it self. If we are with IPV6, disabling it works for a time. But then when it stops working again, just enabling the IPV6 again make it work dough.
