Here are the debug logs after remote connection dropped.Plex Media Server Logs_2020-04-26_11-47-49.zip (3.7 MB)
Mine works for minutes or hours then shows āNot available outside your networkā,ā¦ never had a problem for years. The strange thing is that it is available as I can connect from remote,ā¦ with the acceptation of once last night when Tautulli notified me āThe Plex Media Server remote access is down.ā
@sa2000 Plex Media Server Logs_2020-04-26_10-46-53.zip (4.4 MB) These logs show pms on v1.19 remote access going down
Plex Media Server Logs_2020-04-26_15-14-05.zip (1.1 MB) I back-dated to v1.16 and remote access doesnāt go down.
Iām having this issue too. Canyouseeme says the port is visible and not blocked, but the Plex server Remote Access goes green for a second, then turns red and says not accessible. Running Version 1.19.2.2702 on an iMac, had Remote Access working fine for years. Iāve never had to touch it or change my port forwards since setting it up. Now seeing the exact symptoms others mention: Goes greenā¦two seconds later goes red.
same here, same port forward that has always worked in my router. canyouseeme says open. I get a bit of green if I mess with it briefly, then red. sometimes available outside, sometimes not.
Yep, this definitely seems to be a problem. Downgraded to plexmediaserver-1.19.1.2645-ccb6eb67e.x86_64.rpm and donāt have issues anymore.
My Plex sits on a linux box with direct access to a global IP. No firewall.
What do you mean?
The logs show that remote access connectivity test requests were not reaching the server
Apr 25, 2020 19:12:31.917 [0x7ff3d636f700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="1d1e01b8-51e8-4f66-8d35-0e4a85d88aaf" connectivity="0" command="notifyConnectivity"/>'
Apr 25, 2020 19:12:47.483 [0x7ff3d636f700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="7504549b-1989-43b6-bfe4-86e08760b190" connectivity="0" command="notifyConnectivity"/>'
Apr 25, 2020 19:13:04.020 [0x7ff3d665d700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="f44db7f6-e7a5-4171-877b-014e7ea0cba1" connectivity="0" command="notifyConnectivity"/>'
Apr 25, 2020 19:13:34.810 [0x7ff3d636f700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="a19b5565-1b26-4a6c-92c5-0961ff068a54" connectivity="0" command="notifyConnectivity"/>'
This continued after restarting the server
Apr 25, 2020 19:16:26.129 [0x7f813e2f5700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="2e71a4d2-af06-4023-9002-4b2709b95ba5" connectivity="0" command="notifyConnectivity"/>'
Apr 25, 2020 19:18:09.838 [0x7f813e2f5700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="a3fd1899-3a9c-405a-9f50-65fdedb13af8" connectivity="0" command="notifyConnectivity"/>'
Apr 25, 2020 19:18:26.767 [0x7f813e2f5700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="18820845-c5a1-4a41-aa6f-0fefaeb55e15" connectivity="0" command="notifyConnectivity"/>'
Apr 25, 2020 19:18:46.598 [0x7f813e2f5700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="e21980ba-077d-4e33-ab11-f9d1676b33ee" connectivity="0" command="notifyConnectivity"/>'
Apr 25, 2020 19:19:35.754 [0x7f813e007700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="800e9faa-ca68-4317-84d6-1c3f3d97fe5a" connectivity="0" command="notifyConnectivity"/>'
Apr 25, 2020 19:29:33.879 [0x7f813e007700] DEBUG - EventSource: Got event [data] '<Message address="101.118.xxx.xxx" port="32400" asyncIdentifier="fb3beefb-c714-43b7-8893-de647d4ff8e5" connectivity="0" command="notifyConnectivity"/>'
It is not possible to determine why without a network packet capture - like wireshark
See if you can provide me a pcap file for capturing all traffic on all the network interfaces for the server
Apr 25, 2020 19:16:09.598 [0x7f8148a71740] DEBUG - Network interfaces:
Apr 25, 2020 19:16:09.598 [0x7f8148a71740] DEBUG - * 15 br0 (192.168.3.106) (loopback: 0)
Apr 25, 2020 19:16:09.598 [0x7f8148a71740] DEBUG - * 16 docker0 (10.0.5.1) (loopback: 0)
Apr 25, 2020 19:16:09.598 [0x7f8148a71740] DEBUG - * 17 lxcbr0 (10.0.3.1) (loopback: 0)
Apr 25, 2020 19:16:09.598 [0x7f8148a71740] DEBUG - * 18 qvs0 (192.168.3.2) (loopback: 0)
Apr 25, 2020 19:16:09.598 [0x7f8148a71740] DEBUG - * 19 qvs1 (192.168.4.1) (loopback: 0)
together with server logs next time this happens
Please zip the pcap file and upload to dropbox/google drive and send me link by Private Message with the server logs (with verbose logging enabled as well as debug)
The only wan connections to the server I see for the evening of the 25th are actually coming through 192.168.3.106 - do you had a forward / proxy as the requests are flagged as WAN even though 192.168.3.xxx is a local subnet
Are you able to get network packet capture during the time when this happens ? If you can, please also run with verbose logging enabled on Plex Media Server and let me have the server logs zip and send me privately a zip of the network capture pcap file
Does the issue affect remote access or is it just the status indicator being wrong and saying server is unavailable ?
in my case it is the indicator
look at my capture
I was also experiencing that issue and it seems that disabling DDOS protection on my Asus Router (RT-AC87U with latest Merlin FW) did worked for me. Now solid green since then. Iāve starting having issues mid march. Server was working remote intermittently. Virtual ports are configured manually (no UPnP). I would prefer to have it enabled but for now I will let it disabled. However, I may find a way to whitelist my Plex Server.
FYI, my Plex server is running on a Exsi VM on Windows Server 2016.
I have downloaded the same version and it works without problems, you are right
I was going to post a similar screenshot showing Plex says not available, canyouseeme shows the port available, etc.
@vanhoteen - maybe you should blur or cover up the Public IP address in those screenshots. Iām not sure, but I think it would make it easier for anyone to hack in with that info easily available.
thanks DONāT THINK SO, I thought it was in the family.
the hidden
My Asus router with Merlin FW has DoS protection disabled by default.
what version of plex server do you have and on what device windows, linux, nas.
The same happened to me .
I have downloaded the plexmediaserver_1.19.1.2645-ccb6eb67e_amd64.deb
then downgrade.
everything fine without problems it worked fine but for security I uploaded the version
and then upgrade to VersiĆ³n 1.19.1.2701
it seems that now it works it takes an hour without error
This is all strange since we have users with similar end symptoms but running the version you have downgraded to and ok now - so there are probably different causes for similar outcomes
Thanks you - this does show an issue at 01:13:56 am April 25 - but it is different from what I saw in other users logs
I am referring this to our development team as we appear to have lost the remote access status
You think someone from PLEX SUPPORT would address this situation.
I have found on some of the Plex updates the remote works for a period of time (sometimes up to 4 or 5 hours) but it eventually goes back to red and I no longer have access
