Port Forwarding not working after changing Broadband provider

Plex Media Server Remote Access
1

Server Version#: 1.26.0.5715
Player Version#:
I changed my Broad Band suppler and went full fibre 2 days ago with LIT. I am unable to get Remote Access working now on the new router.

My server sits on an I7 desktop PC and has done so for the last 4 years with no issues.

Things I have tried so far: -

Set up port forwarding on the router. Local LAN address is the desktop where the plex server is.
Set up port forwarding in the Plex Remote Access area. All 32400.
Disabled Firewalls on both the router and Windows 10 just in case that was the issue.
Toggled between disabling and re-enabling UPnP.
Disabled remote access and re-enabled it.
Removing Port Forwarding entirely and relying on UPnP.
Updating the Plex server to latest version.
Rebooting both Desktop and Router.
Ensuring Secure Connections are set to Preferred in the Network section on plex server.

I am at a complete loss. If I refresh plex on my desktop it says remote access is fully accessible. However, I know it isn’t. A few minutes later the dreaded cross comes up against the public IP access on Remote Access.

The fact that it says it is working (but isn’t) and then tells me, a few minutes to an hour later that it isn’t accessible outside my area is the strange thing.

I’m stumped.

Any suggestions as to what could possible be the issue?

2

Maybe you can find some more details to pin down what’s causing this using this guide. Generally speaking, there’s a lot of dependencies when it comes to remote access – some fall under your control, others don’t.

Your primary steps should be to identify if your new ISP is providing your router a publicly routable IPv4 address or if you’re stuck in a CGNAT setup.

3

Thanks for replying so quickly Tom. I’ll have to do a bit more research I think. I believe that the public IP address on the remote access section is set and I have no control over that? 188.74.98.252

The IPv4 IP Address of the router is of course different but further down on that section is a statement saying ISP Protocol - Routed. I’m not sure if that is relevant to what you were talking about.

I have also seen on the router set up that Remote GUI for the router’s IPv4 HTTP(S) URL is Enabled. This is to enable access into the Router rom a WAN connection so everything (I think) points to it being publicly routable.

CGNAT is way beyond me and I can find no mention of it in the router configuration settings so will have to do some more research,

4

I can see that my new ISP router is within the range of a CGNAT so it looks like I am going to be in trouble and will have to contact them to see if it can be resolved.

5

CGNAT is where your internet provider is using NAT so that you don’t actually have a public IP address. You should contact your ISP and ask them if they have this implemented. If they do then ask them if you can be assigned a static public IP address. If not you can also ask for a public IP address and then set up DDNS with one of the free providers of DDNS.

6

Thanks vey much. Will contact ISP is see what they say.

7

I am having the same exact problem after switching from Cox(local Cable) to Glo Fiber(fiber obvisouly) will contact them tommorrow and see what they have to say. Ill report back any findings.

8

Contacted my ISP they do use the CGNAT and assinged me a public IP. I then was able to port forward my eeros that seem to do the trick.

9

Thanks. Me too. Costs 5 pounds a month but worked perfectly.

10

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