It is not allowing me to post the log file but ever since update 1.12.3.4947 my remote access is no longer working. I attempted all port forwarding solutions and checked everything possible in the firewall, nothing has changed but the update and now my remote access reads as “Not available outside your network
Your server is signed in to Plex, but is not reachable from outside your network.”
Log info in comments as the file wont upload
Apr 12, 2018 17:29:03.377 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:03.377 [10312] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:03.378 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 0ms 723 bytes (pipelined: 19)
Apr 12, 2018 17:29:03.880 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:03.880 [8524] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:03.882 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 1ms 723 bytes (pipelined: 20)
Apr 12, 2018 17:29:04.380 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:04.380 [10524] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:04.382 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 1ms 723 bytes (pipelined: 21)
Apr 12, 2018 17:29:04.879 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:04.880 [8524] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:04.881 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 1ms 723 bytes (pipelined: 22)
Apr 12, 2018 17:29:05.381 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:05.381 [10524] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:05.383 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 1ms 723 bytes (pipelined: 23)
Apr 12, 2018 17:29:05.880 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:05.880 [8524] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:05.882 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 1ms 723 bytes (pipelined: 24)
Apr 12, 2018 17:29:06.382 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:06.382 [10312] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:06.384 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 1ms 723 bytes (pipelined: 25)
Apr 12, 2018 17:29:06.890 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:06.891 [12960] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:06.892 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 1ms 723 bytes (pipelined: 26)
Apr 12, 2018 17:29:07.379 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:07.380 [10312] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:07.381 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 0ms 723 bytes (pipelined: 27)
Apr 12, 2018 17:29:07.881 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:07.881 [10452] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:07.883 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 1ms 723 bytes (pipelined: 28)
Apr 12, 2018 17:29:08.379 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:08.379 [12960] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:08.380 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 0ms 723 bytes (pipelined: 29)
Apr 12, 2018 17:29:08.881 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:08.882 [10312] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (16 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:08.883 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (16 live) GZIP 1ms 723 bytes (pipelined: 30)
Apr 12, 2018 17:29:09.378 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:09.379 [10452] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (14 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:09.379 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (14 live) GZIP 0ms 723 bytes (pipelined: 31)
Apr 12, 2018 17:29:09.880 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:09.880 [12960] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (14 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:09.882 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (14 live) GZIP 1ms 723 bytes (pipelined: 32)
Apr 12, 2018 17:29:10.381 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:10.381 [10312] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (14 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:10.383 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (14 live) GZIP 1ms 723 bytes (pipelined: 33)
Apr 12, 2018 17:29:10.882 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:10.882 [10524] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (14 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:10.884 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (14 live) GZIP 1ms 723 bytes (pipelined: 34)
Apr 12, 2018 17:29:11.381 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:11.381 [10452] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (14 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:11.383 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (14 live) GZIP 1ms 723 bytes (pipelined: 35)
Apr 12, 2018 17:29:11.881 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:11.881 [12960] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (14 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:11.883 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (14 live) GZIP 1ms 723 bytes (pipelined: 36)
Apr 12, 2018 17:29:12.178 [2680] DEBUG - NAT: UPnP, found device <http://10.0.0.163:8008/ssdp/device-desc.xml> with private address <10.0.0.75>
Apr 12, 2018 17:29:12.178 [2680] DEBUG - NAT: UPnP, not an IGD: <http://10.0.0.163:8008/ssdp/device-desc.xml>.
Apr 12, 2018 17:29:12.178 [2680] DEBUG - NAT: UPnP, didn't find usable IGD.
Apr 12, 2018 17:29:12.179 [2680] DEBUG - NAT: PMP, attempting mapping.
Apr 12, 2018 17:29:12.379 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:12.380 [10524] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (14 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:12.381 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (14 live) GZIP 1ms 723 bytes (pipelined: 37)
Apr 12, 2018 17:29:12.430 [2680] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Apr 12, 2018 17:29:12.430 [2680] DEBUG - NAT: UPnP, attempting port mapping.
Apr 12, 2018 17:29:12.430 [2680] DEBUG - NAT: UPnP, not an IGD: <http://10.0.0.163:8008/ssdp/device-desc.xml>.
Apr 12, 2018 17:29:12.430 [2680] DEBUG - NAT: UPnP, didn't find usable IGD.
Apr 12, 2018 17:29:12.880 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:12.880 [10452] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (14 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:12.882 [13084] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (14 live) GZIP 1ms 723 bytes (pipelined: 38)
Apr 12, 2018 17:29:13.094 [1308] DEBUG - NAT: UPnP, found device <http://10.0.0.163:8008/ssdp/device-desc.xml> with private address <10.0.0.75>
Apr 12, 2018 17:29:13.095 [1308] DEBUG - NAT: UPnP, not an IGD: <http://10.0.0.163:8008/ssdp/device-desc.xml>.
Apr 12, 2018 17:29:13.095 [1308] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
Apr 12, 2018 17:29:13.345 [1308] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Apr 12, 2018 17:29:13.352 [2680] DEBUG - PublicAddressManager: Mapping failed.
Apr 12, 2018 17:29:13.376 [1308] DEBUG - MyPlex: Sending Server Info to myPlex (user=ortsacknat@gmail.com, ip=, port=0)
Apr 12, 2018 17:29:13.378 [1308] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=360a44a1-22f2-4383-bf99-46efb448359b
Apr 12, 2018 17:29:13.381 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:13.381 [10312] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /myplex/account (14 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:13.383 [7220] DEBUG - Completed: [127.0.0.1:52839] 200 GET /myplex/account (14 live) GZIP 1ms 724 bytes (pipelined: 39)
Apr 12, 2018 17:29:13.828 [7220] DEBUG - handleStreamRead code 2: End of file
Apr 12, 2018 17:29:13.833 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:13.833 [12960] DEBUG - Request: [127.0.0.1:52839 (Loopback)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (13 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:13.834 [12960] DEBUG - Beginning read from two-way stream.
Apr 12, 2018 17:29:13.878 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:13.879 [10452] DEBUG - Request: [127.0.0.1:52841 (Loopback)] GET /myplex/account (13 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:13.879 [7220] DEBUG - Completed: [127.0.0.1:52841] 200 GET /myplex/account (13 live) GZIP 0ms 724 bytes (pipelined: 5)
Apr 12, 2018 17:29:14.175 [1308] DEBUG - HTTP 201 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=360a44a1-22f2-4383-bf99-46efb448359b
Apr 12, 2018 17:29:14.175 [1308] DEBUG - MyPlex: Published Mapping State response was 201
Apr 12, 2018 17:29:14.175 [1308] DEBUG - MyPlex: Got response for 034884cfb1bbe52dff18a3b296e9b3069f1387c7 ~ registered :0
Apr 12, 2018 17:29:14.179 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:14.180 [8524] DEBUG - Request: [127.0.0.1:52841 (Loopback)] PUT /myplex/refreshReachability (13 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:14.184 [1308] DEBUG - MyPlex: Updating device connections (from timer: 0)
Apr 12, 2018 17:29:14.184 [1308] DEBUG - HTTP requesting PUT https://plex.tv/devices/034884cfb1bbe52dff18a3b296e9b3069f1387c7?Connection[][uri]=http://10.0.0.75:32400&httpsEnabled=1&httpsRequired=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Apr 12, 2018 17:29:14.188 [2680] DEBUG - MyPlex: Sending Server Info to myPlex (user=ortsacknat@gmail.com, ip=, port=0)
Apr 12, 2018 17:29:14.189 [2680] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=42c4f215-74cb-4dcf-bd3c-bedc0b869e3b
Apr 12, 2018 17:29:14.304 [10008] DEBUG - EventSource: Got event [data] '<Message address="" port="0" asyncIdentifier="360a44a1-22f2-4383-bf99-46efb448359b" connectivity="0" command="notifyConnectivity"/>'
Apr 12, 2018 17:29:14.377 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:14.377 [10524] DEBUG - Request: [127.0.0.1:52840 (Loopback)] GET /myplex/account (6 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:14.378 [13084] DEBUG - Completed: [127.0.0.1:52840] 200 GET /myplex/account (6 live) GZIP 0ms 724 bytes (pipelined: 8)
Apr 12, 2018 17:29:14.877 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:14.878 [10452] DEBUG - Request: [127.0.0.1:52840 (Loopback)] GET /myplex/account (6 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:14.878 [7220] DEBUG - Completed: [127.0.0.1:52840] 200 GET /myplex/account (6 live) GZIP 0ms 724 bytes (pipelined: 9)
Apr 12, 2018 17:29:14.903 [1308] DEBUG - HTTP 200 response from PUT https://plex.tv/devices/034884cfb1bbe52dff18a3b296e9b3069f1387c7?Connection[][uri]=http://10.0.0.75:32400&httpsEnabled=1&httpsRequired=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Apr 12, 2018 17:29:14.984 [2680] DEBUG - HTTP 201 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=42c4f215-74cb-4dcf-bd3c-bedc0b869e3b
Apr 12, 2018 17:29:14.984 [2680] DEBUG - MyPlex: Published Mapping State response was 201
Apr 12, 2018 17:29:14.985 [2680] DEBUG - MyPlex: Got response for 034884cfb1bbe52dff18a3b296e9b3069f1387c7 ~ registered :0
Apr 12, 2018 17:29:14.985 [8524] DEBUG - MyPlex: Requesting reachability check.
Apr 12, 2018 17:29:14.985 [8524] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/034884cfb1bbe52dff18a3b296e9b3069f1387c7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=dd708764-5634-4738-b2d5-b894faeb1f08
Apr 12, 2018 17:29:14.989 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:14.989 [10312] DEBUG - Request: [127.0.0.1:52840 (Loopback)] PUT /myplex/refreshReachability (6 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:14.993 [2680] DEBUG - MyPlex: Last published value didn't change, we're done.
Apr 12, 2018 17:29:15.380 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:15.381 [10452] DEBUG - Request: [127.0.0.1:52935 (Loopback)] GET /myplex/account (7 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:15.382 [13084] DEBUG - Completed: [127.0.0.1:52935] 200 GET /myplex/account (7 live) GZIP 1ms 780 bytes (pipelined: 1)
Apr 12, 2018 17:29:15.709 [8524] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/034884cfb1bbe52dff18a3b296e9b3069f1387c7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=dd708764-5634-4738-b2d5-b894faeb1f08
Apr 12, 2018 17:29:15.709 [10008] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (360a44a1-22f2-4383-bf99-46efb448359b, expected dd708764-5634-4738-b2d5-b894faeb1f08)
Apr 12, 2018 17:29:15.710 [10312] DEBUG - MyPlex: Requesting reachability check.
Apr 12, 2018 17:29:15.710 [10008] DEBUG - EventSource: Got event [data] '<Message address="" port="0" asyncIdentifier="42c4f215-74cb-4dcf-bd3c-bedc0b869e3b" connectivity="0" command="notifyConnectivity"/>'
Apr 12, 2018 17:29:15.710 [13084] DEBUG - Completed: [127.0.0.1:52841] 200 PUT /myplex/refreshReachability (7 live) GZIP 1530ms 268 bytes (pipelined: 6)
Apr 12, 2018 17:29:15.711 [10312] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/034884cfb1bbe52dff18a3b296e9b3069f1387c7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=be91eebb-0bdc-48d8-a96c-494be8a5edc5
Apr 12, 2018 17:29:16.432 [10312] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/034884cfb1bbe52dff18a3b296e9b3069f1387c7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=be91eebb-0bdc-48d8-a96c-494be8a5edc5
Apr 12, 2018 17:29:16.433 [10008] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (42c4f215-74cb-4dcf-bd3c-bedc0b869e3b, expected be91eebb-0bdc-48d8-a96c-494be8a5edc5)
Apr 12, 2018 17:29:16.433 [10008] DEBUG - EventSource: Got event [data] '<Message address="" port="0" asyncIdentifier="dd708764-5634-4738-b2d5-b894faeb1f08" connectivity="0" command="notifyConnectivity"/>'
Apr 12, 2018 17:29:16.433 [13084] DEBUG - Completed: [127.0.0.1:52840] 200 PUT /myplex/refreshReachability (7 live) GZIP 1443ms 268 bytes (pipelined: 10)
Apr 12, 2018 17:29:16.433 [10008] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (dd708764-5634-4738-b2d5-b894faeb1f08, expected be91eebb-0bdc-48d8-a96c-494be8a5edc5)
Apr 12, 2018 17:29:16.559 [10008] DEBUG - EventSource: Got event [data] '<Message address="" port="0" asyncIdentifier="be91eebb-0bdc-48d8-a96c-494be8a5edc5" connectivity="0" command="notifyConnectivity"/>'
Apr 12, 2018 17:29:16.559 [10008] DEBUG - PubSub: Got notified of reachability: 0 for :0
Apr 12, 2018 17:29:16.565 [7220] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:16.566 [10452] DEBUG - Request: [127.0.0.1:52840 (Loopback)] GET /myplex/account (7 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:16.568 [13084] DEBUG - Completed: [127.0.0.1:52840] 200 GET /myplex/account (7 live) GZIP 1ms 787 bytes (pipelined: 11)
Apr 12, 2018 17:29:21.505 [13084] DEBUG - Auth: authenticated user 1 as KSMKxBRUTALITYx
Apr 12, 2018 17:29:21.506 [12960] DEBUG - Request: [127.0.0.1:52840 (Loopback)] GET /diagnostics/logs (7 live) GZIP Signed-in Token (KSMKxBRUTALITYx)
Apr 12, 2018 17:29:21.506 [12960] DEBUG - Diagnostics: Building logfile zip
I’m also losing remote access with the latest beta (on Qnap). I have to hit apply on “manually specify public port” for it to re-allow remote access, then at some point I will losing it again. I’ll do more testing.
Same here - my plex server all of a sudden a.) isn’t useable outside my home network and b.) shows the wrong IP on the remote access page. It’s as if it no longer recognizes that I’m on a VPN (it HAS been working for quite some time - my VPN allows port forwarding). Logs attached. I’ve tried everything (yes, all the appropriate troubleshooting) and nothing has worked.
Is the latest update broken?
I’m on a QNAP TS-453A and I have NIC’s 1+2 working in tandem. This, too, has been working just fine for a while now.
Same here. Remote access check fails with logs showing “incorrect async identifier” each time the check is invoked.
Using a web browser to connect directly to the plex server’s external network https://IP:port works fine, so it’s not a local network issue as far as I can tell.
Downgrading to version 1.12.2.4929 did not resolve it.
EDIT: and then it suddenly started working again, with no changes on my end.
EDIT2: it’s connecting to eu-west-1.compute.amazonaws.com. That’s a bit odd that it woudn’t be connecting to something closer, ie. in the US.
I reverted to 1.12.2.4929 , rebooted my Qnap and it’s not losing remote access anymore. BTW: I’m also using 2 NIC in tandem.
I’m having this problem too. Restarting Plex fix the problem but it happens again about 2-3 times per day.
I am having similar problem since update (to Version 1.12.3.4973 ).
2-2 times per day the server is unaccessible either on Mac or via Apps on AppleTV. Cannot even restart, must reboot MacPro to gain access, but only works for a few hours until becoming unresponsive.
@lancegspencer said:
I am having similar problem since update (to Version 1.12.3.4973 ).2-2 times per day the server is unaccessible either on Mac or via Apps on AppleTV. Cannot even restart, must reboot MacPro to gain access, but only works for a few hours until becoming unresponsive.
Is your issue with remote access or also on the server itself and local network?
server is unaccessible either on Mac
That sounds like different from remote access not working
As a general point
I’ve been having multiple issues regarding remote access with 1.12.3.4973. I’m actually relieved now (misery loves company ). I’ve found that with absolute certainty, If I specify a port in settings, that port will fail and remote access will be lost - maybe immediately, maybe in a few minutes or hours. The next thing I have to do is continually retry without specifying the port and eventually, I’ll reconnect.
@grandpacarp said:
I’ve been having multiple issues regarding remote access with 1.12.3.4973. I’m actually relieved now (misery loves company ). I’ve found that with absolute certainty, If I specify a port in settings, that port will fail and remote access will be lost - maybe immediately, maybe in a few minutes or hours. The next thing I have to do is continually retry without specifying the port and eventually, I’ll reconnect.
If you specify a public port in server settings for remote access - you must also make sure you have setup a port forward for that tcp public/wan port to forward to tcp port 32400 to the local IP address of the server - which must be fixed - eg as a DHCP Reservation
@sa2000 said:
@grandpacarp said:
I’ve been having multiple issues regarding remote access with 1.12.3.4973. I’m actually relieved now (misery loves company ). I’ve found that with absolute certainty, If I specify a port in settings, that port will fail and remote access will be lost - maybe immediately, maybe in a few minutes or hours. The next thing I have to do is continually retry without specifying the port and eventually, I’ll reconnect.If you specify a public port in server settings for remote access - you must also make sure you have setup a port forward for that tcp public/wan port to forward to tcp port 32400 to the local IP address of the server - which must be fixed - eg as a DHCP Reservation
Yes, I’ve had the same port setup for a few years of plex use. But everything port-wise fell to pieces with this update. I can port forward on my router all day long, it’s when I specify a port in the setup that everything fails. To get by, I stopped specifying the port in plex and all is good.
@grandpacarp said:
@sa2000 said:
@grandpacarp said:
I’ve been having multiple issues regarding remote access with 1.12.3.4973. I’m actually relieved now (misery loves company ). I’ve found that with absolute certainty, If I specify a port in settings, that port will fail and remote access will be lost - maybe immediately, maybe in a few minutes or hours. The next thing I have to do is continually retry without specifying the port and eventually, I’ll reconnect.If you specify a public port in server settings for remote access - you must also make sure you have setup a port forward for that tcp public/wan port to forward to tcp port 32400 to the local IP address of the server - which must be fixed - eg as a DHCP Reservation
Yes, I’ve had the same port setup for a few years of plex use. But everything port-wise fell to pieces with this update. I can port forward on my router all day long, it’s when I specify a port in the setup that everything fails. To get by, I stopped specifying the port in plex and all is good.
There has been no changes to this area in Plex Media Server. Could be something else coincided with the server version update
Interesting post this, I’m having the same sort of issues, suddenly all three servers of mine are off line, The only what to fix them is RDC onto the Windows Console and restart plex, then it’s fine for a while. I’m getting about 5-6 hours before each of them start to drop off.
@systemshark said:
Interesting post this, I’m having the same sort of issues, suddenly all three servers of mine are off line, The only what to fix them is RDC onto the Windows Console and restart plex, then it’s fine for a while. I’m getting about 5-6 hours before each of them start to drop off.
Please upload server logs after you notice the issue.
Please remember if you have multiple NICs enabled then remote access may not work very well and the outcome may vary from version to version as the timing may change. So ensure only one Network Interface active - the one to which you have the Port Forward set up for
See
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
After ensuring debug logging is enabled, please restart the servers to get fresh logs created and when you notice the problem and actually confirm it by failure to connect to the server remotely then gather the logs from each server that fails in this way
That would be sufficient for initial investigation - normally it would also wish to see the router setup for port forwards / DHCP reservations / DHCP range if config of the server if static IP address
@KSMKxBRUTALITYx said:
It is not allowing me to post the log file but ever since update 1.12.3.4947 my remote access is no longer working. I attempted all port forwarding solutions and checked everything possible in the firewall, nothing has changed but the update and now my remote access reads as “Not available outside your network
Your server is signed in to Plex, but is not reachable from outside your network.”Log info in comments as the file wont upload
Are you still have problem with getting remote access to work
As mentioned in my other posts here, it would be more reliable to have a port forward and select manually specify port in the server remote access settings
With regards to logs uploads - may be your forum account email address was not verified at the time. It is verified so hopefully you would be able to attach the zipped logs
I was having a similar issue since Monday, except instead of ALL remote connections failing it was only connections going through Plex Relay. Disabling my secondary Realtek NIC fixed the issue, which happened whether or not it was even plugged in, though I’d had it plugged in and running flawlessly for the past ~9 months. It wasn’t in tandem like the posters above, but actually a second internet line. Here are my logs, I disabled the NIC somewhere in the middle of them. I’m running the latest beta update.
So I’ve managed to fix mine.
I’ve deleted all my servers from the Settings /Device Menu and Re - signed in on each. Somehow I think I have two servers appears on 1 machine in the Device/Servers List, I think it was when the second machine was built from a backup of the first machine. (and yes both machines where named differently, MonsterPlex and Erica).
Both my servers use Bonded Ethernet ports to present a single high available, high capacity port, this I’ve retained as on my machines it’s a red herring for me!
Thanks for follow up @sa2000
I’ve had this problem before and one thing that helped was not to use firefox, for some reason firefox caches the ‘not connected’ display.
I’ve also all of the sudden starting having this issue after years of using the same configuration/port. I’m getting an “indirect connection” when checking from my phone. Server page says Not available outside your network and friends have reported that this started happening about 2 weeks ago which is coincidentally around when I upgraded to 1.12.1.4885. I can hit port checking websites all day long that tell me 32400 is open on my router.
I can sometimes get it to work for a few minutes when unselecting a manual port and going with whatever it chooses, but then that quits after a short while too. Doing the opposite, going from auto to manual does the same thing…works for a few minutes, then dies. I’m at a loss.
Perusing the logs I can’t make heads or tails out of why it’s doing that. I even changed my port to 443 as I see it doing in the relay and opened that port up to test. Turned off Firewall on Router…nothing seem to get it working.
