Plex Constantly Loses Remote Access

artagel · April 29, 2020, 1:31pm

Yes, youcanseeme shows my port 32400 open and reachable.

Apr 29, 2020 09:22:26.008 [0x7fbcb0f84700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (a2ad2db0-ac37-420a-9b73-904720783643, expected 9ac84a8f-3f7e-4f33-a296-0626cee52365)
Apr 29, 2020 09:24:27.009 [0x7fbcabfff700] DEBUG - PubSub: Got notified of reachability for async identifier ca78b03c-5864-403f-a9b7-1c6916c34c6c: 1 for 116.15.153.47:32400 (responded in 2 seconds)
Apr 29, 2020 09:24:53.328 [0x7fbcabfff700] DEBUG - PubSub: Got notified of reachability for async identifier 0463664b-2257-461d-8db2-8170e984640a: 1 for 116.15.153.47:32400 (responded in 1 seconds)
Apr 29, 2020 09:25:15.105 [0x7fbcabfff700] DEBUG - PubSub: Got notified of reachability for async identifier f53b60ee-edfb-4f1f-baa3-c9f588ae2c3b: 0 for 116.15.153.47:32400 (responded in 2 seconds)
Apr 29, 2020 09:25:37.149 [0x7fbcb0f84700] DEBUG - PubSub: Got notified of reachability for async identifier 7d0c85fe-889d-43a4-aa5a-4ab5e2572a91: 0 for :0 (responded in 1 seconds)
Apr 29, 2020 09:26:02.743 [0x7fbcb0f84700] DEBUG - PubSub: Got notified of reachability for async identifier ed738c05-31ab-4bbf-905c-5d98648c48b4: 0 for 116.15.153.47:32400 (responded in 2 seconds)
Apr 29, 2020 09:26:14.136 [0x7fbcabfff700] DEBUG - PubSub: Got notified of reachability for async identifier baaabd9b-b169-4c4f-831b-35562be6a886: 0 for :0 (responded in 1 seconds)
Apr 29, 2020 09:26:42.823 [0x7fbcabfff700] DEBUG - PubSub: Got notified of reachability for async identifier a2fedd69-353d-4304-b610-72b56ce9014b: 0 for 116.15.153.47:32400 (responded in 1 seconds)
Apr 29, 2020 09:27:15.226 [0x7fbcb0f84700] DEBUG - PubSub: Got notified of reachability for async identifier e13a464f-ab2f-4a1a-9b0c-7e7756c196a7: 1 for 116.15.153.47:32400 (responded in 2 seconds)
Apr 29, 2020 09:28:15.199 [0x7fbcb0f84700] DEBUG - PubSub: Got notified of reachability for async identifier 556d9065-ae7c-4fc3-9524-1ef667f8d002: 1 for 116.15.153.47:32400 (responded in 2 seconds)

Plex Media Server Logs_2020-04-29_09-29-42.zip (1.5 MB)

davorbn · May 12, 2020, 8:31am

Plex Media Server Logs_2020-05-12_17-35-51.zip (4.5 MB)

I am still having this issue. I sort of forgot about it because i turned off Tautulli notification relating to the remote access.

I’m using Version 1.19.3.2764.

My system is setup as following:

Asus router to;
Unifi Security Gateway Pro;
Unifi 24 PoE Switch;
Synology NAS
Plex running as application

Port forwarding enabled via asus router and security gateway. Checked port via portchecker.co and is always open.

I don’t seem to have issues accessing the content remotely, even though the remote access continues to drop and reenable itself constantly…

sa2000 · May 12, 2020, 12:58pm

Are you still getting these connectivity test failures?

I have been looking into an issue where the connectivity test requests timeout early or get aborted - If you are getting this problem still, I would like to have verbose logging also enabled - that would show if the requests are being aborted leading to the connectivity="0" events you pasted in above.

If there is evidence of that. then the next step would be to get traceroute for the failing / aborted connections IP addresses and see what delays are in the route.

I have posts here about it in here Remote Access connects for about 15 seconds then disconnects - #161 by sa2000

sa2000 · May 12, 2020, 1:33pm

It appears to be the issue I mentioned here Remote Access connects for about 15 seconds then disconnects - #161 by sa2000

we are getting aborted / timed out connections to the servers - seen mostly on those located in Australia / New Zealnd / Singapore / Malaysia -

May 12, 2020 17:30:08.890 [0x7f209303c700] VERBOSE - Didn't receive a request from 54.171.49.143:43698: stream truncated
May 12, 2020 17:30:09.121 [0x7f209303c700] DEBUG - EventSource: Got event [data] '<Message address="155.143.xxx.xxx" port="32400" asyncIdentifier="24660336-2514-40bc-95bb-1ed1ca3c69c0" connectivity="0" command="notifyConnectivity"/>'

May 12, 2020 17:32:09.040 [0x7f209303c700] DEBUG - EventSource: Got event [data] '<Message address="155.143.xxx.xxx" port="32400" asyncIdentifier="50956ac4-f895-4bea-87fd-fafffa2ba399" connectivity="0" command="notifyConnectivity"/>'
May 12, 2020 17:32:09.051 [0x7f209303c700] VERBOSE - Didn't receive a request from 34.248.59.52:41906: stream truncated

May 12, 2020 17:33:37.988 [0x7f209303c700] VERBOSE - Didn't receive a request from 34.243.160.122:37442: stream truncated
May 12, 2020 17:33:38.244 [0x7f209332a700] DEBUG - EventSource: Got event [data] '<Message address="155.143.xxx.xxx" port="32400" asyncIdentifier="44d0bd56-4ebc-4eb2-b97f-7c06b8b921f8" connectivity="0" command="notifyConnectivity"/>'

May 12, 2020 17:34:08.946 [0x7f209303c700] VERBOSE - Didn't receive a request from 34.248.59.52:46542: stream truncated
May 12, 2020 17:34:09.164 [0x7f209303c700] DEBUG - EventSource: Got event [data] '<Message address="155.143.xxx.xxx" port="32400" asyncIdentifier="64b130c2-3ae5-407f-8602-7c00d2604ba7" connectivity="0" command="notifyConnectivity"/>'

Could you get me traceroute outputs for each of these ip addresses to see what the delays are - these Amazonws servers are located in Ireland

52.16.207.132
34.243.160.122
34.245.172.51
34.248.59.52
63.34.171.72
54.171.49.143

sa2000 · May 12, 2020, 1:34pm

and I suggest you disable remote access checks by Tautulli - and contact the developers and suggest they change the frequency of checks from once every minute to - say 2 or 4 an hour

artagel · May 12, 2020, 2:46pm

Hi Sa2000,
My logs are attached.
Traceroutes from a couple of the IPs I saw in the log:

traceroute to 34.243.160.122 (34.243.160.122), 30 hops max, 60 byte packets
 1  192.168.100.254 (192.168.100.254)  0.781 ms  0.829 ms  0.999 ms
 2  bb116-15-153-254.singnet.com.sg (116.15.153.254)  3.886 ms  3.883 ms  3.964 ms
 3  202.166.123.130 (202.166.123.130)  5.979 ms  5.964 ms  5.991 ms
 4  202.166.123.129 (202.166.123.129)  4.499 ms  4.592 ms  4.466 ms
 5  ae8-0.qt-cr03.singnet.com.sg (202.166.121.101)  4.669 ms  4.914 ms  5.114 ms
 6  ae13-0.tp-cr03.singnet.com.sg (202.166.120.109)  5.100 ms  2.711 ms  3.634 ms
 7  ae4-0.tp-er03.singnet.com.sg (202.166.123.70)  3.585 ms  3.731 ms  7.264 ms
 8  203.208.191.113 (203.208.191.113)  3.806 ms  4.225 ms 203.208.191.197 (203.208.191.197)  4.599 ms
 9  203.208.153.246 (203.208.153.246)  4.619 ms  4.659 ms 203.208.149.77 (203.208.149.77)  4.457 ms
10  203.208.172.166 (203.208.172.166)  187.346 ms 203.208.154.46 (203.208.154.46)  190.311 ms 203.208.178.186 (203.208.178.186)  187.281 ms
11  64.125.35.201 (64.125.35.201)  193.374 ms  193.153 ms  194.346 ms
12  ae13.cs2.lax112.us.eth.zayo.com (64.125.27.42)  326.768 ms  326.720 ms  326.722 ms
13  * * *
14  * * *
15  * ae11.cs1.den5.us.zip.zayo.com (64.125.26.42)  313.529 ms  316.738 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

traceroute to 54.171.49.143 (54.171.49.143), 30 hops max, 60 byte packets
 1  192.168.100.254 (192.168.100.254)  0.827 ms  0.905 ms  0.946 ms
 2  bb116-15-153-254.singnet.com.sg (116.15.153.254)  5.939 ms  5.898 ms  5.854 ms
 3  202.166.123.130 (202.166.123.130)  7.699 ms  7.678 ms  7.646 ms
 4  202.166.123.129 (202.166.123.129)  6.703 ms  7.529 ms  7.485 ms
 5  ae8-0.qt-cr03.singnet.com.sg (202.166.121.101)  7.764 ms  7.851 ms  8.134 ms
 6  ae13-0.tp-cr03.singnet.com.sg (202.166.120.109)  8.906 ms  6.447 ms  3.261 ms
 7  ae4-0.tp-er03.singnet.com.sg (202.166.123.70)  3.315 ms  3.693 ms  3.641 ms
 8  203.208.145.233 (203.208.145.233)  4.767 ms 203.208.191.197 (203.208.191.197)  4.327 ms 203.208.145.233 (203.208.145.233)  3.386 ms
 9  203.208.153.246 (203.208.153.246)  4.085 ms  4.442 ms  4.536 ms
10  203.208.158.30 (203.208.158.30)  178.459 ms 203.208.154.46 (203.208.154.46)  187.836 ms 203.208.171.10 (203.208.171.10)  185.476 ms
11  * * *
12  ae13.cs2.lax112.us.eth.zayo.com (64.125.27.42)  326.083 ms  321.861 ms  322.565 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Plex Media Server Logs_2020-05-12_10-45-53.zip (4.9 MB)

sa2000 · May 12, 2020, 10:36pm

Thanks - the logs show dropped/aborted connectivity test requests - and the 2 traceroutes you provided are relevant - for 2 of the 3 that had aborts

I will pass the details on

I would like to understand the route -
So the server is located in Singapore - the route to the Ireland hosted Amazon servers is through USA and the server is running on US Timezone (GMT-4)

The traceroute shows delays along the way

203.208.172.166		187 ms 	Singapore Telecoms 
64.125.35.201		193 ns  Zayo Bandwidth - US California
64.125.27.42		326 ms  Zayo - US
64.125.26.42		313 ms  Zayo - US

I notice the server logs show a corrupt Plex Media Server database you are running with - please try a repair or restore from last good scheduled task backup

May 11, 2020 09:04:45.424 [0x7f6188b99780] ERROR - SQLITE3:(nil), 11, database corruption at line 85694 of [bf8c1b2b7a]
May 11, 2020 09:04:45.424 [0x7f6188b99780] ERROR - SQLITE3:(nil), 11, statement aborts at 15: [CREATE INDEX 'index_statistics_media_on_at' ON 'statistics_media' ('at')] database disk image is malformed
May 11, 2020 09:04:45.424 [0x7f6188b99780] ERROR - Exception inside transaction (inside=1) (../Library/DatabaseMigrations.cpp:209): sqlite3_statement_backend::loadOne: database disk image is malformed
May 11, 2020 09:04:45.428 [0x7f6188b99780] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed

See
https://support.plex.tv/articles/201100678-repair-a-corrupt-database/
https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

sa2000 · May 12, 2020, 10:50pm

And whilst there are these issues, I suggest disabling Tautulli remote access checking that tests it every minute. Remote Access is working - it is just the indicator that is wrong - but if you start to disable / re-enable remote access whilst connections are being dropped to the Ireland servers - then that might actually impact remote access and stop it being established

davorbn · May 12, 2020, 11:29pm

I have set Tautulli to check every 2 hours.

IP: 52.16.207.132

traceroute to 52.16.207.132 (52.16.207.132), 30 hops max, 38 byte packets
 1  58.162.27.200 (58.162.27.200)  5.152 ms  4.229 ms  4.548 ms
 2  10.203.121.6 (10.203.121.6)  5.127 ms  5.626 ms  5.613 ms
 3  10.203.221.2 (10.203.221.2)  6.609 ms  8.608 ms  10.203.121.2 (10.203.121.2)  14.106 ms
 4  Bundle-Ether36.win-edge903.melbourne.telstra.net (203.54.220.117)  6.721 ms  5.696 ms  Bundle-Ether49.lon-edge903.melbourne.telstra.net (203.54.218.241)  5.901 ms
 5  Bundle-Ether26.win-edge901.melbourne.telstra.net (139.130.141.1)  6.713 ms  Bundle-Ether25.lon-edge901.melbourne.telstra.net (139.130.74.209)  6.689 ms  bundle-ether13.win-core10.melbourne.telstra.net (203.50.11.194)  7.982 ms
 6  bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122)  18.450 ms  17.471 ms  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  17.117 ms
 7  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  18.012 ms  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  17.208 ms  18.908 ms
 8  bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  18.895 ms  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  18.105 ms  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  19.687 ms
 9  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  163.240 ms  162.783 ms  bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98)  20.087 ms
