CGNAT: 100.64.0.0/10
This block includes addresses from 100.64.0.0 to 100.127.255.255 , providing 4,194,304 unique IP addresses for use by ISPs in CGNAT deployments.
From your logs:
NAT: UPnP, public address is 100.65.233.70
PublicAddressManager: got WAN IP 100.65.233.70 from router
I’m in exactly the same situation. I’ve checked everything in the troubleshooting guidance. I’m not in Double NAT, my port forwarding rules have not changed in two years, my router hasn’t changed, I’ve not changed ISP- in fact I’ve not changed anything. But I’ve had the Not Accessible Outside Your Network message for 2 weeks.
Yes, I’ve got a static IP address, I’m not in CGNAT.
This all worked perfectly well. But now, whatever I try, nothing seems to improve the situation.
debug is under settings. there’s a debug option on all of the choices in the left column. flip to enabled. do not do verbose. i then restarted plex to let it fail and get info. then you download and upload to your post as an attachment.
for my issue — i called my ISP support. they opened a ticket and someone was to call me within 24 hours. He did say they’ve gotten several CGNAT calls recently. Yesterday morning my entire internet went offline for a few minutes. When it came back up, plex worked again. Still no call, but I am fully functional. I’m going to guess they did something. But what? I don’t know.
If your setup has not changed, Plex update could be the culprit. What worked for me was to disable Windows firewall, which caused remote access to become stable. I then created an inbound FW rule to allow the connection to plex media server.exe. along with a port rule for 32400 and re-enabled the FW.
I seem to have had a flash of inspiration. I use EE as my ISP and they provide Norton as security software. It appears Norton had been over zealous and thought that changing the network to Public would be helpful! Having set it back to Private, rebooted the router, I now appear to be up and running again.