I can see evidence of a Double NAT reported in the logs
Nov 19, 2021 22:51:17.592 [13288] ERROR - MyPlex: mapping failed due to potential double NAT configuration
Nov 19, 2021 22:51:17.592 [13288] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published (Double NAT)'.
Router is showing a 100.88.xx.xx public IP Address but the actual public IP that plex.tv is seeing is 188.xx.xx.xx
Just wanted to share my experience on this… (was able to solve my issue!)
I was having an issue very similar to those described in this thread: router config seemed fine, and Plex showing remote access Green for a few secs and then back to Red again…
And remote access not working of course…
Took me a while to figure out that the issue actually came from my Synology NAS Firewall, and not at all from Plex.
It took me so long to figure it out cause I had already added manually a rule to authorize port 32400, so I figured there was no point trying to disable the Firewall altogether cause it couldn’t be any better, right?
After a few days, out of desperation, I finally did it, and was surprised to see my remote access finally working!
So, what was wrong with the rule I created manually?
Well basically I never noticed that until now, but actually in DSM the firewall the rules are ordered. And of course I screwed the order in mine (had a general Disallow rule before the Plex rule basically).
I fixed the order of the rules and now everything works fine again!!
So, TDLR: try to disable your NAS firewall altogether to see if it fixes it, and if so, then you now know where the issue comes from :).
Hope it can help some of the future visitors here…
Cheers
I’ve never had the synology firewall enabled, so it’s not that here. I hope yours stays accessible, as I’ve given all hope of plex ever paying attention, let alone fixing the issue
Not aware of any Plex Media Server issue relating to remote access
With regards to your old post:
Was the port forward setup as follows
TCP Port Forward WAN port 32401 to 32400 on 192.168.1.9
or
TCP Port Forward WAN port 32401 to 32401 on 192.168.1.9
The latter would be wrong. It should work with this
TCP Port Forward WAN port 32401 to 32400 on 192.168.1.9
together with Server Settings for Remote Access having Manually Specify Port selected with port 32401 specified
If this does not work, please provide router screenshots, and debug server logs when attempting to enable remote access and screenshot of the Plex Web Server Remote Access screen with Show Advanced
Same problem just happened to me. Everything was working fine for years and then today i replaced my ethernet pci-e card and I lost remote access. It stays green for 5 sec and go offlline
Received notifyConnectivity event with incorrect async identifier
wait, the 427 post in this thread are all from the same person /problem ? Sorry i posted here because the thread title is exactly the same problem i have
No, the thread is from Feb 2020 and given the post count I’m sure there were multiple people/issues involved. It also got necro’d a few days ago after having been dormant for a year. Neither of which negates my point; which is that for most troubleshooting where everyone’s setup is different, separate threads make it easier for all involved. I see you have posted one, so I’ll jump over there to help.
Looks like the issue has returned. since the move to the new app. my remote access would go green then back to red. The only update was the plex update.
Same problem. I have a server working without problem then another smaller server that just gets green, red, green red… cant access it remotely anymore… tried everything i can think off… even a fresh install and restore.