10  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  163.307 ms  i-10604.1wlt-core02.telstraglobal.net (202.84.141.225)  154.255 ms  i-10403.sydo-core04.telstraglobal.net (202.84.222.130)  17.729 ms
11  202.84.249.173 (202.84.249.173)  293.201 ms  i-10106.unse-core01.telstraglobal.net (202.40.148.105)  213.167 ms  i-10604.1wlt-core02.telstraglobal.net (202.84.141.225)  153.757 ms
12  202.84.249.173 (202.84.249.173)  285.022 ms  i-10106.unse-core01.telstraglobal.net (202.40.148.105)  214.351 ms  202.84.249.173 (202.84.249.173)  284.685 ms
13  i-91.ulco01.telstraglobal.net (202.40.148.34)  285.015 ms  i-31.ulhc-core01.telstraglobal.net (202.84.252.90)  295.530 ms  297.706 ms
14  *  *  *
15  *  *  *
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *

IP: 34.243.160.122

traceroute to 34.243.160.122 (34.243.160.122), 30 hops max, 38 byte packets
 1  58.162.27.200 (58.162.27.200)  4.627 ms  4.679 ms  4.386 ms
 2  10.203.121.6 (10.203.121.6)  4.804 ms  103.8.135.58 (103.8.135.58)  5.296 ms  10.203.121.6 (10.203.121.6)  5.005 ms
 3  10.203.122.2 (10.203.122.2)  7.315 ms  10.203.221.2 (10.203.221.2)  6.744 ms  10.203.221.1 (10.203.221.1)  6.324 ms
 4  Bundle-Ether49.lon-edge903.melbourne.telstra.net (203.54.218.241)  16.770 ms  5.640 ms  6.359 ms
 5  Bundle-Ether26.win-edge901.melbourne.telstra.net (139.130.141.1)  6.345 ms  Bundle-Ether25.lon-edge901.melbourne.telstra.net (139.130.74.209)  6.938 ms  6.229 ms
 6  bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122)  18.834 ms  18.222 ms  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  19.097 ms
 7  bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122)  18.579 ms  18.246 ms  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  18.389 ms
 8  bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  18.704 ms  bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98)  17.929 ms  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  18.229 ms
 9  bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  19.613 ms  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  162.720 ms  163.007 ms
