Errors enabling Remote Access

General Discussions
1

Enabling Remote Access in Plex continues to be an exercise in futility. My previous post may be too old to get any attention so I’m starting a new one in the hopes Plex support staff will provide a solution.

It actually worked for most of the weekend until my PC lost power. Before this last weekend, it wasn’t connecting and then it just started working for no apparent reason on Friday. I did nothing. It just did it on its own after the server had been running for about a week.

Below is the section of my plex server log that contains the errors I’m seeing. Does this provide enough information to determine the cause and what needs to be done to fix it?

Oct 10, 2016 08:43:17.722 [7260] INFO - Plex Media Server v1.1.4.2757-24ffd60 - Microsoft PC x64 - build: windows-i386 english - GMT -06:00
Oct 10, 2016 08:43:17.722 [7260] INFO - Windows version: 10.0 (Build 14393), language en-US
Oct 10, 2016 08:43:17.722 [7260] INFO - 4 2095 MHz processor(s): Architecture=0, Level=6, Revision=15620 Processor Identifier=Intel64 Family 6 Model 61 Stepping 4, GenuineIntel
Oct 10, 2016 08:43:19.463 [6336] INFO - Successfully retrieved OCSP response
Oct 10, 2016 08:43:23.549 [1176] INFO - LibraryUpdateManager path watching is disabled
Oct 10, 2016 08:43:24.845 [6336] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Oct 10, 2016 08:43:24.992 [3648] INFO - Sync: downloaded 0 sync list(s) with 0 sync items(s): 0 new, 0 updated, 0 deleted
Oct 10, 2016 08:43:25.446 [4408] ERROR - Network Service: Error in browser handle read: 995 (The I/O operation has been aborted because of either a thread exit or an application request) socket=-1
Oct 10, 2016 08:43:25.562 [4408] INFO - Network Service: Abandoning browse socket, it was closed.
Oct 10, 2016 08:43:27.250 [5668] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Oct 10, 2016 08:43:31.251 [10236] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Oct 10, 2016 08:43:32.867 [3644] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (21c28540-0a05-4462-9f24-fc8ff94d4da1, expected 62a55954-9116-4c2f-9a2e-1c1b0dcb71a7)
Oct 10, 2016 08:43:33.614 [5716] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (ee4f9449-8249-414b-aa47-4e1900992071, expected 83f25b7e-3278-4ee2-b570-c8ef46567c92)
Oct 10, 2016 08:43:33.614 [3644] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (ad890d59-1d94-4d64-953c-f147f8e24353, expected 83f25b7e-3278-4ee2-b570-c8ef46567c92)
Oct 10, 2016 08:43:33.614 [5716] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (62a55954-9116-4c2f-9a2e-1c1b0dcb71a7, expected 83f25b7e-3278-4ee2-b570-c8ef46567c92)
Oct 10, 2016 08:43:59.921 [3644] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (3b1cbd47-206e-478c-9091-bc91d84403ef, expected 13d21e41-be26-4354-ab4d-82bb1e282cd2)
Oct 10, 2016 08:44:04.761 [0432] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Oct 10, 2016 08:44:07.165 [10388] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Oct 10, 2016 08:44:08.803 [3644] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (911b70d5-cb64-4ac8-b4dd-02c2b72fbda2, expected 1dd5d2df-a487-499d-8cda-3ad84ae5311c)

2

Your logs are too short to identify the problem. You’ll need to provide the full log. Best would be to restart PMS, wait 3 minutes without doing anything, then provide the log.

As suggested in your previous post, I would set up manual port forwarding. You are correct that you should not need to do it and allow UPnP to automatically make the right connections. However, UPnP is not very reliable. I would not be surprised if after you set up port forwarding, all your problems go away.

3

I muddled through setting up port forwarding for my CenturyLink C1900A router by adapting these generic instructions successfully. Having never succeeded at port forwarding before, so far so good. Thank you MovieFan.Plex for your assistance.