Mine is better, still shows not available for a few seconds when I access the page, then goes green.
then I have the green checkmark next to remote access.
That is how it is
At the moment every hour we re-instate any uPnP port mapping and in all cases - port forward or dynamic port allocation, we check the public IP address but the server remote access status becomes in a state that needs verification after this and this only happens when server setting page is opened in Plex Web when a connectivity test is actually made and the status corrected.
Have updated but mine is still showing as Not available outside of your network. Using Retry to update the status doesnāt reset it. Not sure if itās related to the TLS dropped connection issues.
It could be due to the aborted connectivity tests when the TLS connection is dropped. This issue is still outstanding and I need to see more packet captures and logs from other users
We can see if it is still that issue for your server from verbose logging and server logs to see if any dropout in connections from one of the 6 IP addresses used for connectivity tests
Do you need the packet capture and TLS logs or just the server logs?
I already have packet capture from you - I think just verbose logging when attempting the retry / reconnect on remote access page
Have sent logs to you. There was some weird behaviours with Plex so I kept the logging going a little longer.
Thanks - yes it is the issue that you had before - aborted TLS connections
We have now found the cause. TCP connections for these requests are being timed out after 1 second and the TLS dialogue sometimes takes about 1 second - we are increasing this timeoutā¦ That explains why disabling secure connections fixed the problem for one user - because http requests are faster than https requests.
I will let you know when that change is live
2 Likes
I donāt know if Iām having the same problem all this talk about networks connections and port is all very confusing to me. yesterday plex was working fine and now remote access doesnāt work. Iāve got it to connect to for a little bit but anytime I go into settings it kicks me off of remote access. when it does say its connected anyone trying to watching something from an outside network gets automatically transcoded to SD not matter if they have their settings for higher quality. In windows my firewalls are turned off and my router settings are still the default settings Ive always had for the past two years.
The recently released update works for me, Thanks!!
I have a different problem that has popped up. I have updated and reviewed all the trouble shooting links. My remote now stays green, but Plex is always on relay. I have tied everything so far, reserved ip, port forwarding, firewall settings, etc. I have trouble even logging in on my Shield sometimes that is on ethernet (it says not connected to network), but my family can log in on wifi across town at the same time. My Plex app on my Vizio tv on wifi can access some of the time, but the Shield on ethernet wonāt. I am on Windows 10, with my server on my HP i5 laptop.
Sadly i have the same problem with āNot available outside your networkā.
The change to the back-end systems that do the connectivity testing to the Plex Media Server went live last night.
I am keen to see if the TLS dialogue aborts during the connectivity test requests have now stopped
Still experiencing issue with remote access indicator. Iāve captured the logs and will send to you via PM.
Thanks - it looks the same as before with the connectivity test requests aborted
These coincide with the times when a connectivity test request was being made from these back-end systems
May 05, 2020 23:24:47.752 [0x7f044efc2700] VERBOSE - Didn't receive a request from 34.245.172.51:56012: stream truncated
May 05, 2020 23:25:19.528 [0x7f044f7c3700] VERBOSE - Didn't receive a request from 54.171.49.143:34078: stream truncated
May 05, 2020 23:27:14.632 [0x7f044efc2700] VERBOSE - Didn't receive a request from 34.243.160.122:39274: stream truncated
May 05, 2020 23:30:10.875 [0x7f044f7c3700] VERBOSE - Didn't receive a request from 63.34.171.72:43336: stream truncated
May 05, 2020 23:30:34.394 [0x7f044f7c3700] VERBOSE - Didn't receive a request from 34.248.59.52:46736: stream truncated
I have referred it back to our plex.tv team
Thanks for getting the logs and doing the test
1 Like
Iāve not had many issues with remote access, but for the last two days (I assume since the back-end change) tautulli has been reporting remote access down every hour at xx:04:xx
If you donāt mind I have the same problem can you tell me what older version of Plex you are referring to I would like to give it a try also.
I can access Plex remotely when it is red only some of the timeā¦like so many others it starts out green and then within 10 seconds it turns to redā¦sometimes it stays green for up to 8 hours but eventually turns to redā¦its a shame Plex technical support doesnāt address this issue especially when thousands of Plex users are having the same remote access issue
There is a specific issue with timeouts on connectivity tests coming from the plex.tv Amazon Cloud hosted servers in Europe - I have seen this from 6 users - 5 are in New Zealand / Australia / Singapore and Malaysia and 1 in the US.
I would like to see logs from more users - with verbose logging during the time when server settings is open and it is expected to be green and it is not
Is there an issue with losing remote access - or is it just the indicator that is wrong ?
This has happened to me in the last few days. I get an alert that remote access is down. It almost immediately comes back (1-10 min later). If I manage to check remote access while itās ādownā, itās working. I set up an external monitor on my external port (via UptimeRobot) and it never alerts. Finally, If I manage to log in and pull up the web UI and āretryā itāll immediately green up again. Everything I can see is that itās a false alarm.
Iāll try to provide logs the next time it happens. Itās happened at exactly 22:55 GMT the last two days. Maybe itāll happen again today.
