Could you do a traceroute for 34.243.160.122 and send me the output
tracert 34.243.160.122
Tracing route to ec2-34-243-160-122.eu-west-1.compute.amazonaws.com [34.243.160.122]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 5 ms 6 ms 10.20.25.153
3 6 ms 6 ms 6 ms adl-apt-pir-crt1-be100.tpgi.com.au [203.219.182.1]
4 19 ms 21 ms 22 ms nme-sot-dry-crt1-be70.tpgi.com.au [203.219.107.189]
5 36 ms 30 ms 30 ms syd-apt-ros-crt1-be-10.tpgi.com.au [202.7.171.141]
6 30 ms 30 ms 31 ms syd-apt-ros-int1-hu0-3-0-2.tpgi.com.au [203.29.134.3]
7 200 ms 200 ms 200 ms ix-et-0-0-2-0.tcore1.lvw-losangeles.as6453.net [64.86.197.96]
8 336 ms 336 ms 335 ms if-ae-8-3.tcore1.sv1-santaclara.as6453.net [63.243.250.58]
9 333 ms 332 ms 332 ms if-ae-0-2.tcore2.sv1-santaclara.as6453.net [63.243.251.2]
10 332 ms 333 ms 333 ms if-ae-18-3.tcore1.sqn-sanjose.as6453.net [63.243.205.130]
11 344 ms 344 ms 345 ms if-ae-0-2.tcore1.nto-newyork.as6453.net [63.243.128.30]
12 336 ms 336 ms 336 ms if-ae-8-3.tcore2.nto-newyork.as6453.net [63.243.128.135]
13 338 ms 336 ms 338 ms if-ae-32-2.tcore2.ldn-london.as6453.net [63.243.216.23]
14 335 ms 335 ms 335 ms 80.231.20.82
15 350 ms 329 ms 329 ms 54.239.100.238
16 329 ms 328 ms 328 ms 150.222.65.31
17 * * * Request timed out.
18 338 ms 339 ms 339 ms 52.93.128.212
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
I’m having a similar problem where Plex will say “Your server is registered with Plex, but it is not accessible outside your network.” but if I hit retry it will say it’s fully accessible. Then 10+ minutes later I’ll get the not accessiblePlex Media Server Logs_2020-06-30_22-23-54.zip (5.1 MB) message. This repeats. I have attached the log. I got a new Fios Home Router, G3100 and the problem started. It was a big upgrade in speed 
Appreciate any help!
Thanks for the logs. Do you have any Geo Blocking on IP addresses or other IP specific whitelisting ?
The connectivity tests for remote access would come from one of these IP addresses and any could be used
34.243.160.122
34.245.172.51
34.248.59.52
52.16.207.132
54.171.49.143
63.34.171.72
The logs does show that the connectivity tests come in at some points but not every time. There is no evidence in the verbose logging of an aborted or timed out connectivity test
If this is repeatable - i would like to see a wireshark packet capture - pcap file saved for when this happens and please stay on the remote access server setting page and do not click on retry - just want to see if every connectivity test fails or just some
Wireshark is available here Wireshark · Download
Also when it happens and again without doing any retries, get a screenshot of the router uPnP port forwards screen and note down the times
With uPnP automatic port forwarding Plex Media Server refreshes the uPnP port forward every hour and I do not see any errors in the log when this is happening - at the moment this is happening at xx:40:xx every hour. It would be useful to get a wireshark capture for this action - this time is relative to when the Plex Media Server was launched and it happens every hour from then on - so if you have not restarted Plex Media Server since it would be 12:40 and 13:40 and 14:40 etc… You could start wireshark a minute or so before and let it capture packets for 5 minutes and then save and send me with the logs zip
I would also like to see a wireshark capture for the sequence of clicking retry - what this does is dis-establish the port forward and then re-establish it. I would like to know why we get an error on attempting to dis-establish it
Jun 30, 2020 17:16:01.067 [17424] WARN - NAT: UPnP, error unmapping port 26262, error: Invalid Args.
Jun 30, 2020 17:16:01.317 [17424] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
The error is probably harmless - but still i would like to understand why
So would like a wireshark capture for this with logs - again please note down the times of the tests and do not attach wireshark pcap files in the forum - zip and send me as private message
Thanks for your detailed reply! I seemed to have fixed it. It seems Plex added a port forward for my router, but something was not correct with it, as it seemed to “time out” after 10+ minutes and fail to foward the port. It had picked port 26261. I went to my router and deleted that port forwarding and created my own, using port 32400. Then I manually specified the port in Plex (that option wasn’t used before). It has been working fine for the past two days. Any thoughts on what was wrong with the way Plex setup the port forwarding? I believe it set it up to use both UDP and TCP.
it should be tcp only. I wanted to see the wireshark capture and router table to find out more. The only error in the log was for when trying to remove the port forward but the hourly refresh of the port forward seemed ok with no errors
That is always the more reliable option - but you must make sure the local IP address does not change - set to static outside dhcp range or dhcp reserved
Sometimes ISPs update firmware without notification and port forwards or dhcp reservation get lost
Anything else you need from me besides the trace? Its still occurring in the latest public release Version 1.19.4.2935
You probably have UPNP on, which tried to automatically add the relevant port forward rules. Turn that off and generate them yourself, like you have done.
A wireshark capture of network packets whilst the server settings remote access screen is displayed would be useful to see - together with the associated verbose Plex Media Server logs zip - having the wireshark network capture started before the server settings page is dispalyed.
Just dm them to you.
Thank you - i can see aborted TLS connections after about 2.5 seconds
I am passing the evidence to our engineering team
You probably find that disabling secure connections would get round the problem
I had to set my cable modem to bridge mode to fix this.
That would have been a Double NAT fixed by switching the cable modem/router to bridge mode to eliminate the Double NAT
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.
Yes. Still occurring for me at least.
Happy to supply whatever you need.
Thanks.
sent you instructions for enabling Plex Media Server TLS Logging to go with the wireshark capture and server logs
Thanks
This topic was automatically closed after 90 days. New replies are no longer allowed.
