Up and running only changes I made was DNS moved for 1.1.1.1 to 8.8.8.8 than to open DNS. 
I started having this problem in the last few days. Again, the only things that changed were a Windows update and a Plex update. It reports that it is not available outside of my network, and when I try it via my phoneās 4G connection, all I get is the freebie Plex stuff like the podcasts/etc.
I did a disable/enable cycle, and it shows green/connected for about 3 seconds, and then it shifts to red/not-connected. It gives me this message:
āYour server is signed in to Plex, but is not reachable from outside your network. [Learn more]ā
I have tried this with port forward on and with it off. Same result.
Plex Version 1.19.1.2645
Windows Version 10 Pro 1903, build 18362.778
I donāt think Iām running any add-ons. Itās just a vanilla Plex installation.
Why is this broken, and if you guys canāt fix it on your end, what am I supposed to do on my end?
-Dan
1 Like
Thanks for the new logs. The connectivity tests are still not getting through and these would result in the remote access setting to show as unavailable
I can see remote requests active during these periods
Plex Web on Google Chrome From Apr 16, 2020 19:49 to 19:57 from IP 1.127.xx.xxx
Plex for Android on Galaxy S9 from Apr 16, 2020 20:44 to Apr 17, 2020 16:43 from IP 123.209.xxx.xxx
And from April 17 18:12 to 19:17 from IP 120.157.xxx.xxx
I would like to establish if there is an issue with our back end systems in sending out connectivity test requests.
Are you able to run packet capture applications on the QNAP capturing all packets received on the local network interface that the port forward is set to (192.168.3.2)?
If you are I would like you to do that whilst a Plex Web screen within the local network is displaying the server settings page and send me zipped pcap file in private message together with the corresponding server logs
Thanks for this and the fresh logs.
The syslog plex_nat.txt file does show the connectivity requests. What timezone are these entries in?
The server log you provided with it was captured at 14:55 local time on 17th April. The last entry in the plex_nat.file is timestamped 00:11:40 17 April. What time was this log captured
the Server log covers period 02:04 to 14:55 on 17 april. Only connectivity request seen by the server was 05:59 am
Apr 17, 2020 05:59:23.957 [0x7f2de92dd700] DEBUG - Request: [34.248.59.52:33128 (WAN)] GET /identity (5 live) TLS Signed-in Token (markstubb)
which is from a different IP from those in the plex_nat.txt file for the 17th and the server log shows connectivity tests at 14:55 that did not get a connectivity test request. So I need to see matching syslog and server logs and what timezone / local time the router is running at as I believe that would be the time that shows in the log
These are the only 17th April entries in the nat log
Apr 17 00:11:08 SHRouter kernel: [WAN_IN-3003-A]IN=pppoe2 OUT=eth0 MAC= SRC=34.243.160.122 DST=192.168.15.20 LEN=60 TOS=0x00 PREC=0x00 TTL=34 ID=18628 DF PROTO=TCP SPT=40650 DPT=32400 WINDOW=7300 RES=0x00 SYN URGP=0
Apr 17 00:11:16 SHRouter kernel: [WAN_IN-3003-A]IN=pppoe2 OUT=eth0 MAC= SRC=34.243.160.122 DST=192.168.15.20 LEN=60 TOS=0x00 PREC=0x00 TTL=34 ID=59296 DF PROTO=TCP SPT=46094 DPT=32400 WINDOW=7300 RES=0x00 SYN URGP=0
Apr 17 00:11:40 SHRouter kernel: [WAN_IN-3003-A]IN=pppoe2 OUT=eth0 MAC= SRC=52.16.207.132 DST=192.168.15.20 LEN=60 TOS=0x00 PREC=0x00 TTL=34 ID=32505 DF PROTO=TCP SPT=48786 DPT=32400 WINDOW=7300 RES=0x00 SYN URGP=0
Making Plex accessible outside my network required me to select āManually specify public port.ā Then, the access disabled after 10 seconds.
The fix seems to be to create a rule in the Windows Defender firewall to open inbound local port 32400 TCP, as sa2000 mentioned. Thanks for the help!
Nevermind. That didnāt do it.
The fix seems to be in setting up my router for port forwarding for 32400. Fingers crossed!
A Port Forward and manually specifying the public port is more reliable - but we have had cases of ISPs resetting their routers during updates and losing port forwards
Make sure also your local IP address that you are port forwarding is a DHCP Reservation or static outside DHCP range
This just started happening for me after upgrading the server to Version 1.19.2.2673. Nothing has changed on my network side and it was fine before this.
2 Likes
Also having an issue after the last patch or two. Iām getting remote access is down errors from tautulli every 15 minutes.
1 Like
I am having the same issue here, although mine only connects for a second, as you can see the screen video noted in this post. I thought it was my new VPN, but I am still having the issue when I go back to my standard setup, which worked great before.
So even though i keep getting these errors and the settings say that there is no remote connection available, i have multiple people watching stuff and no one has asked me about any issues.
It could be just the connectivity testing that is failing - I have been investigating an issue raised by @kesawi but we got to a point where network packet capture was required together with server debug and verbose enabled logs covering the time when server settings were displayed and the status switching from green to red
I would like to see more examples to establish if we have the same underlying issue affecting users - so if you can provide me with a pcap file as well as server logs and do a test - with both verbose and debug enabled then I will look into it
this has started happening to me on Unraid as well. Official plex docker. Users can successfully access my server, however the check mark never automatically turns to a green tick, i need to click retry, it then turns green after 5 secs , and then 5 secs later turns back to a red x. i can successfully access my server using my dns domain and am challenged with a login screen. I disabled my tautulli notifications because i was getting spammed with server down/server up messages for the last 2 weeks or so.
What do you need?
1 Like
I want to establish if it is the same underlying TSL negotiation issue that was in the diagnostics from kesawi
I need network packet capture - are you able to provide that ?
This would be together with server logs
So to start with - enable both debug and verbose logging on the server
See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
(at the end of collecting diagnostics for this - remove verbose logging setting leaving only debug enabled)
With network packet capture in place and running, launch Plex Media Server, wait few minutes and then open the remote access server setting page and see if it goes from Green to Red
Stop the network packet capture and save into a pcap file and zip and send me by Private Message and also collect the server logs zip
See https://support.plex.tv/articles/200250417-plex-media-server-log-files/
(I will be sending you a private message with some additional instructions and you can reply to that)
Ive seen the dropout before lasting 5 to 10 secs and no remote access. Theres is only one change that fixed my issue and thats in Settings>Network settings>Secure Connections : Disabled (Select Disabled)
When I have this Enabled the drop outs start up again.
Hope this helps.
1 Like
the issue seems to have self resolved itself, its now reporting as a green tick???
I am having the same problem with binhex-plexpass docker in Unraid, and I have tried everything:
-
rolled back to previous version of docker (version 1.91.1.2630-1-01)
-
restarted the server, docker and router
-
confirmed the port is open on router with canyouseeme.org
-
the remote access keeps going back and forth from accessible to inaccessible and remote users are only able to stream at 1-2mbps with buffering
I have not had an issue for >2 years with 3-4 people remote streaming at 4-8mbps at once.
I am using linux (ubuntu 16.04). Installed plex about a month ago to use with my echo speaker. It all worked fine until last week. Now shows green for a few seconds then turns red. Alexa reports that it is online but not available. The only change I know of is an update to plex. Tried reinstalling the earlier version, but that didnāt help. I am in Canada, so not xfinity/comcast, etc. Mine is a plain vanilla installation (no port forwarding, etc.)
To start an investigation need server debug logs
After that then depending on what I see, may then need to have network packet capture as well as outlined here Remote Access connects for about 15 seconds then disconnects
Followed some other ubuntu-specific suggestions (unchecked 'enable the dlna server) and now the earlier version (1.14.1) is working. I am reluctant to tamper with it.
Sorry, I have alot off unsure traffic locally. Itās dropping out again, hope Plex cant get a fix soon. Plex Media Server Logs_2020-04-25_19-30-41.zip (5.4 MB)
