Can't open Plex from QNAP dashboard over Wifi on home network

Plex Media Server NAS & Devices
1

On a computer (windows 10) with a wired LAN connection to my router, I have no issues opening Plex via the QNAP dashboard icon or via app.plex.tv in a browser.

However, on a separate computer (OSX) connected to the same router via Wifi, i can only access Plex via app.plex.tv. When I try to open it via the QNAP dashboard, i get the following message in Chrome : “This site can’t be reached
192.168.0.11 took too long to respond.”

192.168.0.11 is the IP assigned to my QNAP. In my router options, I’ve opened port 32400 in that IP, but have no other opened ports.

Any ideas how I can get the QNAP dashboard Plex app icon to open plex properly?

Thanks for the help in advance!

2

What is the IP range and netmask used by your wifi network? It must be in the same subnet as 192.168.0.11, otherwise you need to specify a certain parameter in PMS settings

3

My IP range is 192.168.0.10-192.168.0.254
Subnet Mask is 255.255.255.0.

QNAP is connected via LAN to the Router, while anything connected via Wifi to the Router only gets remote connections to plex.

4

Please post logs using the following procedure

https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/

5

Thanks for the reply.

My issue is maybe more on the QNAP or network side of things, so I’m not sure if logs will help.

If I stop the server in the QNAP app center and then restart it, when I try to “Open” it I get the same message:

“This site can’t be reached 192.168.0.11 took too long to respond.”

I can only open PMS remotely via the Plex App or typing app.plex.tv in a browser.

Attached are logs after restarting the server and then opening PMS remotely in a browser and letting it idle for a few minutes.

6

I’ll also mention that I tried plugging another computer directly into the router via LAN, and can do all of the above things with no issues - connect via Plex dashboard, get a “nearby” connection instead of “remote”, etc etc.

It’s only when I’m connecting to the router via WIFI that I have these problems and am getting the “This site can’t be reached 192.168.0.11 took too long to respond.”

7

I’m not super experienced with router issues, but here’s a screenshot of some options that are factory defaults and I’m unsure of.

If more of my router settings might be helpful, just say the word. Thanks again.

8

could be DNS Rebinding Protection in the router

Could you try this in command line

nslookup  192-168-0-11.e95c4e4908fe4b8383d196a70a05503c.plex.direct

Your router DNS should translate that url to IP 192.168.0.11

If it fails, you could force Google DNS and see what you get

nslookup  192-168-0-11.e95c4e4908fe4b8383d196a70a05503c.plex.direct 8.8.8.8

All connections showing in the log are via the remote access public IP. You do have Double NAT with CGNAT IP address but that does not appear to have caused an issue with getting remote access to work

9

Sorry, how do I use command line? I’m using a mac; is there some way to use command line in the QNAP? Thanks

10

nevermind, just tried it in the terminal. I’m getting the following:

Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: 192-168-0-11.e95c4e4908fe4b8383d196a70a05503c.plex.direct
Address: 192.168.0.11

11

also, strange if I’ve got double NAS because there’s only one router connected in the apartment…

12

@GraigEarle said:
nevermind, just tried it in the terminal. I’m getting the following:

Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: 192-168-0-11.e95c4e4908fe4b8383d196a70a05503c.plex.direct
Address: 192.168.0.11

Is the default DNS using google DNS?

Did you try both nslookup commands I gave you?

13

This is not the default DNS. I was having the same issues with the default so I’d previously tried the google DNS as a troubleshooting measure. Should I switch back?

Both nslookup commands gave the same result.

14

Here’s what I’m getting with the default DNS

Server: 89.150.129.22
Address: 89.150.129.22#53

Non-authoritative answer:
Name: 192-168-0-11.e95c4e4908fe4b8383d196a70a05503c.plex.direct
Address: 192.168.0.11

15

OK so it is not a DNS Rebinding Protection issue as DNS lookup did work

So is the Mac with one network interface and is on the 192.168.0.xx subnet ?
and in browser this does not get through ?
http://192.168.0.11:32400/web
or
https://192-168-0-11.e95c4e4908fe4b8383d196a70a05503c.plex.direct:32400/web

and can you ping the server from the mac in terminal

ping 192.168.0.11

Have you tried wired connection to eliminate wifi

The QNAP did have also have other subnets 10.0.3.x and 10.0.5.x

Feb 21, 2018 13:06:58.435 [0x7f81a6d83800] DEBUG - Network interfaces:
Feb 21, 2018 13:06:58.436 [0x7f81a6d83800] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Feb 21, 2018 13:06:58.436 [0x7f81a6d83800] DEBUG -  * 2 eth1 (192.168.0.11) (loopback: 0)
Feb 21, 2018 13:06:58.436 [0x7f81a6d83800] DEBUG -  * 6 docker0 (10.0.5.1) (loopback: 0)
Feb 21, 2018 13:06:58.436 [0x7f81a6d83800] DEBUG -  * 7 lxcbr0 (10.0.3.1) (loopback: 0)

The DNS Rebinding Protection was just a thought that it might be - but it is not

16

Neither of those http links work.

The ping works in terminal.

This computer doesn’t have a LAN port, but another computer I have does (PC) and works perfectly with a wired connection.

Everything has a subnet mask of 255.255.255.0.

edit: Mac is on 192.168.0.12 and QNAP 192.168.0.11

17

When you try those links
http://192.168.0.11:32400/web
and
https://192-168-0-11.e95c4e4908fe4b8383d196a70a05503c.plex.direct:32400/web
would be good to then get the server logs to see if the requests hit the server or not.
If not - then it is some networking setup issue or security

Suggest you also try these from the computer with LAN connection that works and then we can see how the requests come in to the Plex Media Server in the logs

May be you have wifi isolation in the router / access point?
But if ping 192.168.0.11 works from the Mac then that suggests it can’t be that

Does the other computer that works with LAN have wifi ? you can then try that

18

Just leaving for work but will give all this a try later. Thanks a ton for the help!

19

Also you can look at the router LAN Network Connected devices page to see if it shows the Mac and the LAN connected computer as well as the QNAP

Is the 192.168.0.11 address a DHCP Reservation in the router?

20

What is the IP and Netmask of your OSX computer (or computers connected via wifi) ? I do not see any signal in PMS logs of any access attempt from your local LAN, looks like the issue is in networking, not in PMS.

Try to access PlexWeb using http://192.168.0.11:32400/web/index.html or https://192.168.0.11:32400/web/index.html instead of from the QNAP UI.

As a side note, if you plan to use remote connections, please contract a fixed IP. Your ISP assigned you a CG-NAT IP, and in such cases you will have trouble, not only with PMS, but also with any other service.