10  i-14808.ny8a-core01.telstraglobal.net (202.40.148.98)  259.336 ms  i-10403.sydo-core04.telstraglobal.net (202.84.222.130)  19.329 ms  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  162.618 ms
11  i-3.unse-core01.telstraglobal.net (202.40.148.117)  214.685 ms  i-10106.unse-core01.telstraglobal.net (202.40.148.105)  214.825 ms  i-10348.ulhc-core01.telstraglobal.net (202.84.141.229)  288.534 ms
12  i-10401.ulco-core02.telstraglobal.net (202.84.141.146)  281.058 ms  i-92.ulco01.telstraglobal.net (202.84.178.6)  281.204 ms  i-10106.unse-core01.telstraglobal.net (202.40.148.105)  214.057 ms
13  i-91.ulco01.telstraglobal.net (202.40.148.34)  281.172 ms  *  i-10401.ulco-core02.telstraglobal.net (202.84.141.146)  285.143 ms
14  *  *  i-91.ulco01.telstraglobal.net (202.40.148.34)  303.366 ms
15  *  *  *
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *

IP: 34.245.172.51

traceroute to 34.245.172.51 (34.245.172.51), 30 hops max, 38 byte packets
 1  58.162.27.200 (58.162.27.200)  4.881 ms  4.884 ms  4.653 ms
 2  10.203.121.6 (10.203.121.6)  4.830 ms  103.8.135.58 (103.8.135.58)  5.258 ms  5.272 ms
 3  10.203.122.1 (10.203.122.1)  6.881 ms  10.203.121.2 (10.203.121.2)  7.306 ms  10.203.221.1 (10.203.221.1)  6.085 ms
 4  Bundle-Ether49.lon-edge903.melbourne.telstra.net (203.54.218.241)  5.692 ms  cpe-141-168-7-2.static.belong.com.au (141.168.7.2)  6.699 ms  Bundle-Ether49.lon-edge903.melbourne.telstra.net (203.54.218.241)  5.890 ms
 5  Bundle-Ether25.lon-edge901.melbourne.telstra.net (139.130.74.209)  5.931 ms  6.155 ms  6.347 ms
 6  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  18.146 ms  19.248 ms  18.877 ms
 7  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  19.293 ms  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  17.957 ms  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  20.757 ms
 8  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  17.206 ms  bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  18.373 ms  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  17.650 ms
 9  i-10403.sydo-core04.telstraglobal.net (202.84.222.130)  17.966 ms  17.473 ms  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  163.160 ms
