There’s a pretty active thread about this at:
I’m no expert in networking, but I’ve noticed that some of the people having this problem have identified their router/firewall as the problem. I’m wondering if the connectivity checks are being interpreted as an attack of some kind. Thinking there was an attack, the router would block Plex, connectivity would be lost…
I could definitely see that. A large part of my job is configuring Cisco firewalls and intrusion prevention systems, so I know that’s not the case with my particular setup, but I’ll definitely check that other thread out. It would be nice to know the specifics of how Plex Media Server determines whether or not it’s remotely accessible. I would assume it does so by simply attempting to connect in.
When I have it check it shows this:
Private <- Public X Internet
Meaning it can NAT traverse in, but can’t reach it from the internet? Weird. Again I can get to mine directly.
Thanks again, I’ll dig in with the other thread.
Im experiencing the same remote access problems as others, wish I hadn’t just purchased the Plex Pass now after reading all the posts.
I’ve had this issue going on for a couple of months. I was thinking it has something to do with my Bitdefender Box 2 (firewall/router) since it automatically blocks suspicious network traffic, but it worked for 3-4 months under the exact same setup. I have ports manually forwarded and set up. The Tautulli checks also wouldn’t be affecting me as the Check for Plex updates and Check for Plex remote access are both inactive in my Tautulli settings.
If people rolling back to previous updates fixes the issue, I think it’s something that has been included in the last few updates that is causing the issue. I just updated to version 1.13.5.5291 today so hopefully there’s a fix in there.
My setup is PMS version 1.13.5.5291 on Windows Server 2012 R2 Essentials. My networks is a Verizon Fios G1100 router (with WiFi radios disabled) set up in a bridge with a Bitdefender Box 2 which provides WiFi and LAN and is connected to 2 Netgear switches. Port 32400 manually forwarded and Windows Firewall access is allowed.
Hey FittyFrank, or anyone else that has updated recently. Let us know how you go with the new .5291 PMS update and remote access issues, I am curious to know, thanks
Issue still exists for me today with update .5291 installed. I couldn’t connect remotely until I came home and went to the server settings on plex on my local network. Then after a second or two, remote access turns back on again.
I thought as much. I will be sticking to the .5142 update (as as stated, remote access works fine with this backdated version) until the remote access issues are well and truly fixed and sorted… appreciate the update FittyFrank.
I’ve been having this problem and the only workaround that actually works (for me) is to use the “Manually specify public port” setting.
I am using manually specified public port as well. With the double routers in bridge mode the automatic settings wouldn’t work.
Add me to the list of people having issues. I am running the .5291 version as of a few days ago, but this issue has been happening for at least a month…maybe more. Static IP. Port forwarded. No double-NAT. I’m not sure what else to do. Paid for a lifetime membership, so it’s not even like I can cancel! 
confirmed. I’m also having the same issue starting yesterday. running .5291 on Mac. Was working great before the PMS update.
This problem continues to persist. The lack of support by Plex speaks volumes. I refuse to revert back to an old update. I’ll just have to decide whether or not I want to continue paying for a defective product.
Same issue here. Wound up reverting back to a previous version until this issue is resolved.
I contacted customer service two or more weeks ago, and they said they were going to have someone take a look at this thread and respond. I gave them the link and everything. No one has responded yet, and this is extremely annoying. 4 months without service I’m paying for, and zero support 
It seems that Plex has now released another Plex Server update, being Version 1.13.5.5332. Let me know how you guys go with this new PMS update, and along with the remote access issue.
Sorry for not having a look at this forum thread earlier
I am looking at the moment at the logs posted by @slashmanmusic
To investigate what I would like to see are logs covering the time when remote access is lost and I mean lost as opposed to the status indicator in Plex Web showing it as off.
I am aware of some timing issues that may result in the Plex Web Server Remote Access setting available indicator may be inaccurate
So please have debug logging enabled on the server
Use the more reliable manual port and have a port forward in the router to the local IP of the server - with the IP being a DHCP reservation or static outside DHCP range or static but also in DHCP Reservation
When you lose remote access and clients fail to connect (eg mobile app through cellular) - then collect the server logs and attach here together with an indication as to when the remote connection attempt was made
There was an issue observed for users running Tautulli where the repeated frequent monitoring of remote access was unearthing some timing bugs in Plex Media Server and these checks should be avoided
See these support articles for server logs
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
When the problem arises you can find out what routes to the server are published to plex.tv (this is how client apps find out how to get to the server) by making this request in a browser
https://plex.tv/api/resources?includeHttps=1&includeRelay=1&X-Plex-Token=xxxxxxxxxxxxxxxx
You need to subtitute the server token for the xxxxxxxxxxx in this request
You can find out the token by hovering with your mouse on the Download Logs button and right clicking and copying the link into a text file and extracting the token from that
The resulting xml from the browser request for https://plex.tv/api/resources?includeHttps=1&includeRelay=1&X-Plex-Token=xxxxxxxxxxxxxxxx should be copied to a text file and sent to me by private message after you attach the logs here.
I am sorry your logs got missed and were not looked into at the time
It has been a long time and i do not expect you to remember the times
what we have in the logs are these periods
Jul 17, 2018 20:06:58 server launched
Jul 18, 2018 10:57:59. server shut down
Jul 18, 2018 10:58:11 server launched
Jul 18, 2018 21:16:00 Disabled and Re-Enabled Server Remote Access setting
Jul 18, 2018 21:18:18 logs captured
What i would need to know to look for potential bugs / issues is know when the remote access first dropped. So for you to disable/enable at 21:16:00 you must have thought it was down. Was it down through out the period from 10:58:11 ? Do you know when it dropped ? And did it really drop or just the setting showing as unavailable?
I can see a successful connectivity test at 10:58:33
Jul 18, 2018 10:58:33.023 [37640] DEBUG - EventSource: Got event [data] '<Message address="35.132.xxx.xxx" port="32400" asyncIdentifier="c13917c2-9222-4da5-9e49-a8091ae6c98d" connectivity="1" command="notifyConnectivity"/>'
and as mentioned at 21:16:00 you disabled and re-enabled remote access and remote access was confirmed as working at 21:16:09
Jul 18, 2018 21:16:09.419 [18956] DEBUG - EventSource: Got event [data] '<Message address="35.132.xxx.xxx" port="32400" asyncIdentifier="a74bed4f-0d40-4e73-8c48-904595aad43d" connectivity="1" command="notifyConnectivity"/>'
Probably best to wait for next time it happens and note down when you discovered it was down (and please do that by an actual remote connection test rather than looking at the server setting page) and collect the logs and send me by private message the plex.tv/api/resources response as outlined here Plex Constantly Loses Remote Access - #36 by sa2000
I responded to your post here Remote Access Drops with Version 1.13.2.5154 - #40 by sa2000 with advice that a port forward and manually specified public port is the most reliable option and has always been that way
i have the same issues and today I seem to have fixed it by turning off UPNP then ON in the router settings, then rebooting the router.
Nope…didn’t work. Woke up this morning and no remote connection again
