I don’t understand what is happening, my server has been online and working fine for years. I updated to the newer UI treatment version and now have loads of issues connecting remotely.
Settings > Remote Access will give me all green check marks for about 15 seconds, then shift to red. Even thought it shows red, I’m still able to get to the server but sometimes it says ‘no libraries available’ until I restart the server. There has been no changes to my router (Google Mesh/Wifi) my IP is static on my server and I have a port forwarding rule that has been working for ages with no issues.
I’ve tried updating to the latest version of Plex, restarting my router, all behavior continues.
So if you see your inital connection showing online, and then it flaps to offline, maybe that is a pretty good sign that you have inconsistent routing? Regardless, in my case was due to Double NAT.
It turns out, someone called to troubleshoot cable, and in the course of the call to Xfinity, the rep reset the modem/router and in doing so, turned OFF Bridge-Mode. So it was acting as a Man-in-the-middle router trying to redirect my traffic.
I can now confirm via canyouseeme.org that my server is available and consistent connection seems to be restored.
Also, for some dumb reason, if you are on Xfinity Mobile, the feature is under
Wifi > WiFi > Broadcast wireless network (not labeled as bridge mode)
On a computer browser, you will need to navigate to http://10.0.0.1 – default admin (admin) default password (password).
Another clue for me was that within Google Home App > Advance Settings > WAN Connection > WAN IP — it was giving me a 10.X.X.X IP Address, and NOT showing me my Public IP Address given via Xfinity. This was what tipped me off to the Double NAT.
No. The initial green status is just an unfortunate design decision. It optimistically shows green before the actual connection test is performed. Once the latter has been done and failed, it turns red.
The takeaway is to simply disregard the remote status for the first few seconds.