10  i-10604.1wlt-core02.telstraglobal.net (202.84.141.225)  154.016 ms  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  170.241 ms  i-14808.ny8a-core01.telstraglobal.net (202.40.148.98)  258.290 ms
11  i-14808.ny8a-core01.telstraglobal.net (202.40.148.98)  257.284 ms  i-10604.1wlt-core02.telstraglobal.net (202.84.141.225)  154.791 ms  154.484 ms
12  i-10348.ulhc-core01.telstraglobal.net (202.84.141.229)  291.128 ms  i-10106.unse-core01.telstraglobal.net (202.40.148.105)  214.536 ms  202.84.249.173 (202.84.249.173)  285.826 ms
13  i-91.ulco01.telstraglobal.net (202.40.148.34)  281.256 ms  311.047 ms  *
14  *  *  *
15  *  *  *
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *

IP: 34.248.59.52

traceroute to 34.248.59.52 (34.248.59.52), 30 hops max, 38 byte packets
 1  58.162.27.200 (58.162.27.200)  5.501 ms  4.769 ms  6.521 ms
 2  10.203.121.6 (10.203.121.6)  4.678 ms  6.349 ms  5.350 ms
 3  10.203.221.1 (10.203.221.1)  6.368 ms  10.203.222.1 (10.203.222.1)  33.575 ms  6.258 ms
 4  cpe-141-168-7-2.static.belong.com.au (141.168.7.2)  6.337 ms  cpe-141-168-8-2.static.belong.com.au (141.168.8.2)  8.479 ms  Bundle-Ether49.lon-edge903.melbourne.telstra.net (203.54.218.241)  5.688 ms
 5  bundle-ether13.exi-core10.melbourne.telstra.net (203.50.11.198)  7.170 ms  bundle-ether13.win-core10.melbourne.telstra.net (203.50.11.194)  6.736 ms  bundle-ether13.exi-core10.melbourne.telstra.net (203.50.11.198)  7.209 ms
 6  bundle-ether11.win-core10.melbourne.telstra.net (203.50.11.107)  7.258 ms  *  bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122)  19.533 ms
 7  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  17.274 ms  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  18.037 ms  19.152 ms
 8  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  18.635 ms  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  18.248 ms  bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  18.406 ms
 9  i-10403.sydo-core04.telstraglobal.net (202.84.222.130)  18.988 ms  18.846 ms  18.918 ms
