So I go onto the server, disable remote access and then enable it again which works for 15 minutes and as I watch it then just disables it self. What is odd is I can still access it via the web app. The reason for this being an issue is that Alexa won’t see the player and though the web app works Alexa doesn’t
I was going to start yet another “Remote Access Keeps Going On and Off” thread, but maybe I can just jump in here.
I am super frustrated with it going on and off all day and night. Sometimes I can get a few hours, then I get notified by PlexPy that it’s offline again. Then a couple of hours later it just goes back on line. I’ve tried EVERYTHING in the help sections. I’ve enabled and disabled uPnP, I’ve activated and deactivated port forwarding, I’ve done both together, or with just one active, or with none active and nothing changes that fact that I cannot get a stable, long lasting remote connection to last.
SURELY with all the constant threads on this there MUST be a problem on the Plex end of things? About a year or so ago, it was rock solid. Never dropped and stayed active all day, everyday. Yes, in most cases the relay indirect connection will save the day, but that’s not the point. Yes, re-booting the router, or PMS, usually brings it back for a period of time, but it NEVER, EVER stays on. It ALWAYS disconnects and does it all day and night.
I have D-LINK DIR-880L router that is fairly new. I don’t know if it’s this particular router, or what to try next.
DOES ANYONE OUT THERE ACTUALLY GET A STABLE REMOTE ACCESS CONNECTION THAT STAYS ACTIVE for more than a few hours at a time? If so, please tell us what EXACTLY you are doing. With so many people having the same problem there HAS to be something on the Plex side that is causing this.
I have two instances and both have a reliable remote access connection.
One with a fixed ip behind a reverse proxy: remote access works flawless, even though the remote connectivity is marked as unreachable.
One with a dynamic ip with port forwarding: remote access works flawless since years across all the updates that came along. Though, there was a time when a bugged firmware version of my router messed up the port forwaring rules. Appart from that: works like a charm!
The user mygatenet had the situation where two PMS Docker instances where running at the same time using the same machine identifier, which led to a random loss of remote connections. It is impossible for two instances to share the same config/library folder and have a reliable remote connection. Though, working with two copies of the config/library folder works, if everything except the Preferences.xml was copied.
@Verminator14 said:
DOES ANYONE OUT THERE ACTUALLY GET A STABLE REMOTE ACCESS CONNECTION THAT STAYS ACTIVE for more than a few hours at a time? If so, please tell us what EXACTLY you are doing. With so many people having the same problem there HAS to be something on the Plex side that is causing this.
Set portwarding in the router {WAN-IP}:{REMOTE-PORT} → {SERVER-IP}:32400 (32400), TCP
if the router supports “dns rebind protection”, create an exception for *.plex.direct
In PMS remote access: activate remote access, check manual public port and enter the REMOTE-PORT and apply (assuming the user is logged in).
Check your remote access
If still not working: share screenshots of router port forwarding settings and the pms remote access settings.
A picture is worth a thousand words…
Glad it’s working for some of you. For some reason it’s no longer giving me a false positive and just shows as “Not Available outside your network” The Plex Server is plugged directly to the router via cable and I’ve checked with just wifi (Before it worked with one or the other couldn’t remember)
What’s interest is if I set it to autmatic port and then use the port it’s automatically using as a static port it just breaks (I added it in port forwarding and disabled the old one: