Server is connected to network via ethernet cable.
Is possibly the issue that the server is connected to an AP (Archer A7 in Access Point mode)? The AP is cable-connected to the router. So, the router settings are as above but the AP provides no specific settings and should be a pass thru to the router – I think.
So you have a modem from your ISP in bridge mode? Connected to an A7 acting as your router, which is connected to another A7 in AP mode? If not, then you might be dealing with a double NAT situation. You will want to confirm this is not the case if you have not done so already, and also eliminate CGNAT.
You could try setting a manual port forward instead of relying on UPNP.
No, no separate modem – at least, no other device. We have fiber to our house which comes into a “gray box”; it appears to be just a fiber-to-ethernet transfer. From the “gray box” is ethernet to the router incoming WAN line. But, yes, the router is an A7 in “normal” mode using NAT and another A7 (in AP mode) is connected via cable to the router, and the server is connected via cable to the AP.
I considered the manual forwarding but it seemed unlikely given that the UPnP is indicating the correct ports internal/external. But, I just tried adding a “virtual server” (the listing in my router) forwarding this port. I get the same results. When I first go view the “Remote Access” section in Plex, it initially shows green (accessible) but then turns to red (inaccessible) after a second or two and remains that way.
The site “canyouseeme.org” reports that it cannot see my public IP/20040. Guess I’ll call my ISP…
Is your fiber Fios by any chance? I seem to recall that their Home Network Protection stuff does not play nicely with Plex remote access. You may also want to check that your provider does not have any other sort of ‘smart’ protection active that could be interfering.
Have you compared your public IP address with your WAN IP to make sure they match? And that it’s not in the CGNAT range of 100.64.0.0 - 100.127.255.255
That’s interesting because I’m pretty sure last time I looked at this (year or so back maybe), they were the same. So, it appears the ISP has introduced CGNAT. I’m not familiar with it but have done some research and found this: How to Port Forward on Xfinity Routers and Get Around CGNAT. So, maybe a VPN is an option?
I’ve not seen any answers so: If you haven’t already, go through the steps listed above in the original discussion; i.e., check whether your router IP is in the range 100.64.0.0 - 100.127.255.255 and use canyouseeme.org to confirm whether your external IP matches the router IP – likely not, if it is in that range.
For me, I’m still working on this. Using a VPN allowed me to get past CGNAT; i.e., I now have a different IP and it matches what canyouseeme.org shows. But my initial effort to get the remote access working still fails and I’ve been too busy lately to work on this.