10  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  162.881 ms  i-10604.1wlt-core02.telstraglobal.net (202.84.141.225)  155.051 ms  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  163.764 ms
11  i-14808.ny8a-core01.telstraglobal.net (202.40.148.98)  256.428 ms  i-10348.ulhc-core01.telstraglobal.net (202.84.141.229)  289.882 ms  i-10106.unse-core01.telstraglobal.net (202.40.148.105)  214.279 ms
12  i-10106.unse-core01.telstraglobal.net (202.40.148.105)  213.790 ms  i-91.ulco01.telstraglobal.net (202.40.148.34)  285.487 ms  i-92.ulco01.telstraglobal.net (202.84.178.6)  281.698 ms
13  i-31.ulhc-core01.telstraglobal.net (202.84.252.90)  308.288 ms  i-92.ulco01.telstraglobal.net (202.84.178.6)  288.222 ms  289.774 ms
14  *  *  *
15  *  *  *
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *

IP: 63.34.171.72

traceroute to 63.34.171.72 (63.34.171.72), 30 hops max, 38 byte packets
 1  58.162.27.200 (58.162.27.200)  4.729 ms  4.546 ms  4.531 ms
 2  103.8.135.58 (103.8.135.58)  5.159 ms  5.475 ms  10.203.121.6 (10.203.121.6)  5.642 ms
 3  10.203.122.1 (10.203.122.1)  7.020 ms  10.203.221.2 (10.203.221.2)  6.559 ms  10.203.122.1 (10.203.122.1)  6.070 ms
 4  Bundle-Ether49.lon-edge903.melbourne.telstra.net (203.54.218.241)  5.871 ms  Bundle-Ether36.win-edge903.melbourne.telstra.net (203.54.220.117)  5.968 ms  5.422 ms
 5  Bundle-Ether25.lon-edge901.melbourne.telstra.net (139.130.74.209)  6.204 ms  bundle-ether13.win-core10.melbourne.telstra.net (203.50.11.194)  7.951 ms  Bundle-Ether26.win-edge901.melbourne.telstra.net (139.130.141.1)  6.752 ms
 6  bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122)  18.224 ms  bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124)  17.450 ms  bundle-ether12.ken-core10.sydney.telstra.net (203.50.11.122)  18.662 ms
 7  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  17.465 ms  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  17.437 ms  17.973 ms
 8  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  18.027 ms  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  17.211 ms  bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  19.299 ms
 9  bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  18.786 ms  i-10403.sydo-core04.telstraglobal.net (202.84.222.130)  19.367 ms  18.474 ms
