QNAP - Can't claim my server

Plex Media Server NAS & Devices
1

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

I’m starting to be at my wits end here with this QNAP Plex server.. I just bought the lifetime pass so I would really love not to give up on this…

I had this issue earlier, where my libraries vanished from my Plex server, but I just reinstalled Plex server on my QNAP and things continued working from there, albeit with the loss of my categories and such. For the longest time server ran with zero problems, until one day I get back home from work and the libraries seem to be vanished again. My thinking goes → ok I will just reinstall the server app just as I did earlier, but as I’m installing it I get encountered with this notification:

error1
error11416×717 40.4 KB

Error is in finnish but the statements are:

There was an error in claiming the server
There was an error in logging in

And as I go into settings and try to claim the server, the button just refreshes and nothing happens. Profile states that the server is unclaimed:

error2
error21091×341 47.4 KB

I’ve been reading the forums and other sources throughout the week and read about forcing the claim of the server through this manually injected token:

As I follow these directions through putty, I get this response:

error3
error31081×988 43.6 KB

Is there something I’m missing here? How can I manually reclaim my server? Can you direct me to some other sources of guidance here?

Here you can find logs:

Plex Media Server Logs_2025-11-02_19-40-27.zip (152.4 KB)

2

In your logs, I see:

Nov 02, 2025 19:39:41.406 [140430597237560] WARN - [HttpClient/HCl#23] HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxficate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name ‘plex.tv’)

and the screenshot above tells me you are not connecting to the Plex.tv backend.

Somehow you’re getting a regular web page (front end). It’s as if someone mapped plex.tv → www.plex.tv (which are two different entities. plex.tv is the backend operations system. www.plex.tv is the web server

3

Thanks for getting back to me so fast and on a sunday…

How can I force the connection to plex.tv -backend? What could cause this re-mapping of plex.tv?

4

@Wireframe

while we wait for Chuck, post the output you get from curl -v https://plex.tv

5 
curl -v https://plex.tv

* Host plex.tv:443 was resolved.
* IPv6: (none)
* IPv4: 3.248.163.211, 34.254.245.199, 54.76.243.238, 34.254.54.72
*   Trying 3.248.163.211:443...
* Connected to plex.tv (3.248.163.211) port 443
* ALPN: curl offers http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: none
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 / prime256v1 / rsaE                                                                                 ncryption
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.smatis.fr
*  start date: Dec 20 00:00:00 2024 GMT
*  expire date: Jan 18 23:59:59 2026 GMT
*  subjectAltName does not match plex.tv
* SSL: no alternative certificate subject name matches target host name 'plex.tv                                                                                 '
* Closing connection
* TLSv1.2 (OUT), TLS alert, close notify (256):
curl: (60) SSL: no alternative certificate subject name matches target host name                                                                                  'plex.tv'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
6

My router is Asus RT-AC88U, which the QNAP is connected to the internet through.

If it gives you any more relevant context.

7

@Wireframe
Well that’s not working for you. It’s connecting to smatis.fr which is a healthcare provider.

Check that you have good public nameservers set for you network interface like Cloudflare (1.1.1.1 and 1.0.0.1). Another good one is Quad9. I avoid Google.

The docs for QTS 5.2.x are here:

I’m not exactly sure whether QTS 5.2 configures the command line util, nslookup, to use the DNS servers you set in your Network Settings, but I think it uses what you have in your /etc/resolv.conf file, which on my system is 127.0.1.1 perhaps because I have a bonded network interface bond0 (2 NICs) rather than a single NIC, eth0. Anyway these commands use the default server and a specific server to let you see the different replies you might get.

# nslookup plex.tv

# nslookup plex.tv 1.1.1.1

As an example, I saw this on QTS 4.5.4.

# nslookup plex.tv 1.1.1.1
Server:		1.1.1.1
Address:	1.1.1.1#53

Non-authoritative answer:
Name:	plex.tv
Address: 34.238.225.186
Name:	plex.tv
Address: 44.210.41.33
Name:	plex.tv
Address: 35.172.142.61

Hopefully that’s an easy fix for you. Any idea why your DNS is acting strangely? VPN maybe? Do you live in France? ISP shenanigans?

I should also ask do you have a lot of good, recent .pem files in your /etc/ssl/certs directory? I think those are supplied by QTS App Store updates.

8

Apologies for the delay. One my busiest days off in a long time lol

Please run my script.

It has more detailed instructions w/ example for QNAP

Let’s see what happens.

9

Thank you both, I got it working by setting the DNS to 1.1.1.1

It was set to automatic by ISP so my best guess is the issues were caused by some ISP shenanigans. Good to know that it is best to set DNS manually!

1 Like