OK, my parents can no longer connect becuase “your server does not allow secure connections”.
…I am temporarily going back to DHCP as then I can at least keep my parents occupied until I understand what the problem is. …easy to do, just plugging into my other QNAP L:AN port…
[edit:] this is probably me no re-assigning the port-for3warding on my router, so will reset that and try again (when my parents have finished watching their movie).
OK, parents’ TV requirements satisfied and back on Static IP with port forwarding now set to that new static IP (can’t believe I forgot to do that before but hey, ho).
So remote access to Plex is now OK and also https://app.plex.tv/desktop is now OK.
The only 2 things that aren’t working are accessing the QNAP’s admin page over https (http is OK) and also accessing it via it’s name over http (in lieu of its IP address). The server is named correctly and I can see it named correctly over SMB. …both of these things are minor if everything else works though.
edit:
Here are the WARN and ERROR for the 1st 30 mins after restarting everything (QNAP, router, my Mac after setting port forwarding). I cannot see anything regarding web hooks anymore so hopefully that is now addressed.
Plex Media Server.log (666.9 KB)
errors are:
~/Downloads/Plex Media Server.log:514: Aug 02, 2020 20:45:51.917 [0x7f3d79cd7700] ERROR - downloadContainer: expected MediaContainer element, found html
~/Downloads/Plex Media Server.log:524: Aug 02, 2020 20:45:51.920 [0x7f3d79cd7700] ERROR - downloadContainer: expected MediaContainer element, found html
~/Downloads/Plex Media Server.log:538: Aug 02, 2020 20:45:51.945 [0x7f3d9052b700] ERROR - downloadContainer: expected MediaContainer element, found html
~/Downloads/Plex Media Server.log:548: Aug 02, 2020 20:45:52.001 [0x7f3d9052b700] ERROR - downloadContainer: expected MediaContainer element, found html
~/Downloads/Plex Media Server.log:644: Aug 02, 2020 20:45:52.561 [0x7f3d7940d700] ERROR - Unknown metadata type:
~/Downloads/Plex Media Server.log:865: Aug 02, 2020 20:45:53.064 [0x7f3d799e9700] ERROR - downloadContainer: expected MediaContainer element, found html
~/Downloads/Plex Media Server.log:877: Aug 02, 2020 20:45:53.066 [0x7f3d799e9700] ERROR - downloadContainer: expected MediaContainer element, found html
~/Downloads/Plex Media Server.log:1051: Aug 02, 2020 20:45:53.373 [0x7f3d796fb700] ERROR - downloadContainer: expected MediaContainer element, found html
~/Downloads/Plex Media Server.log:1489: Aug 02, 2020 20:45:56.912 [0x7f3d78e31700] ERROR - Error issuing curl_easy_perform(handle): 28
~/Downloads/Plex Media Server.log:1491: Aug 02, 2020 20:45:56.912 [0x7f3d7911f700] ERROR - Error issuing curl_easy_perform(handle): 28
~/Downloads/Plex Media Server.log:1493: Aug 02, 2020 20:45:56.912 [0x7f3d78b43700] ERROR - Error issuing curl_easy_perform(handle): 28
~/Downloads/Plex Media Server.log:1495: Aug 02, 2020 20:45:56.913 [0x7f3d78567700] ERROR - Error issuing curl_easy_perform(handle): 28
~/Downloads/Plex Media Server.log:1505: Aug 02, 2020 20:46:01.912 [0x7f3d91d1c700] ERROR - Error issuing curl_easy_perform(handle): 3
~/Downloads/Plex Media Server.log:1509: Aug 02, 2020 20:46:02.219 [0x7f3d91d1c700] ERROR - Unknown metadata type:
WARN:
~/Downloads/Plex Media Server.log:311: Aug 02, 2020 20:45:41.972 [0x7f3d9384a700] WARN - MyPlex: attempted a reachability check but we're not yet mapped.
~/Downloads/Plex Media Server.log:374: Aug 02, 2020 20:45:45.694 [0x7f3d93b38700] WARN - NAT: PMP, got an error: Not Supported by gateway.
~/Downloads/Plex Media Server.log:515: Aug 02, 2020 20:45:51.917 [0x7f3d79cd7700] WARN - Subscription: No container available for /tv.plex.providers.epg.xmltv:38/metadata/tv%2Eplex%2Exmltv%3A%2F%2Fshow%2FFirst%2520Wave
~/Downloads/Plex Media Server.log:525: Aug 02, 2020 20:45:51.920 [0x7f3d79cd7700] WARN - Subscription: No container available for /tv.plex.providers.epg.xmltv:38/metadata/tv%2Eplex%2Exmltv%3A%2F%2Fshow%2FStar%2520Trek%253A%2520Voyager
~/Downloads/Plex Media Server.log:539: Aug 02, 2020 20:45:51.945 [0x7f3d9052b700] WARN - Subscription: No container available for /tv.plex.providers.epg.xmltv:38/metadata/tv%2Eplex%2Exmltv%3A%2F%2Fshow%2FElementary
~/Downloads/Plex Media Server.log:549: Aug 02, 2020 20:45:52.001 [0x7f3d9052b700] WARN - Subscription: No container available for /tv.plex.providers.epg.xmltv:38/metadata/tv%2Eplex%2Exmltv%3A%2F%2Fshow%2FSpace%253A%25201999
~/Downloads/Plex Media Server.log:721: Aug 02, 2020 20:45:52.824 [0x7f3d796fb700] WARN - SLOW QUERY: It took 300.000000 ms to retrieve 1 items.
~/Downloads/Plex Media Server.log:866: Aug 02, 2020 20:45:53.064 [0x7f3d799e9700] WARN - Subscription: No container available for /tv.plex.providers.epg.xmltv:38/metadata/tv%2Eplex%2Exmltv%3A%2F%2Fshow%2FMisfits
~/Downloads/Plex Media Server.log:878: Aug 02, 2020 20:45:53.066 [0x7f3d799e9700] WARN - Subscription: No container available for /tv.plex.providers.epg.xmltv:38/metadata/plex%3A%2F%2Fshow%2F5da900d67ba509001e9f48b9
~/Downloads/Plex Media Server.log:1052: Aug 02, 2020 20:45:53.373 [0x7f3d796fb700] WARN - Subscription: No container available for /tv.plex.providers.epg.xmltv:38/metadata/tv%2Eplex%2Exmltv%3A%2F%2Fmovie%2FSherlock%2520Holmes%253A%2520A%2520Game%2520of%2520Shadows
~/Downloads/Plex Media Server.log:1502: Aug 02, 2020 20:46:01.911 [0x7f3d7a88f700] WARN - Connection Tester: Error testing media server Lemnos in 10000 ms.
~/Downloads/Plex Media Server.log:1506: Aug 02, 2020 20:46:01.912 [0x7f3d91d1c700] WARN - HTTP error requesting GET /media/providers (3, URL using bad/illegal format or missing URL) ()
~/Downloads/Plex Media Server.log:1671: Aug 02, 2020 20:46:21.325 [0x7f3d925e6700] WARN - SLOW QUERY: It took 220.000000 ms to retrieve 10 items.
~/Downloads/Plex Media Server.log:1691: Aug 02, 2020 20:46:21.849 [0x7f3d92eff700] WARN - [Analytics] Attempting to send unrecognized metric (sync:downloaded). Skipping.
~/Downloads/Plex Media Server.log:1759: Aug 02, 2020 20:46:22.281 [0x7f3d92eff700] WARN - [Analytics] Attempting to send unrecognized metric (sync:downloaded). Skipping.
~/Downloads/Plex Media Server.log:1778: Aug 02, 2020 20:46:22.602 [0x7f3d925e6700] WARN - QueryParser: Invalid field 'promoted' found, ignoring.
~/Downloads/Plex Media Server.log:1779: Aug 02, 2020 20:46:22.603 [0x7f3d925e6700] WARN - QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
~/Downloads/Plex Media Server.log:2957: Aug 02, 2020 20:48:49.255 [0x7f3d78b43700] WARN - QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
~/Downloads/Plex Media Server.log:2962: Aug 02, 2020 20:48:49.404 [0x7f3d799e9700] WARN - QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
~/Downloads/Plex Media Server.log:3517: Aug 02, 2020 20:49:08.625 [0x7f3d78b43700] WARN - QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
~/Downloads/Plex Media Server.log:3771: Aug 02, 2020 20:49:58.112 [0x7f3d7a88f700] WARN - QueryParser: Invalid field 'promoted' found, ignoring.
~/Downloads/Plex Media Server.log:3772: Aug 02, 2020 20:49:58.112 [0x7f3d7a88f700] WARN - QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
~/Downloads/Plex Media Server.log:3773: Aug 02, 2020 20:49:58.112 [0x7f3d7a88f700] WARN - QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Lemnos is a friend’s server. It’s often slow or offline, so ignore that 
Hi, OK here is my log after 18 hours. A few more errors in. there now.
Plex Media Server.log (8.3 MB)
Thanks.
J.
JC,
I see it in your logs.
What I’m failing to understand here is how it thinks it’s still offline & not connected.
everything I know about how it all works is telling me you have a connectivity problem between the first hop and upstream.
My reasoning is:
Are you comfortable opening up a SSH session to the QNAP and having it run a steady ping to look for dropouts? If so, please start a steady ping to google. We’re looking for anything to drop out (missed PING replies).
Also, I think you really should optimize that database. The number of “SLOW QUERY” is disturbing. I know the N3150 isn’t a fast CPU but it still should be faster than that.
The NAS is connected directly to my modem/router by a 1m standard cable of unknown origin and probably quite old. I have just swapped it out for a brand new 1m Cat6 cable
I thought I had optimised only a couple of months ago. I have just set it to optimise again.
Yes, no problem.
…and thanks 
…how many./ how long to ping for?
…here are 100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max = 11.678/12.337/18.644 ms
[~] # ping -c 100 google.com
PING google.com (216.58.204.14): 56 data bytes
64 bytes from 216.58.204.14: seq=0 ttl=116 time=12.153 ms
64 bytes from 216.58.204.14: seq=1 ttl=116 time=12.128 ms
64 bytes from 216.58.204.14: seq=2 ttl=116 time=12.063 ms
64 bytes from 216.58.204.14: seq=3 ttl=116 time=12.397 ms
64 bytes from 216.58.204.14: seq=4 ttl=116 time=12.025 ms
64 bytes from 216.58.204.14: seq=5 ttl=116 time=12.193 ms
64 bytes from 216.58.204.14: seq=6 ttl=116 time=12.149 ms
64 bytes from 216.58.204.14: seq=7 ttl=116 time=12.072 ms
64 bytes from 216.58.204.14: seq=8 ttl=116 time=11.980 ms
64 bytes from 216.58.204.14: seq=9 ttl=116 time=12.141 ms
64 bytes from 216.58.204.14: seq=10 ttl=116 time=12.316 ms
64 bytes from 216.58.204.14: seq=11 ttl=116 time=12.450 ms
64 bytes from 216.58.204.14: seq=12 ttl=116 time=11.885 ms
64 bytes from 216.58.204.14: seq=13 ttl=116 time=12.086 ms
64 bytes from 216.58.204.14: seq=14 ttl=116 time=12.269 ms
64 bytes from 216.58.204.14: seq=15 ttl=116 time=12.463 ms
64 bytes from 216.58.204.14: seq=16 ttl=116 time=12.189 ms
64 bytes from 216.58.204.14: seq=17 ttl=116 time=12.060 ms
64 bytes from 216.58.204.14: seq=18 ttl=116 time=12.469 ms
64 bytes from 216.58.204.14: seq=19 ttl=116 time=12.404 ms
64 bytes from 216.58.204.14: seq=20 ttl=116 time=12.061 ms
64 bytes from 216.58.204.14: seq=21 ttl=116 time=12.242 ms
64 bytes from 216.58.204.14: seq=22 ttl=116 time=12.201 ms
64 bytes from 216.58.204.14: seq=23 ttl=116 time=18.644 ms
64 bytes from 216.58.204.14: seq=24 ttl=116 time=12.031 ms
64 bytes from 216.58.204.14: seq=25 ttl=116 time=12.218 ms
64 bytes from 216.58.204.14: seq=26 ttl=116 time=11.850 ms
64 bytes from 216.58.204.14: seq=27 ttl=116 time=12.258 ms
64 bytes from 216.58.204.14: seq=28 ttl=116 time=12.165 ms
64 bytes from 216.58.204.14: seq=29 ttl=116 time=12.094 ms
64 bytes from 216.58.204.14: seq=30 ttl=116 time=12.252 ms
64 bytes from 216.58.204.14: seq=31 ttl=116 time=11.678 ms
64 bytes from 216.58.204.14: seq=32 ttl=116 time=12.162 ms
64 bytes from 216.58.204.14: seq=33 ttl=116 time=12.161 ms
64 bytes from 216.58.204.14: seq=34 ttl=116 time=11.999 ms
64 bytes from 216.58.204.14: seq=35 ttl=116 time=12.477 ms
64 bytes from 216.58.204.14: seq=36 ttl=116 time=12.339 ms
64 bytes from 216.58.204.14: seq=37 ttl=116 time=15.519 ms
64 bytes from 216.58.204.14: seq=38 ttl=116 time=12.213 ms
64 bytes from 216.58.204.14: seq=39 ttl=116 time=17.682 ms
64 bytes from 216.58.204.14: seq=40 ttl=116 time=11.948 ms
64 bytes from 216.58.204.14: seq=41 ttl=116 time=12.122 ms
64 bytes from 216.58.204.14: seq=42 ttl=116 time=12.229 ms
64 bytes from 216.58.204.14: seq=43 ttl=116 time=12.146 ms
64 bytes from 216.58.204.14: seq=44 ttl=116 time=12.051 ms
64 bytes from 216.58.204.14: seq=45 ttl=116 time=11.966 ms
64 bytes from 216.58.204.14: seq=46 ttl=116 time=12.240 ms
64 bytes from 216.58.204.14: seq=47 ttl=116 time=12.128 ms
64 bytes from 216.58.204.14: seq=48 ttl=116 time=12.023 ms
64 bytes from 216.58.204.14: seq=49 ttl=116 time=12.027 ms
64 bytes from 216.58.204.14: seq=50 ttl=116 time=11.866 ms
64 bytes from 216.58.204.14: seq=51 ttl=116 time=12.263 ms
64 bytes from 216.58.204.14: seq=52 ttl=116 time=12.249 ms
64 bytes from 216.58.204.14: seq=53 ttl=116 time=12.156 ms
64 bytes from 216.58.204.14: seq=54 ttl=116 time=12.075 ms
64 bytes from 216.58.204.14: seq=55 ttl=116 time=13.347 ms
64 bytes from 216.58.204.14: seq=56 ttl=116 time=12.379 ms
64 bytes from 216.58.204.14: seq=57 ttl=116 time=12.341 ms
64 bytes from 216.58.204.14: seq=58 ttl=116 time=12.003 ms
64 bytes from 216.58.204.14: seq=59 ttl=116 time=12.179 ms
64 bytes from 216.58.204.14: seq=60 ttl=116 time=11.788 ms
64 bytes from 216.58.204.14: seq=61 ttl=116 time=12.513 ms
64 bytes from 216.58.204.14: seq=62 ttl=116 time=12.170 ms
64 bytes from 216.58.204.14: seq=63 ttl=116 time=12.053 ms
64 bytes from 216.58.204.14: seq=64 ttl=116 time=12.020 ms
64 bytes from 216.58.204.14: seq=65 ttl=116 time=12.186 ms
64 bytes from 216.58.204.14: seq=66 ttl=116 time=12.298 ms
64 bytes from 216.58.204.14: seq=67 ttl=116 time=12.130 ms
64 bytes from 216.58.204.14: seq=68 ttl=116 time=12.549 ms
64 bytes from 216.58.204.14: seq=69 ttl=116 time=12.459 ms
64 bytes from 216.58.204.14: seq=70 ttl=116 time=11.860 ms
64 bytes from 216.58.204.14: seq=71 ttl=116 time=12.185 ms
64 bytes from 216.58.204.14: seq=72 ttl=116 time=12.342 ms
64 bytes from 216.58.204.14: seq=73 ttl=116 time=12.218 ms
64 bytes from 216.58.204.14: seq=74 ttl=116 time=12.376 ms
64 bytes from 216.58.204.14: seq=75 ttl=116 time=12.163 ms
64 bytes from 216.58.204.14: seq=76 ttl=116 time=12.258 ms
64 bytes from 216.58.204.14: seq=77 ttl=116 time=12.171 ms
64 bytes from 216.58.204.14: seq=78 ttl=116 time=12.099 ms
64 bytes from 216.58.204.14: seq=79 ttl=116 time=12.117 ms
64 bytes from 216.58.204.14: seq=80 ttl=116 time=12.293 ms
64 bytes from 216.58.204.14: seq=81 ttl=116 time=12.427 ms
64 bytes from 216.58.204.14: seq=82 ttl=116 time=12.265 ms
64 bytes from 216.58.204.14: seq=83 ttl=116 time=12.202 ms
64 bytes from 216.58.204.14: seq=84 ttl=116 time=12.107 ms
64 bytes from 216.58.204.14: seq=85 ttl=116 time=12.038 ms
64 bytes from 216.58.204.14: seq=86 ttl=116 time=12.464 ms
64 bytes from 216.58.204.14: seq=87 ttl=116 time=12.166 ms
64 bytes from 216.58.204.14: seq=88 ttl=116 time=12.315 ms
64 bytes from 216.58.204.14: seq=89 ttl=116 time=12.252 ms
64 bytes from 216.58.204.14: seq=90 ttl=116 time=11.902 ms
64 bytes from 216.58.204.14: seq=91 ttl=116 time=12.116 ms
64 bytes from 216.58.204.14: seq=92 ttl=116 time=12.262 ms
64 bytes from 216.58.204.14: seq=93 ttl=116 time=12.161 ms
64 bytes from 216.58.204.14: seq=94 ttl=116 time=12.138 ms
64 bytes from 216.58.204.14: seq=95 ttl=116 time=12.030 ms
64 bytes from 216.58.204.14: seq=96 ttl=116 time=11.952 ms
64 bytes from 216.58.204.14: seq=97 ttl=116 time=12.432 ms
64 bytes from 216.58.204.14: seq=98 ttl=116 time=12.263 ms
64 bytes from 216.58.204.14: seq=99 ttl=116 time=12.174 ms
--- google.com ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss
round-trip min/avg/max = 11.678/12.337/18.644 ms
[~] #
That looks good to me 
Go back into “Network & Virtual Switch”. See how your Default Gateway is “Auto” ?
For some screwy reason, QNAP seems to work better if:
Please look at what I’ve done.
not sure how significant this is, but I was only able to select the adaptor. I don’t have virtual switch (should I?).
The existence or not of a Virtual Switch is dependent on whether you have containers or VMs defined. If you had either, you would have a Virtual Switch (brings those different software subnets together at the adapter like a router).
Were you able to Optimize the database along the way?
Out of curiosity, how much media do you have indexed? (approx count).
Hi,
OK thanks for explaining that
Yes, I pushed the button to optimise my server a couple of hours ago.
I have:
Approx 9 TB in total
Should I leave it a bit and then resend the logs?
Yes, Let it sit for a bit. Let’s see what happens.
I am concerned that the BT is going to be the root cause but don’t want to make that leap just yet.
OK. Will send some more logs tomorrow.
I am definitely not the only BT Plex user - BT is a major ISP here in the UK. But, ff BT is the root cause, I’ll take recommendations for a different router and leave the BT model/router as just a modem
[edit] My parents are also on BT and have Plex running on a Mac mini. If I get a copy of their logs, would you take a quick look to see if they have the same problem (BT being a common point for both of us)?
I know, Britian is to “BT” as Deutschland is to “DT” 
Your mac logs would definitely help . There is a common theme or there isn’t. We won’t know until we look.
OK, here we go. please ignore there fact that the logs stop a couple of days ago - I switched it off for other reasons.
Plex Media Server.log (145.1 KB)
There it is… DNS Rebinding blocking.
Aug 02, 2020 18:40:05.678 [0x700007cd9000] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (3abf452b-2113-4aef-a41f-817f7207e2e8, expected 103da56b-d291-4be3-9a84-65d7ee553ef7)
Aug 02, 2020 18:40:53.099 [0x700007c56000] ERROR - getaddrinfo(192-168-1-126.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: 8
The first shows that a reply from Plex.tv came AFTER a second test had been requested. Either the host is overloaded or the network is abysmal (goats chewing on the wires again like they do here. 
). Yes, I know that’s yesterday
plex.direct is DNS rebinding. That’s the BT preventing Plex from overlaying plex.direct domain on top of your LAN IP block . It’s a private domain and not routable but they don’t know that. Just as I did with my PfSense, the private domain must be defined (or you run on the wild side and turn all the protections off – not advised)
…and here are my logs after a couple of hours.
Plex Media Server.1.log (10.0 MB)
@ChuckPa is there a nothing I should be doing right now? …is it worth me setting different DNS on my QNAP to bypass the DNS set by BT/BT router?
cheers.
JC,
I have been researching. Sorry for not posting back to you.
If you’re comfortable setting up your own DNS server, one which is capable of handling the DNS rebinding allowances, which then forwards to the BT DNS servers, by all means try it.
This may ultimately come down to limitations imposed by that BT when it’s in router mode. If true, you’ll be better served with it in Bypass mode (modem-only) and your own router serving as the edge device ( This is the configuration I have with my ISP: Their modem/router is reduced to media conversion only. VDSL -> Ethernet. My PfSense box does all the authentication (PPPoE) and originates the routing (NAT) for my home LAN.
hey - no need to apologise for anything - I really appreciate your help!
I was first thinking of simply setting my QNAP’s STATIC setup to point to different DNS altogether (eg: QUAD9 or other). …would that not work?
Changing the DNS is a good first step TEST.
Google’s 8.8.8.8 / 8.8.4.4 is a GREAT test.
That my take care of one problem but it won’t address the DNS rebinding blocks the BT is causing.
If everything else is working - AND - you can live with those messges in your logs, then so be it ?
