Never had an issue with Remote Access before, then added an IPFire Firewall box in front of our home network.
Followed all st https://support.plex.tv/hc/en-us/articles/200931138-Troubleshooting-Remote-Access
Specifically:
Here’s what my remote access settings page looks like right now:
Having the same issue. I can connect via a browser from the outside to https://(myplexip):32400/web and it works fine. Tried different ports, tried installing on a different computer, uninstall and reinstall. Do we have access to an older version (wish I had kept one) to test?
You need to disable remote access, set up your router with port forwarding 32400 and enable remore access (and tickin that wee box). Had same issue and now works fine.
Hello Sharbb, I have tried that quite a few times. Even changing the port. It works with a browser test from outside my network (https://MYIP:32400/web), so I know the port forwarding is correct, and it worked before the last update. I think there may be something in their phone home check that now fails their connection test. Not sure what their criteria is for a connection test. Very strange. I also turned off Windows Defender as a test, since it has given me trouble in the past, where I would have to add an exception. My first test is to disable, then add an exception if it works. I appreciate the assistance!
Have you checked to make sure you’re not in a double-NAT situation?
Yes sir. Went through all of the posted troubleshooting steps. I have a dedicated PC for my firewall (IPFire). One NIC is attached directly to the modem, and the other NIC is attached to a GB switch for internal traffic. No other router/firewall in the mix. Wireless has all firewall/routing functions off. Windows firewall is off. The kicker on my troubleshooting is that port 32400 does work, it just doesn’t think it does! 
Guess this forum is the only avenue for support?
Disable ‘DNS rebinding protection’ for the domain *.plex.direct or encrypted communication will fail.
https://support.plex.tv/hc/en-us/articles/206225077-How-to-Use-Secure-Server-Connections
Make sure to use a DNS server which reliably resolves hosts on the .direct TLD.
Switch to Google’s public DNS servers (8.8.8.8 and/or 8.8.4.4) in case of doubt.
If you employ geo-blocking, make sure to whitelist your nearest Amazon AWS datacenter, because that’s where the plex cloud is hosted. And that is what PMS will contact to determnine its online/offline status.
Hello Otto! I have my Windows firewall disabled.
I added a DNS record for plex.direct which did not work. (http://forum.ipfire.org/viewtopic.php?t=14041) I also changed my DNS servers to Google’s, verified with nslookup. Tried it with my DNS entry and without it using Google’s DNS. Verified DNS lookup with both. I have GEO IP blocking turned off. Rebooted computer and firewall after config changes. No luck. Just updated to the latest version, no change. I have not parsed the IP range file (http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html#aws-ip-download) to verify that all Amazon servers are accessible, but I have a few apps that use AWS and they work fine. I welcome any other suggestions. Thank you!
@CarMelPlex said:
I have my Windows firewall disabled.
This applies not only to the Windows Firewall but to any typer of firewall.
I added a DNS record for plex.direct which did not work. (http://forum.ipfire.org/viewtopic.php?t=14041)
I am not the expert in networking, but the guide on this page makes any subdomain of *.plex.direct resolve to your own local Plex server. Which is not correct at all.
How the actual FQDNs look like, you can observe like this:
log into plex.tv, then issue https://plex.tv/pms/resources.xml?includeHttps=1 in your web browser address bar.
the content in the uri="https://172-29-0-157.b1b9f8abed4a66e7f8a8c8be9374.plex.direct:xxxxx" tags
is “the real stuff”
I welcome any other suggestions.
Sorry, this is the end of my wisdom.
@OttoKerner said:
@CarMelPlex said:
I have my Windows firewall disabled.This applies not only to the Windows Firewall but to any typer of firewall.
I don’t think so, but please correct me if wrong: “Note: This article is discussing ports in the local firewall of the computer running Plex Media Server. This is not discussing ports on a router.” I think those services are provided by the Plex software running on the PC and would need unfettered access, hence not blocked by a firewall on the PC. I have no other firewall on the PC.
I added a DNS record for plex.direct which did not work. (http://forum.ipfire.org/viewtopic.php?t=14041)
I am not the expert in networking, but the guide on this page makes any subdomain of
*.plex.directresolve to your own local Plex server. Which is not correct at all.
I tried all of the combinations, just in case. 
How the actual FQDNs look like, you can observe like this:
log into plex.tv, then issuehttps://plex.tv/pms/resources.xml?includeHttps=1in your web browser address bar.
the content in theuri="https://172-29-0-157.b1b9f8abed4a66e7f8a8c8be9374.plex.direct:xxxxx"tags
is “the real stuff”
I signed in and then attempted the URL but it returned this: Please sign in. Signed in, same result, endless loop.
I welcome any other suggestions.
Sorry, this is the end of my wisdom.
I do appreciate your help! I may try plugging in one of my wireless routers, bypassing the IPFire to make sure I have the weak link in the chain. I assume it will work and will then try to either rebuild the IPFire, or keep poking around logs until I uncover a clue.
Regards,
Carl
@CarMelPlex said:
I signed in and then attempted the URL but it returned this: Please sign in. Signed in, same result, endless loop.
This may provide you with a clue here. Apparently your firewall is blocking something which is needed to sign in to your plex account. I’d analyze which hosts are contacted when you start up PMS without the IPFire in the way. And then compare with the IPfire in place.
Well this update to IPFire seems to have resolved the issue for me: http://www.ipfire.org/news/ipfire-2-19-core-update-103-released
Would be nice to know what was the cause. I appreciate all of the assistance!