10  i-10403.sydo-core04.telstraglobal.net (202.84.222.130)  17.578 ms  18.020 ms  19.317 ms
11  i-14808.ny8a-core01.telstraglobal.net (202.40.148.98)  257.425 ms  i-10604.1wlt-core02.telstraglobal.net (202.84.141.225)  153.742 ms  155.243 ms
12  i-10348.ulhc-core01.telstraglobal.net (202.84.141.229)  288.704 ms  i-3.unse-core01.telstraglobal.net (202.40.148.117)  215.730 ms  i-10401.ulco-core02.telstraglobal.net (202.84.141.146)  283.225 ms
13  i-91.ulco01.telstraglobal.net (202.40.148.34)  280.695 ms  i-10401.ulco-core02.telstraglobal.net (202.84.141.146)  281.186 ms  i-92.ulco01.telstraglobal.net (202.84.178.6)  281.443 ms
14  *  i-91.ulco01.telstraglobal.net (202.40.148.34)  281.000 ms  *
15  *  *  *
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *

IP: 54.171.49.143

traceroute to 54.171.49.143 (54.171.49.143), 30 hops max, 38 byte packets
 1  58.162.27.200 (58.162.27.200)  59.972 ms  66.143 ms  26.300 ms
 2  10.203.121.6 (10.203.121.6)  29.753 ms  33.949 ms  103.8.135.58 (103.8.135.58)  52.228 ms
 3  10.203.122.1 (10.203.122.1)  40.254 ms  10.203.122.2 (10.203.122.2)  53.120 ms  10.203.121.2 (10.203.121.2)  46.478 ms
 4  Bundle-Ether36.win-edge903.melbourne.telstra.net (203.54.220.117)  22.653 ms  cpe-141-168-8-1.static.belong.com.au (141.168.8.1)  65.907 ms  Bundle-Ether36.win-edge903.melbourne.telstra.net (203.54.220.117)  14.469 ms
 5  bundle-ether13.win-core10.melbourne.telstra.net (203.50.11.194)  10.681 ms  Bundle-Ether25.lon-edge901.melbourne.telstra.net (139.130.74.209)  25.387 ms  54.115 ms
 6  bundle-ether11.win-core10.melbourne.telstra.net (203.50.11.107)  32.563 ms  *  bundle-ether10.exi-core10.melbourne.telstra.net (203.50.11.109)  20.664 ms
 7  bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93)  28.482 ms  19.767 ms  18.753 ms
 8  bundle-ether1.sydp-core04.sydney.reach.com (203.50.13.90)  21.650 ms  21.925 ms  bundle-ether1.pad-gw11.sydney.telstra.net (203.50.6.61)  22.268 ms
 9  i-10403.sydo-core04.telstraglobal.net (202.84.222.130)  24.616 ms  i-20802.eqnx-core02.telstraglobal.net (202.84.141.25)  166.586 ms  bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98)  30.701 ms
