Server 2016 remote connection, are there logs?

Plex Media Server Desktops & Laptops
1

Hi all,

Im port forwarding from outside the network. All other ports forwarded are working fine (mail, remote access ect) except for Plex. If I retry it, it goes green for a second. Then back to red.

Are there logs for this, that will give me more information, where it fails, why it fails?

Server 2016
Direct NAT

Im just getting to the point where I’m wondering if a plex pass subscription is worth it anymore.

No Alexa (no remote access)
Android PMP doesn’t support 4K content
No support on the forums

Why am I paying money for this?

2

Have the exact same problem. Only Plex is having issues with the forwarded port. Everything else works. Tried changing ports, disabling Windows Firewall, reinstalling PMS, even did a clean install of Server 2016. Nothing has gotten it to stay open. And external port checkers show the port being closed.

Wireshark shows the inital packets coming in, but when Plex tries to respond it shows TCP retransmission errors.

Turning of verbose logging, I get these entries:

Jul 29, 2018 01:35:32.245 [0468] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af, expected 3d1dc0c4-2014-4a2a-8f29-3dd30f4dd89a)
Jul 29, 2018 01:35:32.245 [4212] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af, expected 3d1dc0c4-2014-4a2a-8f29-3dd30f4dd89a)
Jul 29, 2018 01:35:32.245 [0468] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af, expected d55629a5-e31b-4f05-8db0-39c323df0074)
Jul 29, 2018 01:35:32.245 [4212] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af, expected d55629a5-e31b-4f05-8db0-39c323df0074)
Jul 29, 2018 01:35:32.245 [0468] DEBUG - EventSource: Got event [data] '<Message address="$EXTIP" port="32400" asyncIdentifier="42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af" connectivity="0" command="notifyConnectivity"/>'
Jul 29, 2018 01:35:32.245 [4212] DEBUG - EventSource: Got event [data] '<Message address="$EXTIP" port="32400" asyncIdentifier="42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af" connectivity="0" command="notifyConnectivity"/>'
Jul 29, 2018 01:35:32.245 [0468] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af, expected 3d1dc0c4-2014-4a2a-8f29-3dd30f4dd89a)
Jul 29, 2018 01:35:32.245 [4212] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af, expected 3d1dc0c4-2014-4a2a-8f29-3dd30f4dd89a)
Jul 29, 2018 01:35:32.245 [0468] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af, expected d55629a5-e31b-4f05-8db0-39c323df0074)
Jul 29, 2018 01:35:32.245 [4212] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (42b100b5-37ad-4cae-a1a7-b1c8fa8fa6af, expected d55629a5-e31b-4f05-8db0-39c323df0074)

I know its not a problem with Plex and my WAN firewall, because it works if I run PMS on Windows 10 or OS X.

3

Common???

We are both paying customers, can we not get a little support on this???

4

This is ■■■■, provided all this info and not one member of staff can offer anything?

5

So I ran the latest update, worked for about 20 mins and then died.

AGAIN

Pity Plex has abandoned its users and just couldn’t give a ■■■■ about its customers anymore

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.