Remote Access Broken

Any assistance is greatly appreciated. I’ve had Remote Access working for literally years…and it recently broke and I cannot figure out how to fix. I’m not exactly sure at what release level it stopped working, but I do know that in August when my family traveled it was working and now it is not.

Details:
Plex Version - 1.14.1.5488
Windows 10
Network setup:
-ISP Router (router rules for port forwarding are properly defined for outbound and for the Eero Pro below). Wifi is turned off on this router.
-Eero Pro Wifi system (proper ports are open on the Eero for Plex). UPnP configured as on.
-24 Channel Network switch (Ethernet going out to the house)

No matter what I do…I cannot get the external connection to become active/ready and it was working properly until very recently without any network changes. I verified that both my ISP and Eero routers didn’t change any settings.

No dual-NAT on the network. I confirmed that the IP on the ISP router and the external IP match. They’re also the same IPs that the Plex UI is reporting as external address info.

Let me know if anyone has any ideas.

Do you have a dedicated port forward or do you use UPnP?
Can you access the respective public port from outside your network (e.g. using canyouseeme.org; if you use UPnP the port should be 32400).

The ports are explicitly setup as manual port forwarding rules.

I have port 32400 manually forwarded on the Eero setup for the IP Address of the computer where Plex is running. UPnP is also flipped to “on” on the Eero, however the ISP Router doesn’t have a setting for UPnP or bridging.

I have port 32400 manually forwarded on the ISP’s router.

However, canyouseeme.org does not see port 32400.

Makes me think either something is messed up with the ISP router or with the Plex software.

PS - canyouseeme.org says --> Reason: Connection refused

The other reason I think it might be a Plex issue at some level is the setting for Enabling or Disabling remote access keeps changing by itself. So, I click “Enable” and then after retrying the connection a few times it reverts back to disabled. Not sure if this is by design, but seemed odd.

So you followed this?

Until canyouseeme shows success it will not work.
Forget about UPNP and focus on the Port forwarding.

Never used eero. Could you bypass and place Plex on primary router?

Yes, followed Port Forwarding.

I can try to bypass the Eero router. However my signal chain goes: 1) Hard line --> 2) ISP Router --> 3) Eero Puck --> 4) Switch Input --> 5) Ethernet lines

I could output a line from the ISP Router directly to the Switch, however I’m concerned that it would create two separate networks (Switch and Eero on separate subnets) and disconnect some of the in-home connectivity I have setup.

One way or another, your current issue is not with Plex itself but with your router/ISP. While canyouseeme.org cannot see your port (literally), those requests won’t even get to Plex.

Also… if you configure a port forward within your home network, that’ll do you no good. The port needs to be accessible from the outside – so you’ll need to start enabling this with the ISP router.

As for avoiding to setup multiple networks… that depends on how your ISP router works. If it’s actually a router, it probably has e.g. its own DHCP which assigns the internal IP addresses of your home network. If the Eero does the same, you already have multiple networks in your home. Unless you specifically want that you might consider several options:

  • check if the ISP router can be switched into some kind of modem mode so it only acts as gatekeeper between your ISP’s internet backbone and your main router
  • disable the dedicated DHCP on your Eero router, using it solely for physical connectivity but no active network management.
1 Like

Makes sense. I believe I can switch the Eero into a bridged connection so the ISP manages DHCP and NAT.

Hopefully that solves it.

Still no idea what changed. Maybe something updated on the routers causing things to get out of sync.

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