10  i-10403.sydo-core04.telstraglobal.net (202.84.222.130)  19.401 ms  i-14808.ny8a-core01.telstraglobal.net (202.40.148.98)  258.836 ms  i-10604.1wlt-core02.telstraglobal.net (202.84.141.225)  166.971 ms
11  i-14808.ny8a-core01.telstraglobal.net (202.40.148.98)  256.596 ms  i-3.unse-core01.telstraglobal.net (202.40.148.117)  218.872 ms  i-10604.1wlt-core02.telstraglobal.net (202.84.141.225)  160.002 ms
12  i-31.ulhc-core01.telstraglobal.net (202.84.252.90)  296.605 ms  i-10106.unse-core01.telstraglobal.net (202.40.148.105)  236.234 ms  i-31.ulhc-core01.telstraglobal.net (202.84.252.90)  305.634 ms
13  i-92.ulco01.telstraglobal.net (202.84.178.6)  297.986 ms  289.792 ms  *
14  *  *  *
15  *  *  *
16  *  *  *
17  *  *  *
18  *  *  *
19  *  *  *
20  *  *  *
21  *  *  *
22  *  *  *
23  *  *  *
24  *  *  *
25  *  *  *
26  *  *  *
27  *  *  *
28  *  *  *
29  *  *  *
30  *  *  *[Plex Media Server Logs_2020-05-13_09-28-36.zip|attachment](upload://gPJLv3JF3LapdtdTA19ZE6NCfK7.zip) (7.7 MB)

sa2000 · May 13, 2020, 10:39am

[quote=“davorbn, post:427, topic:284944”]
I have set Tautulli to check every 2 hours.

Thanks for the traceroutes

Alejo516 · May 17, 2020, 10:53pm

I am having the same issue mentioned in this thread. Remote access not working. I’ve never had any issues with it and never had to open ports on my router or anything like that. Seems like updating the app from a perfectly working version has made a turn for the worst for me. I’m located in Canada. Right now I’m reverting to an older version and try to see if it works. Just wanted to chime in so the devs know that this is happening with the latest version.
Thanks

rolle · May 18, 2020, 12:28pm

Updated yesterday to the latest plexpass version and now having this problem… https://dsh.re/99a530

davorbn · May 18, 2020, 9:48pm

What’s the next step?

sa2000 · May 21, 2020, 12:30pm

What is the impact of the issue? It should only be affecting the status indicator and alerting by Tautulli - it should not be impacting Remote Access functionality

davorbn · May 22, 2020, 8:39am

The only impact is the annoyance - haha! I guess I’ll just have to put up with it.

GXEmpire · May 22, 2020, 2:32pm

Same issue. Plex was fine for quite some time using manual port forwarding. Out of the blue (or perhaps after the latest Plex update), it now keeps dropping remote access intermittently.

bhav111 · May 26, 2020, 12:47pm

So, can I add to this topic or have to create new topic for my issue which is almost similar. Bit detail, I always had this issue of loosing outside connection after ANY plex updates came. At one point, I stopped updating PMS and I had the most stable connection for almost 8 or so months. Then at some point within last 2/3 updates, iOS settings changed and I couldn’t get to Plex if I was using my iPhone or iPad. So finally gave in and did the most recent PMS update. Everything started working as expected and i thought I was safe. But in short period of time, now I’m back to original issue and my PMS doesn’t hold connection to outside of my network for more then 5/10 mins. I have to hit “retry” button and it sometime comes back. But oh it’s so frustrating. I’m not sure what info I can provide for someone to look into it but please let me know and I’ll gladly follow instructions. Also, I have xFi Gateway from xFinity and I have done the port forwarding on that. Also, disabled Advanced Security as at some point I thought that was blocking Plex connections. But again, it worked just fine for about 8 months without doing any updates and now it broke. I understand that PMS updates are a required thing to fix bugs/holes/provide new options but it defeats the purpose, for me, if PMS completely stops working as expected after each updates.

sa2000 · May 27, 2020, 12:58am

There is a difference between dropping remote access (and access to the server remotely no longer possible) and remote access availability indicator saying it is unavailable.

If there is a port forward in the router and manually specified port setup then Plex Media Server does not the means to dis-establish that and it should remain working.

The availability indicator may be wrong sometimes - but there is a change in the latest beta in 1.19.4 to minimize the chances of the indicator being wrong

See release note

(Remote Access) Status may initially show as unavailable on server settings web page. (#5114)

Logs would be needed to investigate the loss of remote access

sa2000 · May 27, 2020, 1:05am

bhav111:

, can I add to this topic or have to create new topic for my issue which is almost similar. Bit detail, I always had this issue of loosing outside connection after ANY plex updates came. At one point, I stopped updating PMS and I had the most stable connection for almost 8 or so months. Then at some point within last 2/3 updates, iOS settings changed and I couldn’t get to Plex if I was using my iPhone or iPad. So finally gave in and did the most recent PMS update. Everything started working as expected and i thought I was safe. But in short period of time, now I’m back to original issue and my PMS doesn’t hold connection to outside of my network for more then 5/10 mins. I have to hit “retry” button and it sometime comes back. But oh it’s so frustrating. I’m not sure what info I can provide for someone to look into it but please let me know and I’ll gladly follow instructions. Also, I have xFi Gateway from xFinity and I have done the port forwarding on that. Also, disabled Advanced Security as at some point I thought that was blocking Plex connections. But again, it worked just fine for about 8 months without doing any updates and now it broke. I understand that PMS updates are a required thing to fix bugs/holes/provide new options but it defeats the purpose, for me, if PMS completely stops working as expected after each updates.

A few things -

xFinity Advanced Security does kill remote access functionality as each port forward has a limited time and incoming traffic needs to be authorized bythe user. We have a section about this now on the troubleshooting remote access support page https://support.plex.tv/articles/200931138-troubleshooting-remote-access/

In latest beta 1.19.4 we have new additional logging to help troubleshoot remote access issues and also there is a change to avoid marking Remote Access as unavailable if a connectivity test request has not been done,

I would suggest trying 1.19.4 and if you have issues then get logs and I will have a look

Mark_Leefie · August 14, 2020, 10:22am

In my experience (after almost a year of trying everything including replacing hardware) I fixed an identical issue by having my ISP manually enable ip4.

Topic		Replies	Views
Remote Access shuts off General Discussions	73	138	January 7, 2020
Remote access Stopped working Desktops & Laptops server-windows	38	4903	January 4, 2019
Remote Access Drops with Version 1.13.2.5154 Desktops & Laptops	61	5253	December 9, 2018
PLEX remote access keeps disconnecting, bug? Remote Access server-windows , server-linux	57	6874	August 5, 2019
Remote Access - Says its working, but it isnt Desktops & Laptops server-windows	98	4347	March 21, 2019

Plex Constantly Loses Remote Access

Related topics