Thanks for the tip. I have been unable to get a “Green” light for remote access, but after reading your post, I just tried logging on through my Router net address, and it worked. Using app.plex.tv also worked, but Remote Access is still red.
confirm with your isp if your in a Nat on their end… or that you can open ports needed… you maybe behind a double nat environment
“confirm with your isp”
LOL- Har-de-har....... My ISP is Verizon FIOS. Getting a straight
answer from their “support” is a joke, and they want me to pay $120
for “premium technical support” to get answers beyond, “is it
plugged in”?
I use Open port Check Tool at [https://canyouseeme.org](https://u2182565.ct.sendgrid.net/wf/click?upn=2s0qHf9caT9wbe8CB8ESQu-2Bjoi0Ixrr6DsuNonXSLODDXCKfmuEdqethmXkRVMix_EQOAB9kEwcPNAL6b-2FJTTTr10vEgqv2SqPV-2Fsde-2FqJK-2FdKAtfkkL29YciUmpEjTUT7fK1cS2hrdzCcH5fj9A-2BjAlofe-2FAVfiaiOcnPIdBVaQjQ3CWi0ne8032EEgI8lbrvqSr228Z67I1sVAzKiFPu6Kc-2F5MBTmU5MeEXLrl920DpXJZUSz4HvCSWaSNDiOXpGDuhvnURaa2DX2lmLe9VM2XftQJFi29V37HbPnCObrl1KLSEq2NLTgIwm3slVpK-2FgHAWq7UoCNwPHXc81XBWSw-3D-3D)
to make sure that my default port (34200) is accessible.
I am sure there isn't a double NAT because I can log onto plex using
my external IP address and plex.tv, but the Remote Access icon in the dashboard is red.
Oh, and thanks for the reply
OK, so I set up a port monitor to see if I could find any consistencies.
My other application’s ports stay available when my Plex port stops responding. I’ve reviewed all of the stuff shown in the documents referenced above. At what point do we actually start looking at Plex as the issue and not my router or firewall?
1 Like
I have been looking at your logs from the 2 servers. i will summarize what i saw. It is not clear to me which specific time you are referring to for loss of remote access
HTPC Server
we have logs from the server on version 1.15.2.793 from 20:22 to 21:34 when the server was shut down, and then
a restart on version 1.15.3.858 from 21:34 to the time logs were collected at 21:41
For the time the server was on 1.15.2.793, the logs show there were two remote connections one from LG TV app user cnhanxxx and this was accessing the server through remote access connection. At the same time there was a paused firefox playback session for user chatengxxxxx - this was for some reason through Plex Relay. Not sure why it chose relay but to establish that, one would need to see logs from Plex Web at the time it enabled relay and also from the server. This was some 9 hours earlier - but throughout that time the LG TV App for the other user was seeing the server and playing back through the remote access wan IP and port - which at the time was a uPnP random port 11280 and not a port forwarded manually specified port.
To enable plex web logging, user would need to select beforehand settings / web / show advanced / debug / enable verbose and save changes and when plex web log to be collected, then settings / web / show advanced / debug / view log / select all displayed log text and copy to notepad and save as text file and obtain the server logs
A connectivity test on the server at 21:33:44 was successful
Apr 05, 2019 21:33:44.429 [8064] DEBUG - EventSource: Got event [data] '<Message address="116.90.xxx.xxx" port="11280" asyncIdentifier="192a22e0-749f-49e8-a3fb-6847dc07819d" connectivity="1" command="notifyConnectivity"/>'
Apr 05, 2019 21:33:44.429 [8064] DEBUG - PubSub: Got notified of reachability: 1 for 116.90.xxx.xxx:11280
So with the exception of the firefox session using relay - it appeared to be ok.
The logs after the restart at 21:34 show several actions of disabling / re-enabling remote access. I can see that remote access was actually established in each case, but for some reason you repeated the sequence of disabling and re-enabling remote access. Was this because Plex Web was not correctly updating the status to green ?
If there is an issue after re-enabling remote access, then try F5 to refresh the browser. If it still does not work, then i would like to see what you get back when you put this in a browser on the server at that time
http://127.0.0.1:32400/myplex/account?X-Plex-Token=xxxxxxxxxx
You would need to put in the server security token instead of the xxxxxxxxxxxx - see https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
The logs show
At 21:34:55 Remote Access disabled and then re-enabled
At 21:35:05 connectivity test showed it was ok - through uPnP port 112280
Apr 05, 2019 21:35:05.857 [13392] DEBUG - EventSource: Got event [data] '<Message address="116.90.xxx.xxx" port="11280" asyncIdentifier="99ae7f8d-9f98-4ae9-897e-a4cd98a0fe0f" connectivity="1" command="notifyConnectivity"/>'
Apr 05, 2019 21:35:05.857 [13392] DEBUG - PubSub: Got notified of reachability for async identifier 99ae7f8d-9f98-4ae9-897e-a4cd98a0fe0f: 1 for 116.90.xxx.xxx:11280 (responded in 1 seconds)
After this you decided to switch from an automatic port mapping to have a manually specified port 32402
The first attempt to do a connectivity test to 32402 failed
Apr 05, 2019 21:35:44.970 [13388] DEBUG - EventSource: Got event [data] '<Message address="116.90.xxx.xxx" port="32402" asyncIdentifier="6c8c878c-2e1b-4b30-9273-d36124f49f48" connectivity="0" command="notifyConnectivity"/>'
But one later succeeded
Apr 05, 2019 21:38:38.611 [13392] DEBUG - EventSource: Got event [data] '<Message address="116.90.xxx.xxx" port="32402" asyncIdentifier="9e4aed03-a0b7-449c-af4f-54923d5a462b" connectivity="1" command="notifyConnectivity"/>'
Did you need to add the port forward for 32402 to 32400 in the router between 21:35 and 21:38 ?
Unfortunately when needing to investigate, it is necessary to know exactly what issue to look for and at what time.
Apologies for a lot of detail. May be the issue is simply that because you created the server afresh it got reset to uPnP port mapping rather than your manually specified port which you set up in the end at 21:38 on the 5th
HOME Server
Not sure what the issue was and when
On 1.15.2.793 there was a connectivity test to wan port 32401 and it was ok
Apr 05, 2019 21:10:06.013 [15476] DEBUG - PubSub: Got notified of reachability: 1 for 116.90.xxx.xxx:32401
Then restart on version 1.15.3.858
and connectivity tests were ok as well
Apr 05, 2019 21:11:05.816 [35828] DEBUG - PubSub: Got notified of reachability for async identifier d5d3f078-7cbb-4484-b18d-aa73836f8f30: 1 for 116.90.xxx.xxx:32401 (responded in 1 seconds)
Apr 05, 2019 21:18:06.351 [36084] DEBUG - PubSub: Got notified of reachability for async identifier 1c4cfe93-80da-47c3-8741-4242826340f1: 1 for 116.90.xxx.xxx:32401 (responded in 2 seconds)
Apr 05, 2019 21:18:23.832 [36084] DEBUG - PubSub: Got notified of reachability for async identifier df53f32c-5377-4a60-82f3-cce81b8d27f6: 1 for 116.90.xxx.xxx:32401 (responded in 1 seconds)
Apr 05, 2019 21:33:20.505 [35828] DEBUG - PubSub: Got notified of reachability for async identifier 02681162-a056-482e-850d-1c4e6a4c754e: 1 for 116.90.xxx.xxx:32401 (responded in 1 seconds)
What was the issue ? when ?
if you are getting remote access drop out or not getting enabled, get server logs and screenshots of settings in the router - with the logs captured at time of the issue arising or soon after
I’ve since checked from a variety of sources. Roku users can’t see the server. TiVo users can get it to work sometimes, but with drop-outs. Windows clients, and web users, can use it fine.
In the control panel, it goes green for four seconds, then goes red.
Which “guide link” are you talking about? This thread is 300+ posts long 
It stayed up all day today until 17:51. Then it started going up and down for the rest of the evening. I found a narrowed down period it occurs in.
The remote connection drops sometime between 22:33:00 and 22:34:26. It is re-established by 22:37:27.
DropOutLog.log (5.0 MB)
Am assuming he is taking about this one A definitive guide to remotely waking & sleeping your Plex Windows 10 Server via Remote Access & WOL
1 Like
Any luck finding anything in the log? This is from the 24th to now. Large blocks of time without any issue and then lots of switching back and forth.
I have looked at the logs and i can see you are using Tautulli to do a check every minute on the server connection. Of 33 tests between 22:08 and 22:40 the logs show that 15 external requests to your 47.145.xxx.xxx public IP and public port got through but 18 were not logged as being received by Plex Media Server.
This shows the outcomes of the 33 tests
Apr 23, 2019 22:08:35.151 [9960] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="decd3c03-cb89-4883-9684-7e066dc90fc3" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:09:35.199 [9960] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="927aa721-ac3f-4730-85ce-4126cdf14890" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:10:35.276 [9960] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="e0daa665-cba6-466e-9f1b-3b7d3c9c86f4" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:11:39.471 [9960] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="2b3729f5-5200-4723-9899-28181ee5d683" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:12:39.446 [9960] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="002c0128-d802-48c5-a747-9aea42a502df" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:13:39.355 [9960] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="870a4a86-2c48-4696-bb51-e8c97b655b8f" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:14:39.450 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="ebcd1a0c-4885-46ea-b8d0-0127604a4634" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:15:40.450 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="58b3bf47-1f0a-4798-97bd-9dfd3595efb2" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:16:35.132 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="1ec488a5-6fae-454e-8557-97db8f57ffa7" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:17:35.322 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="7468f952-83db-454a-bb5b-4da9ff9fa126" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:18:35.143 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="d32f569b-3d6e-4845-962b-635b9a2202d7" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:19:35.157 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="a043fced-6fc4-4f6b-af8f-c96ca83c1c20" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:20:35.112 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="a1357a65-9fea-428a-9e6d-a4b63a78c400" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:21:39.424 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="e3cd0fa2-5d8d-47c7-bce3-8c2b3adf00bb" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:22:39.306 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="088cae0f-c22d-4fe8-b851-34e01a92c927" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:23:39.433 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="3e2e9ac4-63b8-43e8-9ff1-5c806e0f6a82" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:24:39.440 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="3ed4f1d0-20e2-441f-8aac-ff332a6fc7fa" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:25:39.441 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="286943d6-fa4b-4c3b-9b58-8b97a3e77a10" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:26:35.159 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="f80210c8-3c90-4f9c-860a-47a8948b076e" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:27:35.167 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="23934eb5-6fa1-4334-8702-f6170566511d" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:28:35.115 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="083fcea2-9a97-4753-b85c-0dd960c923ee" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:29:35.211 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="628069f2-ff03-4966-96bc-b015daf598f2" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:30:35.150 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="da0cebfb-9d2c-444f-8026-1defdf9120c6" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:31:39.546 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="7f518859-907c-413a-aef9-543568d48679" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:32:39.439 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="b6735d04-8218-4fd2-be14-10303671adf5" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:33:39.290 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="6e55e834-a73f-4d5a-8412-34b5296a4020" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:34:39.302 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="a088ff08-f797-4b1c-8519-1bed0729b702" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:35:39.447 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="079172a0-a1a9-43b0-acbf-04f7c41f0dcd" connectivity="0" command="notifyConnectivity"/>'
Apr 23, 2019 22:36:35.140 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="c8772e4c-fa71-4770-9c6e-c501e4cbf2da" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:37:35.159 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="75360bc0-fef5-4adc-9c15-2f548de7ed83" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:38:35.402 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="3f734f7d-d104-4ac9-94ac-2cc1b711318a" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:39:35.144 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="f2d8f0b8-637f-4bc3-bfc4-192be8509f1e" connectivity="1" command="notifyConnectivity"/>'
Apr 23, 2019 22:40:35.155 [18140] DEBUG - EventSource: Got event [data] '<Message address="47.145.xxx.xxx" port="32400" asyncIdentifier="f505fcf6-3bcf-4635-8c11-d51e7cd8c826" connectivity="1" command="notifyConnectivity"/>'
Those that gave rise to a connectivity="1" event (i.e. a succes) can be seen in the log as receiving the connectivity check from one of the plex.tv systems, e.g. this test from plex.tv system 47.152.176.69
Apr 23, 2019 22:10:34.798 [90120] DEBUG - Request: [47.152.176.69:47430 (WAN)] GET /identity (45 live) TLS Signed-in Token (KnightCat83)
Apr 23, 2019 22:10:34.800 [18140] DEBUG - Completed: [47.152.176.69:47430] 200 GET /identity (45 live) TLS 2ms 385 bytes (pipelined: 1)
I have asked our plex.tv team to see if there were issues on April 24 between these times
05:11:35 am GMT to 05:15:35 am GMT and
05:21:34 am GMT to 05:25:34 am GMT and
05:31:35 am GMT to 05:35:34 am GMT
With regards to your router configuration - you should delete all the Port Triggering settings for Plex. What is needed is just Port Forwarding - forwarding 32400 to 32400 to the local IP of the server
I do not know what impact this would have but it is wrong and there should be no Port Triggering
OK, I’ll remove the port triggering and let you know if it appears to have any impact.
Yep, this describes me too. I’ve literally just built a new server on new hardware and I was looking forward to stress-testing it, however me and my family can’t even access it apart from on localhost.
I’ve sent a DM to Elan (CTO) in the hope he sees it asking about this. I understood the fruore surrounding the interface changes a while ago, but also understood that sometimes design decisions are made and they’re wrong. Elan was man enough to own up and accept that. However in this instance, this is Billy basic functionality of the service. It’s literally the entire point of Plex. And it’s not working.
For this to have been going on for as long as it has without any kind of comment is, in my opinion, totally unacceptable and more evidence of what I said the main issue was earlier - incredibly poor communications between the company and the customer.
would need to see logs again and establish which pubsub server is being used.
I notice 2 active network interfaces on the server. Could you disable the one that does not have the port forward and see if it becomes more reliable
Can you actively check that? That would not have been in the log I provided before. I just added that new NIC this weekend to see if splitting the PMS from the other services would improve things.
Remote Access was down as I started writing this so, I tried disabling and re-enabling it (which sometimes works for a bit but didn’t help this time.
Log attached.Plex Media Server.log (3.5 MB)
plex.tv has info on the public IP and port if remote access is enabled and also has the local network ip addresses which plex clients on the local network use for connecting to the local server.
We need to establish if this is really remote access going down or just the connectivity tests mechanism, that I presume Tautulli is instigating every minute, has a problem getting actioned correctly every time.
It may be just that the indicator that you are looking at through Tautulli that is inaccurate rather than that you have actually lost remote access.
The log does show that some of these minute by minute requests to do a connectivity test have failed.
Connectivity Tests from plex.tv reached the server at these times 17:42:09, 17:43:09, 17:44:09
Connectivity Tests from plex.tv were not seen by the server at these times 17:45:09, 17:46:09, 17:47:09, 17:48:09, 17:49:09
Connectivity Tests from plex.tv reached the server at these times 17:50:09, 17:51:09, 17:52:09, 17:53:09, 17:54:09
Connectivity Test from plex.tv was not seen by the server at this time 17:55:09
After this you disabled and re-enabled remote access and captured the logs at 17:56
There is a potential problem in that having a failed connectivity test could make further attempts to connect to the server fail. I am not seeing this in your logs and in any case a change will be made to plex.tv soon to ensure that a failed test would not impact future connection attempts to the server
You can try the following when you notice Tautulli (or whatever you are using to check every minute) indicates Remote Access has dropped out:
- Use a mobile device with Plex app to try and access your server through cellular or remote WiFi.
If this fails, get the logs from that device through the App Settings / Help / Email Device Logs to your email address
Also if the connection from the mobile device fails, get the resources.xml info from plex.tv by running this in a browser
https://plex.tv/pms/resources.xml?includeHttps=1&includeRelay=1&X-Plex-Token=xxxxxxxxxxxxx
You will need to put in the server token instead of the xxxxxxxxxxx - see https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
Copy the response xml to a text file and send me privately in Private Message.
and collect the server logs as well
- If the test from the mobile device through cellular or remote wifi works, then it suggests that the issue is just the mechanism that Tautulli (or whatever you are running) is using every minute that is not reliable and has operational issues - that we can have looked into - would need to know what pubsub is in use and the server logs as before
The IP Address of the pubsub server in use is logged when the server starts and also if it changes. The registry entries inHKEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Serverwould hold the info. You can export to text and zip and send me privately
When doing the mobile device test you can also do a manual check yourself to eliminate the router by going directly to the public ip:public port url yourself from remote wifi or cellular http://47.145.xxx.xxx:32400/web and see if you get through and requested to authenticate - subtitute the IP Address that shows on http://canyouseeme.org for the 47.145.xxx.xxx
One other thing - could you purge the old instance of your server on your account.
In Plex Web, Go toSettings / Authorised Devices / In the drop down at the top select Server instead of All and click on the red x to remove the old server instance
here is the deal as i see it with most of the folks having issues.
up until a recent update all was good.
plex pushes out a update and it breaks remote access.
nothing has changed on the users end other then applying a new pms update.
so why would it have anything to do with how they have things set up?
something in your code broke things just like it has in the past.
making folks jump thru hoops other then sending logs is a waste of time.
so either roll things back to when things were not broke or get a patch out to fix things.
i run 2 servers…got two friends in nearby towns who also run servers…mine are win 10, one is linux and one a NAS…and all of them are suffering from this remote access BUG.
this is not an isolated incident involving a couple of users.
I’m on the road at the moment for work and will have to do the more detailed stuff when I get home but I can tell you that it’s not just appearing to be unavailable. I have some friends and family that use the server remotely (as well as I do when travelling like this) and I have seen it go completely offline for remote access (happened to me last night). I then use a remote desktop to connect to the server, disable and re-enable remote access, and if I’m lucky it stays up and a few minutes later I can connect with my mobile device again.
