I would like to see a log of this with verbose logging enabled to see if we are getting aborted connectivity test requests from the servers located in Ireland
We are getting an event saying a test request could not reach the server - but it may have been a timed out/aborted one
I see that your server is in Australia - so most likely the same issue seen on other systems - is this having an impact on the operation of remote access ? is it just the status indicator / alerting by Tautulli ?
I also have this issue in the US. I have a pfsense router with port forwarding to my plex server. I get the green check mark in plex. I also have pfBlockerNG running and created a rule to permit inbound from the plex servers listed in the link.
Iām still getting multiple emails from tautulli that remote access is down and then I get one that itās up 3-5 minutes later. The tautulli log shows
2020-05-21 10:20:32 - WARNING :: Thread-20 : Tautulli Monitor :: Remote access failed: Plex remote access port mapped, but the port is unreachable from Plex.tv, ping attempt 6.2020-05-21 10:21:32 - INFO :: Thread-15 : Tautulli Monitor :: Plex remote access is back up.
If I try to stream on my cell during one of these episodes it works despite being down.
I have downloaded the new version of Plex Media Server: Version 1.19.3.2843 is now running
As soon as I downloaded this version the remote access had green light a little bit longer than few seconds but it eventually went down again. Tried to reconnect, would drop after 2 or 3 seconds again.
I will report the logs with verbose on
I do not have Tautulli, never downloaded, never used. This is actually the first time I hear about this tool
Just wanted to check in for an update on this - as others in the US are also experiencing this issue, just wnat to see if thereās an update or more I can do on my end. Today is partiuclarly bad so far of it āflappingā.
This just started happening to me last night. Iāve never had a major issue with the Remote Access going off so often, just once in a great while. But it would not stay on at all for more than a few seconds. After having no luck rebooting pc and router, I rolled back to .2843 where I had no issue. It is now running fine with that ā¦for the moment anyway, I was not aware of the CanYouSeeMe tool until now, good to know. I did however have MANY Tautulli Remote access failed & Remote access back up messages.
Also uptimerobot.com. Works like canyouseeme.org, but repeats every few minutes. Sends you an e-mail when it detects a service disruption / restoration.
Iām far from technical but I am suffering from Remote Access issues, I go to watch my content and I get errors - so I have to log in and go to the setting and that seems to be enough to reconnect everything but itās frustrating. Is there an actual fix to this or is it a software issue? If anyone can explain a fix in very simple terms Iād be extremely grateful.
If I need to provide more detail, let me know.
(Also my content never starts from the resume point, always from the beginning, even though I select the former - if anyone has any ideas on that.)
I too am having this issue. It was working fine up until a week or so ago. I am on 1.19.3.2852. Hereās whatās curious about my issue. It seems to work correctly via iPad or Android TV, but will no longer stream to any of my 4 Roku devices. Via Roku I can login and make the connection to the server, and browse titles, but it simply wonāt play any of those titles. Also, I host a Plex server, along with hosting 2 Plex NAS server devices (both approved and on the Plex list of viable devices). One NAS functions normally. The other has dropped connection on my account, and I cannot get it to show, even though the app manager software shows me it is up and running. I have also experienced a TON of port 32400 attacks from IP addresses originating all over the world, but primarily from Ireland. I did change passwords multiple times, but the attacks arenāt letting up. I purchased a lifetime PlexPass, but will have to switch over to PlayOn if this nonsense continues.
Yeah the brute force attacks were relentless. You can change the port to non-standard but it still has limited effect. I normally ignore the noise and rely on strong passwords but in this case I ended up using a combination of tcp wrappers and fail2ban
Are you sure these are attacks and not the connectivity testing for remote access which are done when the server setting screen is opened or if you run tools such as Tautulli - the tests would be from Amazon servers hosted in Irealand - current IP addresses available through a link on this support article
Please make sure you are not blocking any of these
If you have a specific issue with a client app not connecting, please re-authenticate the app by signing out and in and if problem persists, get logs from the server and the app and indication as to what the issue was and exactly at what time
Does this mean that the Plex Media Server is accessible remotely from the plex app but when you start watching, you get an error ?
What Plex app ? version ? and what error ?
so I have to log in and go to the setting and that seems to be enough to reconnect everything
login where ? in a Plex Web session? and displaying server settings page and doing nothing else ?
You say āreconnect everythingā - so was the app that you were watching content through disconnected ?
Is this repeatable ? Could you get me server and client app logs of this sequence and indicating what time the errors arose, what the errors were and what time the settings page was opened and the watching content started to work again
I suggest splitting this up into a separate forum topic providing server and plex app log and details of what was being played and what it should have resumed from
Last logs I have (and apologies for not getting back to you soon after you posted) show that all remote access connectivity tests failing
Edit: I can now see evidence of aborted connections for the remote access connectivity testing
Period between 02:02 am 21 May and 23:46 22 May
public port used was 32410 so router should have had a port forward for 32410 to 32400 to LAN IP 192.168.0.10
Period between 23:46 May 22nd and 23:50 May 22nd
public port used was 32400 so router should have had a port forward for 32400 to 32400 to LAN IP 192.168.0.10
Edit: I could not see an aborted connection for the last failure - but I can see it now for the earlier ones
May 22, 2020 23:45:58.619 [17992] VERBOSE - We didn't receive any data from 52.16.207.132:60618 in time, dropping connection.
May 22, 2020 23:46:12.917 [17972] VERBOSE - Didn't receive a request from 63.34.171.72:51454: stream truncated
May 22, 2020 23:46:42.479 [17992] VERBOSE - Didn't receive a request from 34.245.172.51:45944: stream truncated
May 22, 2020 23:48:14.277 [17992] VERBOSE - We didn't receive any data from 54.171.49.143:48340 in time, dropping connection.
May 22, 2020 23:50:06.237 [17972] VERBOSE - We didn't receive any data from 54.171.49.143:42122 in time, dropping connection.
May 22, 2020 23:50:13.072 [17992] VERBOSE - Didn't receive a request from 54.171.49.143:50630: stream truncated
Would like to see fresh logs please and I will pass on to our plex.tv team if it is still the same
The timeout periods have just been doubled for servers in your country. I would like to know if the issue remains and if the requests for connectivity testing are still aborting, I would like to get wireshark capture and associated Plex Media Server tls key logging. I would send you instructions how to get that in Private Message if the issue remains.