Plex constantly disables remote access

Server Version#: 1.14.1.5488
Player Version#: 3.89.2

I’ve been trying to let my family access my server and share my content. However every time plex service is restarted, or sometimes just randomly it will show the server as “indirect” on the remote side (outside network). In this case they or I would go to the remote access settings and click check again. At which point the check fails and plex completely disables remote access. I have to at that point from the local (inside) network go into plex and re-enable it. Usually it will fail 4-5 times repeating the same indirect/disabled cycle. Eventually it will work. I can’t find a pattern to it.

Setup is as follows:

Inside ip: 192.168.1.100
Inside port: 32400
Outside port: 18700

Inside firewall config:

ACCEPT tcp – br0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:32400
ACCEPT udp – br0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:32400

Outside firewall config:

outside ip -> 18700 UDP/TCP -> inside ip -> 32400 UDP/TCP

If I use telnet from a remote server to check, or via https://canyouseeme.org/ I have absolutely no problem reaching the 18700 port and getting to the 32400 inside port on the plex server. It always works 100% of the time. So this is not a firewall/nat issue.

As you can imagine this is frustrating for non-technical users and as a result me.

There is a race condition in the code. It has been that way for some time now. (year plus)
Engineering hasn’t been able to fix it.
Sorry

That’s too bad. Is there anything i can do in terms of helping debug the issue? I can spend some more timing trying to find a pattern to replicate it. Of course if it’s already a well understood problem and solution is just blocked in terms of resolution, I’ll just be patient :). Thanks for the quick reply!

No, and here’s why.

Your PMS contacts Plex.tv to say “Here I am”.
Plex.tv (a different host most likely) contacts back.
Between the time your PMS sent the request (with an ID number) and Plex.tv replied, PMS sent another request which invalidated the first. The second also fails because it wasn’t expected.

Eventually, it sorts itself out.

1 Like

That makes sense. Thanks Chuck!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.