Not available outside your network

General Discussions
1

I have a Plex running on a Freenas Server. I put new albums into a watched music folder. When I was done, Plex was unable to update the media. I poked around Plex and noticed it was no longer available outside my network. Which is the whole reason you have Plex. I checked the forum and it looks like lots of people have had the same problem. However, I was not able to fix the problem with other peoples solutions. Help!

2

please give us some more information to help you.

  1. what kind of router do you have
  2. are you using UPnP or a port forward.
  3. logs
3
  1. I’m using a Googe wifi - mesh router
  2. I have UPnP enabled and Port Forwarding set up, but to be honest I don’t know if I’ve done it correctly. My private ip address is totally different than my public ip address. I’m not sure if that’s normal.
  3. I’ve attached the logs
4

looking at your logs i see this:

Feb 23, 2018 05:37:10.065 [0x80bc5e000] DEBUG - PublicAddressManager: Obtaining public address and mapping port.
Feb 23, 2018 05:37:10.065 [0x80ad5f400] DEBUG - NAT: UPnP, attempting port mapping.
Feb 23, 2018 05:37:10.065 [0x80bc5e400] DEBUG - PublicAddressManager: Obtaining public IP.
Feb 23, 2018 05:37:10.065 [0x80bc5e400] DEBUG - HTTP requesting GET http://plex.tv/pms/:/ip
Feb 23, 2018 05:37:10.333 [0x80bc5e400] DEBUG - HTTP 200 response from GET http://plex.tv/pms/:/ip
Feb 23, 2018 05:37:10.333 [0x80bc5e400] DEBUG - PublicAddressManager: Got public IP from http://plex.tv: 47.185.106.95
Feb 23, 2018 05:37:13.140 [0x80ad5f400] DEBUG - NAT: UPnP, found device http://192.168.86.1:5000/rootDesc.xml with private address <192.168.86.6>
Feb 23, 2018 05:37:13.144 [0x80ad5f400] DEBUG - NAT: UPnP, usable device http://192.168.86.1:5000/rootDesc.xml with private address <192.168.86.6>.
Feb 23, 2018 05:37:13.146 [0x80ad5f400] DEBUG - NAT: UPnP, mapped port 27678 to 192.168.86.6:32400.
Feb 23, 2018 05:37:13.411 [0x80bc5e400] DEBUG - NAT: UPnP, found device http://192.168.86.1:5000/rootDesc.xml with private address <192.168.86.6>
Feb 23, 2018 05:37:13.416 [0x80bc5e400] DEBUG - NAT: UPnP, usable device http://192.168.86.1:5000/rootDesc.xml with private address <192.168.86.6>.
Feb 23, 2018 05:37:13.418 [0x80bc5e400] DEBUG - NAT: UPnP, public address is 192.168.1.36
Feb 23, 2018 05:37:13.418 [0x80bc5e400] DEBUG - PublicAddressManager: got WAN IP 192.168.1.36 from router
Feb 23, 2018 05:37:13.418 [0x80bc5e400] WARN - PublicAddressManager: WAN IP is a private IP address
Feb 23, 2018 05:37:13.419 [0x80ad5f400] DEBUG - PublicAddressManager: Mapping succeeded for 192.168.86.6:27678.
Feb 23, 2018 05:37:13.420 [0x80ad5f400] DEBUG - MyPlex: Last published value didn’t change, we’re done.
Feb 23, 2018 05:37:13.420 [0x80bc5e400] DEBUG - MyPlex: Last published value didn’t change, we’re done.

I see that you are using 192.168.86.6 as a public address, this is not correct as all 192.168.x.x networks are private and are not routable on the Internet.

I believe you may be in a double nat situation, but I would need more information:
it looks like your plex server is: 192.168.86.25
it look like the wan side of your google mesh router is 192.168.86.1
and your outside real public address is 47.185.106.95
from your logs my guess is this:

plex server connects to google mesh router which in turn is connected to isp device (router) which is connected to isp (internet)

so I’m guessing you have another device from your isp?
please list all your network devices and model numbers if possible

  1. google mesh router, Model number?
5

I have a cable modem

Verizon Fios Acitiontec
Model: mi424wr

Because the modem has a very limited range, I disable the wifi on the router and and added a Google WIFI mesh router.

Google WIFI
Model: AC-1304

To confirm my ip address is 47.185.106.95 and to my knowledge the google WAN is 192.168.86.1. I don’t what my Plex server ip address is. I’m assuming your correct in your assertions.

6

So it looks like you have two routers which is usually a problem.
the easiest fix is to put one of the routers in a non routing mode, such as bridge mode or ap only mode.

are your two router in the same location?

also do you have multiple google wifi (mesh) devices?

7

The two router are in the same location and Google wifi mesh comes with 3 devices. One device acts as the router and the other two distribute the signal.

8

so you are going to need to bridge one of the routers, as google mesh requires the main mesh node to not be in bridge mode, it looks like you should probably bridge your Verizon Fios Acitiontec

9

this (bridging the verizon) would remove the double nat situation and hopefully restore your remote access