I’m having difficulty with this as well. I have setup port forwarding with my Xfinity router a cisco DPC3941T, it works ok for ssh over, which I have tested. I setup the 32400 port and I can telnet (or use a web browser) to the 32400 port ok (web shows “unauthorized” but I assume that’s correct), making we think the port is open. I tried turning on and off uPnP. I am running Version 1.10.1.4602 and it says its up to date.
The xfinity router is running NAT, I do have an airport extreme, but running in bridge mode, so I don’t think I have double NAT (or the ssh forwarding probably wouldn’t work either).
I just had a new router from Bell installed and Plex went offline to my Roku. I set up port forwarding, cycle Upnp, manually specified a port, rebooted everything a couple of times, purchased a new and needed 8 port switch and I still had relayed connection. The remote access was disabled as well. I read the thread about the Windows firewall which has not been touched in years. 3 Plex options were not enabled. I was chasing a network issue and I suspect that the recent upgrade to Plex 1.11.3.4803 caused windows to add 3 identical Plex programs and features to be added to the Firewall. I enabled them the same as the 3 original Plex programs and voila. Everything is OK now. 3 hours to fix this thing only to found out that a Plex update had caused Windows Firewall to add another version of Plex DLNA Server and Plex Media Server.
I just had this same issue and for some reason actually having different internal versa external port fixed the issue I do not know why maybe my firewall but a rule of 32499—>32400 and setting the external port in plex to 32400 fixed it. BTW this was working with 32400–>32400 before the last update.
I had this problem and they way I fixed it was to change Remote IP Address from ANY to SPECIFIC and to leave the range from 0.0.0.0 - 255.255.255.255. Then apply changes.
I did change firewall settings in windows and forwarded the port to Private 32401-32401 and Remote 32400.
Not sure why it worked and when I went back into the port forward rule it had set back to Remote IP Address ANY.
