Server Version#: Versión 1.19.2.2673 , Ubuntu
Player Version#: android phone or sony TV or LG
It says “Your server is registered with Plex, but it is not accessible outside your network.”
Automatic port, I have been years without problems, after the last update, although not if it is the reason, because now it gives this so rare error.
it says it has no connection but then it works.
Log files please?
I have checked the firewall, the router port, I have called the internet company to see if it had a unique public ip. and it only turns green and red varying
Plex Media Server.log (9.3 MB)
It’s complaining because, apparently - but I can’t see with just this one log file - it’s requested a port map (UPNP) but the UPNP hasn’t replied.
It therefore fails the reachability test (return = 0) and this is what you see.
Apr 25, 2020 20:20:15.572 [0x7f42660fb700] DEBUG - Auth: authenticated user 1 as vanhoteen
Apr 25, 2020 20:20:15.573 [0x7f42660fb700] DEBUG - EventSource: Got event [data] '<Message address="" port="0" asyncIdentifier="1368c9a7-90cc-4aa9-b579-5776c372d6ca" connectivity="0" command="notifyConnectivity"/>'
Apr 25, 2020 20:20:15.573 [0x7f42660fb700] DEBUG - PubSub: Got notified of reachability for async identifier 1368c9a7-90cc-4aa9-b579-5776c372d6ca: 0 for :0 (responded in 3 seconds)
Apr 25, 2020 20:20:15.573 [0x7f42660fb700] DEBUG - MyPlex: inaccessibility report ignored because NAT punch is still pending.
Apr 25, 2020 20:20:15.573 [0x7f4219ff3700] DEBUG - Request: [192.168.1.15:60663 (Subnet)] GET /myplex/account (17 live) TLS GZIP Signed-in Token (vanhoteen)
If you don’t need automatic Remote Access, then don’t worry about it.
There are some users who use IPSEC tunnels and VLAN to accomplish the same task.
I understand that it is a mistake, I do not have to worry.
hope the next update works,
my brother needs to see my plex server, this is fine, right?
sorry for my English 
Plex Media Server Logs_2020-04-26_01-08-17.zip (6.1 MB)
For something that I do not know, the router of the company was playing, I have reset and configured my ip again by dmz, now it seems fine.
I’ll be vigilant if it fails.
after an hour it gives me the error with the router again, the web says open, the plex says error, but it works from the outside, there is a reproduction from my phone with 4g android
Continue with this error and everything after the last update, someone can tell me how I reported the problem to plex
i have seen a new update i am testing
plexmediaserver_1.19.2.2702-776106bc6_amd64.deb
I have updated and it keeps giving me the same error. 
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
@vanhoteen I can see dropout of TLS connections around the time when the status go unavailable - this is similar to one I have been investigating but it was the only one I got a network capture for - so I really need to have more evidence of the same underlying issue affecting more than one user
This extract shows a good connectivity test and then aborted tests and failure event
Apr 26, 2020 00:52:51.584 [0x7f4245ffb700] DEBUG - Request: [54.171.49.143:52586 (WAN)] GET /identity (15 live) TLS Signed-in Token (vanhoteen)
Apr 26, 2020 00:52:51.585 [0x7f42668fc700] DEBUG - Completed: [54.171.49.143:52586] 200 GET /identity (15 live) TLS 0ms 398 bytes (pipelined: 1)
Apr 26, 2020 00:52:51.670 [0x7f42668fc700] DEBUG - EventSource: Got event [data] '<Message address="213.195.xxx.xxx" port="29408" asyncIdentifier="6dfcee62-3360-4a02-9c18-75424726c319" connectivity="1" command="notifyConnectivity"/>'
Apr 26, 2020 00:53:06.171 [0x7f42668fc700] VERBOSE - We didn't receive any data from 54.171.49.143:51780 in time, dropping connection.
Apr 26, 2020 00:53:07.510 [0x7f42668fc700] VERBOSE - We didn't receive any data from 54.171.49.143:51068 in time, dropping connection.
Apr 26, 2020 00:53:08.161 [0x7f42660fb700] VERBOSE - Didn't receive a request from 54.171.49.143:51780: End of file
Apr 26, 2020 00:53:08.763 [0x7f42668fc700] VERBOSE - We didn't receive any data from 34.243.160.122:35996 in time, dropping connection.
Apr 26, 2020 00:53:10.510 [0x7f42660fb700] VERBOSE - Didn't receive a request from 54.171.49.143:51068: stream truncated
Apr 26, 2020 00:53:10.675 [0x7f42668fc700] VERBOSE - We didn't receive any data from 34.245.172.51:44778 in time, dropping connection.
Apr 26, 2020 00:53:11.545 [0x7f42660fb700] VERBOSE - Didn't receive a request from 34.243.160.122:35996: End of file
Apr 26, 2020 00:53:11.585 [0x7f42668fc700] VERBOSE - We didn't receive any data from 54.171.49.143:52586 in time, dropping connection.
Apr 26, 2020 00:53:11.889 [0x7f42660fb700] VERBOSE - Didn't receive a request from 54.171.49.143:52586: End of file
Apr 26, 2020 00:53:12.134 [0x7f42668fc700] VERBOSE - Didn't receive a request from 34.245.172.51:44778: End of file
Apr 26, 2020 01:04:30.827 [0x7f42668fc700] DEBUG - EventSource: Got event [data] '<Message address="213.195.xxx.xxx" port="29408" asyncIdentifier="bff44bc0-96b7-4464-901b-f297875ed300" connectivity="0" command="notifyConnectivity"/>'
I have not established yet if this is caused by a Plex Media Server change or our back end systems that send the connectivity tests. A packet capture covering period as in this log extract above together with logs would confirm that this is the same issue I am looking into which appear to fail during TLS dialogue
Did you say you downgraded and the problem went away ? what version ? and can you go forward to establish when the issue came in ?
@vanhoteen I just read your post about versions - so what you are saying:
Problem happens on 1.19.2.2673-776106bc6
Problem does not happen on 1.19.1.2645-ccb6eb67e and 1.19.1.2701-6327e27bf
I have been having the same issue of sort and the only way i could fix it was to disable UPnP and NAT- PMP. Manually port forward, save, restart everything and everything back to Gold/Green sorry.
Version: 1.19.2.2702
There may be several issues
The one I am looking into is a failure during SSL TLS cipher key dialogue for the connectivity test requests. But I have had only one network trace so cannot say if this is the problem affecting others as well
There a new TLS setting in Server settings now mentioning this subject. Could this be the issue?
Disables the deprecated TLSv1.0 and v1.1 protocols, as well as legacy weak ciphers. May prevent older clients from connecting.
@sa2000 Will these logs help?
PMS 1.19.2.2702 on DS918+
Static IP on DS918+, fixed port forwarding statement in router, UPnP disabled in router.
That’s right that’s what happened to me
Problem happens on 1.19.2.2673-776106bc6 and 1.19.2.2702-776106bc6
Problem does not happen on 1.19.1.2645-ccb6eb67e and 1.19.1.2701-6327e27bf
i’ve had this issue for the last few days and it was pretty much driving me crazy this last weekend, mainly because i had moved to a new router 2 weeks ago (from a tp-link to ubiquiti dream machine) and in my mind, this just had to be some problem with my new hardware (despite it had been working just fine the first week or so.).
anyway, it’s still happening with pms 1.19.2.2711 that was pushed this morning. i’ve been running verbose logs for most of today, so i’ve grabbed them and attached them here if it helps you research the issue.
my pms is on a windows 10 PC
router is a UDM pro, port is forwarded and no UPnP
no VPN
hope this helps.
I can see the same issue as that in logs from @Steve_Davis and @spdelope in this forum thread Remote Access connects for about 15 seconds then disconnects
This was at 23:10 on April 25 where the Tautulli checks were ok up to 23:09.
I have referred this to the Plex Media Server development team.
Am I right in saying that this specific time problem resolved itself at 00:42 April 26?
But arose again at 01:10 and subsequently as well
I am not sure at this point if the minute by minute check by Tautulli is compounding the issue
