When I run the option to Retry Remote Access, I get the following warnings in the logs:
1. Jul 16, 2023 16:14:18.269 [0x700004b70000] Warning — [Req#68c] NAT: PMP, got an error: Not Supported by gateway.
2. Jul 16, 2023 16:14:24.845 [0x700005217000] Warning — [Req#68c] NAT: PMP, got an error: Not Supported by gateway.
3. Jul 16, 2023 16:14:24.847 [0x70000508e000] Warning — [HttpClient/HCl#6f] HTTP error requesting GET https://[redacted].49a0d250610f43099a470bddf75b3672.plex.direct:0/identity (7, Couldn't connect to server) (Failed to connect to [redacted].49a0d250610f43099a470bddf75b3672.plex.direct port 0 after 0 ms: Couldn't connect to server)
4. Jul 16, 2023 16:14:30.769 [0x7000053a0000] Warning — [Req#708] NAT: PMP, got an error: Not Supported by gateway.
5. Jul 16, 2023 16:14:32.370 [0x7000056b2000] Warning — [Req#708] NAT: PMP, got an error: Not Supported by gateway.
6. Jul 16, 2023 16:14:32.372 [0x70000508e000] Warning — [HttpClient/HCl#72] HTTP error requesting GET https://[redacted].49a0d250610f43099a470bddf75b3672.plex.direct:0/identity (7, Couldn't connect to server) (Failed to connect to [redacted].49a0d250610f43099a470bddf75b3672.plex.direct port 0 after 0 ms: Couldn't connect to server)
I have internet through Xfinity, but I’m running their modem in Bridge Mode and using a Linksys router with OpenWRT on it to manage my network. I run the wireless through a TP Link Deco mesh system. I haven’t made any changes to my network configuration in over a year, so I’m at a bit of a loss for where to start troubleshooting.
I’ve verified that I’m not experiencing a Double NAT, I’ve tried changing the port to 32401, I’ve verified everything is running the most recent version, I’ve restarted the modem and router and mesh numerous times, I’ve tried new DNS servers (Google and OpenDNS), and I’m at a loss!
What are the next steps for me to troubleshoot this issue?
are you using upnp on the router or mesh system (which ever system is distributing the 102.168.0.X addresses?
how have you verified you aren’t in a double nat situation. You linksys or the TP Link mesh system (one of them) would need to be in bridge mode as well if i’m understanding your topography correctly.
You are double Nat’d unless you buy a modem and replace the Comcast router. Bridge mode just forwards all ports to one ip but still traverses a private ip, probably 10.0.0.1. Document what your network looks like (only need the first two octets) Public IP > Xfinity IP > TP Link > PMS Server.
The Linksys OpenWRT router is managing DHCP, Xfinity Modem and TP Link Deco Mesh are in bridge mode.
The Plex server is hardwired directly into the Linksys router.
To verify that I’m not in a double NAT, I’ve checked that the public IP address showing on my router status page is the same public IP address detected by Plex, and whatismyipaddress.com, etc.
Advanced Security is not enabled, and has never been enabled. When I open my Xfinity app, the Overview page shows me a prompt to turn on Advanced Security.
Just to reiterate, this setup has worked with no changes for the past year, and only recently starting failing with no change on my end.
I have followed a number of online guides (like the Plex Support aticle) to verify that I’m not experiencing a double NAT. You say pretty confidently that I’m experiencing this. Can you share the steps to check?
Yes, I’ve rebooted everything a few times throughout the last few weeks as I’ve been troubleshooting this.
I’ve also tried remapping the port to no avail.
I think I may have framed the problem incorrectly - it’s not just that Remote Access isn’t working, it’s that the server is unavailable, even on local devices. I’ve tried on my Nvidia Shield, my iPhone, a Fire TV, etc.
you need to provide a full set of server logs and hopefully someone that can read those better than me comes along.
you may also want to confirm the servers ip address as well as any one of the devices ip addresses that cannot see the server. your laptop or whatever. I know you have said they are on the same lan and explained how your set up is but people will trust its actually on the same lan if you confirm the specific IP addresses above.
obviously people always say that nothing changed but something similar happened to me a year ago. nothing changed from my perspective but something did either on the server, an update, the router, comcast blocking. vpn. not sure. likely nothing you specifically changed though. networking is weird!
Resetting his Cert won’t do much unless he fixes his networking.
On the Xfinity router he needs a port forward 73.x.x.x:32400 to WAN IP of TP Link. ( Probably 10.0.0.1) 1st NAT
On TP link, port forward 10.0.0.1:32400 to 192.168.0.115. Second NAT.
These are static ports so turn off UPNP and manually specify port in Plex remote networking.
All devices wired and wireless need to be connected to the TP Link, only the TP link should connect to the Xfinity router via the WAN port.
I can’t forward a port on the Xfinity Modem/Router combo because it’s in Bridge Mode, and it’s not my DHCP server.
I can’t forward a port on the TP Link Deco Mesh system, because it’s in Access Point mode and it’s not my DHCP server.
My DHCP server is my Linksys OpenWRT router. All devices are either hardwired to the Linksys Router, or receiving WiFi froim the Linksys Router/TP Link Deco Mesh combo. Here’s a chart for clarity:
To the best of my knowledge there is no double NAT, and I’m confused by your assumption that there is despite the information I’ve shared so far. Can you please point me in the direction of a troubleshooting guide that would help me determine whether this is the case? The Plex support guide for Remote Access tells me to compare the WAN IP address on the router (my Linksys router) to the IP address that shows up on my Plex server when I visit a “What is my IP” site. For me, these are the same IP addresses (see here).
More importantly, the issue I’m experiencing isn’t just that Remote Access won’t work, it’s that the server is Unavailable, even on the same network. As far as I can tell, this wouldn’t be the case if my issue was solely a Double NAT.
Also - here are the first 5 hops with a traceroute:
1 OpenWrt.lan (192.168.0.1) 4.818 ms 4.766 ms 4.748 ms
2 100.93.92.66 (100.93.92.66) 19.008 ms 100.93.92.67 (100.93.92.67) 18.941 ms 18.928 ms
3 96.216.161.165 (96.216.161.165) 18.963 ms 30.557 ms 96.216.161.157 (96.216.161.157) 30.542 ms
4 96.108.139.157 (96.108.139.157) 30.525 ms 18.900 ms 68.86.103.101 (68.86.103.101) 18.833 ms
5 be-304-arsc1.denver.co.denver.comcast.net (96.216.147.13) 30.436 ms 30.422 ms 30.404 ms
I wouldn’t expect this to impact local streaming though. It’s possible there’s multiple issues happening at once, but am I right to think that CGNAT wouldn’t cause me to see an unavailable server/library within my own network?
