Server Version#: 4.4.1.1086(2019/10/10)
Player Version#:1.16.3 (2019/10/24)
Hi,
For about one month PMS is not working anymore.
When I click the Plex-Button the “onboard plex client webapp” only says “Looking for Server…”.
I do not use DNS and the Webapp trys to reach the correct private IP-Address and Port, which should be used.
BR
Today, QNAP contacted me about this issue. They are experiencing it themselves with the version they repackage for App Center.
Have you:
Tried but receive:
192.168.1.112 refused to connect.
Try:
ERR_CONNECTION_REFUSED
Let’s see if it’s even responding:
curl 'http://127.0.0.1:32400/web'
I opend a QNAP-Case one week after I have seen this issue but they were not able to help me.
Maybe they found something out. 
Regarding your input:
Yes I already tried this, but it did’t change anything.
In a browser, browse to: http://<IP_OF_QNAP>:32400/identity
Is an xml returned, and if so, what does version says, and do it have an entry saying: claimed="1"
I don’t only have connection issues to connect to PMS form a client. It isn’t even possible for the QNAP-Webapp based client to connect to the PMS. I think there should not be a firewall which is able to block the connection. As far as I know it is an all in one application, which should be able to connect to the services of it self.
BR
Wow…What do you mean here?
It says:
MediaContainer size=“0” claimed=“0” machineIdentifier=“d433018f124d47258bf271f7a9defbaf40dd2311” version="1.16.3.1402-22929c8a2
I mean I do not think that it is not reachable to due the reason that DNS is not resolving properly.
curl ‘http://127.0.0.1:32400/web/index.html’
is returning:
======= ==
/==////== /==
/== /== /== ===== == ==
/======= /== ==///== //== ==
/==//// /== /======= //===
/== /== /==//// ==/==
/== /== //====== == //==
// // ///// // //
…
curl ‘http://127.0.0.1:32400/web/’
returns nothing
curl ‘http:// 127.0.0.1:32400/’
returns some content
Above means that your PMS is up and running, but not claimed
Then you need to setup your DNS in QNAP Control center first
What DNS servers are you currently using?
And recommend using Google here (8.8.8.8 and 8.8.4.4)
To test DNS, open an SSH session towards your QNAP, and in the console, type ping ping-test.org and see if it respond immediately
Also, is both your QNAP and your workstation using Private Address Space, as well as been on the same IP-Net?
Excuse my description about using DNS, what I tried to say was that the DNS resolution will not affect the PMS because of some bad entrys.
My whole home network is using DNS,
First address is resolving from an pi-hole
second is 8.8.8.8
I already tested only to use 8.8.8.8 before I created this thread but it did not change anything.
DNS is working on all devices in my network.
All of them are using pivate IP-Address but not all of them are in the same sub net( but this was no problem before).
Then you are faced with an issue, where sometimes the browser fails to detect a broadcast from the PMS about it been unclaimed.
(Could be due to firewall on your workstation, or browser plugins)
To work around this, and claim your PMS, go here:
Download the https://github.com/ukdtom/ClaimIt/releases/download/V1.1.0.0/claimpms.sh and copy to your QNAP.
Then run it using SSH, and remember to enter 127.0.0.1 when asked for an IP address
Workstation claiming PMS, must be on the same subnet, unless you go my way with the script
Thank you very much for your information and the script.
But it was not necessary to execute you script i tried to use BrowserStation from Qnap App Center which made an interaction with PMS possible again.
BR 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
