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

Plex Media Server NAS & Devices
21

Hi again. Sorry, I was away for a few days. Thanks again for your help.

Responding to sa2000’s last 2 comments:

I’ve attached a server log. I restarted the server, then first opened Plex via LAN on the windows PC. I then unplugged the LAN, went on wifi and tried opening Plex again. It failed, exactly as it’s been failing on the Mac over Wifi.

So, the issue isn’t specific to my Mac, but does seem to be specific to WIFI.

The LAN Network Connected devices page shows that the QNAP, Mac and Windows PCs are all connected to the router.

192.168.0.11 is a DHCP reservation in the router for the QNAP. No other address is reserved.

When I look at my router’s port forwarding (all of which have been configured by uPNP since I haven’t manually forwarded any), the Plex server has 2 entries on IP address 192.168.0.11 :

The first is TCP external port 17914 & internal port 32400.

The second is TCP External 23815 Internal 32400.

Not sure if this is how it should be or not; seems a bit odd that internal port 32400 is forwarded twice with 2 different, nonmatching external ports.

I’ve tried contacting my ISP to ask them if they know what the issue is and the “technician” unfortunately couldn’t help me and told me his plex server works great with the same router… (it’s a Sagecom FAST3890_D0)

Thanks again for the help and please let me know if there are any other troubleshooting steps I could try and/or if you need me to repeat anything or maybe missed something.

If it’s possible to do some sort of remote access or screen sharing, I 'd also be down for that, just let me know.

responding to moody_blue:

The Mac is on 192.168.0.12, subnet 255.255.255.0.

Neither of the links you provided work when I’m on WIFI, but they do work when I’m connected via LAN.

I will contact my ISP about a fixed IP. What would that help with, and might it immediately clear up problems or would I then need to forward ports or ?

Thanks!

22

@GraigEarle said:
I’ve attached a server log. I restarted the server, then first opened Plex via LAN on the windows PC. I then unplugged the LAN, went on wifi and tried opening Plex again. It failed, exactly as it’s been failing on the Mac over Wifi.

So, the issue isn’t specific to my Mac, but does seem to be specific to WIFI.

The LAN Network Connected devices page shows that the QNAP, Mac and Windows PCs are all connected to the router.

192.168.0.11 is a DHCP reservation in the router for the QNAP. No other address is reserved.

The log shows successful connections to the serve via the local network from 192.168.0.20. I presume this is the wired connection for a PC

With regards to 192.168.0.11 this shows a target connection to 192.168.0.11:32400/web/index.html coming in via the router gateway as redirect (HTTP Response Code 301)

Feb 26, 2018 00:00:28.841 [0x7f93887ff700] DEBUG - Request: [192.168.0.1:51299 (Subnet)] GET /web (7 live) GZIP Signed-in
Feb 26, 2018 00:00:28.842 [0x7f9397d11700] DEBUG - Completed: [192.168.0.1:51299] 301 GET /web (7 live) GZIP 0ms 235 bytes (pipelined: 1) -> http://192.168.0.11:32400/web/index.html

Don’t know why that is

But if all wifi connections are failing then may be you have wifi isolation in the router

There were some DNS failures and loss of network in one of the logs - that could have been you rebooting the router perhaps - happened between 00:14:48 and 00:15:11 Feb 26

Feb 26, 2018 00:14:48.989 [0x7f9394911700] DEBUG - Network change.
Feb 26, 2018 00:14:48.989 [0x7f9394911700] DEBUG - NetworkInterface: Notified of network changed (force=0)
Feb 26, 2018 00:14:48.991 [0x7f9394911700] DEBUG - Network interfaces:
Feb 26, 2018 00:14:48.991 [0x7f9394911700] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Feb 26, 2018 00:14:48.991 [0x7f9394911700] DEBUG -  * 6 docker0 (10.0.5.1) (loopback: 0)
Feb 26, 2018 00:14:48.991 [0x7f9394911700] DEBUG -  * 7 lxcbr0 (10.0.3.1) (loopback: 0)
. . .
Feb 26, 2018 00:14:52.544 [0x7f9394911700] DEBUG - Network interfaces:
Feb 26, 2018 00:14:52.544 [0x7f9394911700] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Feb 26, 2018 00:14:52.545 [0x7f9394911700] DEBUG -  * 2 eth1 (169.254.100.100) (loopback: 0)
Feb 26, 2018 00:14:52.545 [0x7f9394911700] DEBUG -  * 6 docker0 (10.0.5.1) (loopback: 0)
Feb 26, 2018 00:14:52.545 [0x7f9394911700] DEBUG -  * 7 lxcbr0 (10.0.3.1) (loopback: 0)
. . .
Feb 26, 2018 00:14:54.846 [0x7f9395511700] ERROR - Error broadcasting message: send_to: Network is unreachable
Feb 26, 2018 00:14:54.846 [0x7f9395511700] DEBUG - Network change for advertiser.
Feb 26, 2018 00:14:54.846 [0x7f9395511700] ERROR - Error broadcasting message: send_to: Network is unreachable
. . .

Feb 26, 2018 00:15:04.823 [0x7f9394911700] DEBUG - Network interfaces:
Feb 26, 2018 00:15:04.823 [0x7f9394911700] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Feb 26, 2018 00:15:04.823 [0x7f9394911700] DEBUG -  * 2 eth1 (192.168.0.11) (loopback: 0)
Feb 26, 2018 00:15:04.823 [0x7f9394911700] DEBUG -  * 6 docker0 (10.0.5.1) (loopback: 0)
Feb 26, 2018 00:15:04.823 [0x7f9394911700] DEBUG -  * 7 lxcbr0 (10.0.3.1) (loopback: 0)

@GraigEarle said:
When I look at my router’s port forwarding (all of which have been configured by uPNP since I haven’t manually forwarded any), the Plex server has 2 entries on IP address 192.168.0.11 :

The first is TCP external port 17914 & internal port 32400.

The second is TCP External 23815 Internal 32400.

Not sure if this is how it should be or not; seems a bit odd that internal port 32400 is forwarded twice with 2 different, nonmatching external ports.

Could have been the network outage led to a new port being assigned

I would recommend two things here

  1. Buy a fixed WAN IP address from your ISP to overcome any CGNAT issues and Double NAT because of it, eg
Feb 25, 2018 23:41:41.510 [0x7f9393fff700] DEBUG - NAT: UPnP, public address is 100.123.xx.xx
Feb 25, 2018 23:41:41.510 [0x7f9393fff700] DEBUG - PublicAddressManager: got WAN IP 100.123.xx.xx from router
Feb 25, 2018 23:41:41.510 [0x7f9393fff700] WARN - PublicAddressManager: WAN IP on router does not match public IP from plex.tv
  1. Switch to manually specifying the public port and have a port forward setup in the router rather than uPnP
23

Just solved it via (default QNAP Plex app) by changing the https into http… (initially)

24

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.