Remote access says Plex not visible, but manual port is forwarded and accessible as checked with canyouseeme.
Plex is also fully working when connecting via external IP address from off network location, so internet access works just fine this way.
app.plex.tv does not show the library, saying there maybe a connection problem…
How is it that Plex is accessible via external IP, but Plex reports remote access is not working, and plex.tv does not work??
There are two servers which perform the Remote Access tests.
If they cannot connect to the port (Geoblocking?) then PMS will indicate the port is closed
https://s3-eu-west-1.amazonaws.com/plex-sidekiq-servers-list/sidekiqIPs.txt
If you have a more discrete firewall (Pfsense, etc) then you must also allow these to connect as well)
Thanks, though I’m not sure what to do with these?
As I said, the external port is open and accessible when connecting directly via external IP address, but plex.tv is unable to connect and PMS itself says no external access…
I did some deeper digging into your Plex account.
I found your Plex.tv certificate was stuck in the ‘Generating’ state.
I reset it.
Please restart PMS and see if it settles down and Remote Access stabilized
(it would fail like this if a HTTPS connection couldn’t be made.)
Great, that seems to be working now, thanks.
What would have caused that? I haven’t changed anything on my end?
First and foremost, I must apologize. I’ve never seen Remote Access fail in this manner. This is a lesson for me.
For some, Weird-*** reason, when it was updating your server cert, it got stuck.
Certificates automatically update (renew) every 90 days.
What threw me was its behavior. It behaved like IP/port/firewall problems.
NOW that I know it was the cert, it makes perfect sense.
When PMS sets Remote Access
- PMS opportunistically turns it GREEN
- It sends a request using its internal certificate (different than yours)
- It then waits for the test results.
- Plex.tv came back at you, using YOUR certificate to test.
- This is where it couldn’t make the HTTPS connection
- FAILURE
Now that your certificate is valid, the Remote Access test succeeds because a HTTPS connection can be made and sustained.
One for the history books!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.