Server shows unavailable outside network, but it actually is available, why?

General Discussions
1

I recently switched from a home built Untangle firewall/router to a Ubiquiti Edgerouter Lite 3. It took me quite a while to get plex going on the new firewall, but after a few days tinkering it worked.

For about 10 minutes or so the check mark was green, and I could in fact get to my server over LTE on my phone. After a while though the light went red, but access stayed on.

So what is it that tells plex it’s connected and keeps the green check mark? It’s obviously not preventing the server from working, it’s juts annoying that it says it’s not working when it actually is.

2

The green check mark only means that plex.tv ( basically acting as a Dynamic DNS) has your server servers IP address and it matches. it is red if it doesn’t have it. when you sign into a device it checks plex.tv for server IPs you have access to and then connects.

regardless if Plex.tv has your server info if the player app already has the info cached (and valid authorization token) from a previous connection it will connect again.

3

Q: When at home I can stream my movie’s from my PC to my Android Samsung 7 phone, but it won’t stream my Music?
Also when I’m away from home I cant stream anything…Why is that? I have a Plexpass!
Can someone give any advice on this please.

4

Q: When at home I can stream my movie’s from my PC to my Android Samsung 7 phone, but it won’t stream my Music?

I don’t know what that means. the music library is not available, or available and not playing?

Also when I’m away from home I cant stream anything…Why is that? I have a Plexpass!

Plex Pass will not configure your network for you. Remote access is free, it is not a Plex Pass feature and will not work just because you have a Plex pass. You need to configure your router for port forwarding if UPnP is not working for your home network

5

Okay, that makes sense. So what can I do then to keep the connection going? I see the server from one device, but not another, that one says “couldn’t connect to server.” Is there a known trick or config I can put into my router?

6

Assuming you have port forwarding set up, properly. I would next check your regular DNS server in your router first. If it is is using your ISPs default DNS servers I would try Google DNS. ( you can also just set it up on your server computer rather than the router.) https://developers.google.com/speed/public-dns/

I have never used a Ubiquiti router so don’t know if there are any quirks with it.

7

The ubiquity router is running Dnsmasq in the background with their UI on top, basically. I was previously running Google DNS but switched to the new Cloudflare DNS. Both behaved the same. So I have port forwarding enabled, and the port is visible to the app.

Setup looks like this WAN -> Ubiquity Router (dhcp and dns server, 127.0.0.1 for self with forwarding to 1.1.1.1) -> Port forwarding with auto firewall rules to 32400 for internal IP 10.0.1.201 (Ubuntu 16.04 Server, Plex). Pretty straight forward. There’s just got to be one little piece I’m missing on the router to keep this like, I’m assuming it’s DNS now based on your responses. So I’ll dig into that some more.

8

EDIT: IP is fine… issue is in Remote Connection:

The two that stand out to me are:

Apr 04, 2018 15:11:01.829 [0x7fef2b7ff700] DEBUG - CERT: incomplete TLS handshake: short read

and

Apr 04, 2018 15:11:01.967 [0x7fef26bfc700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (5c50673c-c1ab-40e8-9a46-d1b3f84539b9, expected e3099184-0d3f-48a0-9eaa-ae18565172b4)

full log from connection attempt:

Apr 04, 2018 15:10:33.419 [0x7fef2affe700] DEBUG - handleStreamRead code 335544539: short read
Apr 04, 2018 15:10:33.427 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:33.427 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57853 (Subnet)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:33.427 [0x7fef0d7fe700] DEBUG - Beginning read from two-way stream.
Apr 04, 2018 15:10:40.423 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:40.423 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] PUT /:/prefs?PublishServerOnPlexOnlineKey=true (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:40.472 [0x7fef2c7ff700] DEBUG - MyPlex: Toggling server publish state.
Apr 04, 2018 15:10:40.472 [0x7fef2c7ff700] DEBUG - PublicAddressManager: Starting.
Apr 04, 2018 15:10:40.472 [0x7fef2c7ff700] DEBUG - PublicAddressManager: Obtaining public address and mapping port.
Apr 04, 2018 15:10:40.472 [0x7fef253ff700] DEBUG - PublicAddressManager: Obtaining public IP.
Apr 04, 2018 15:10:40.472 [0x7fef253ff700] DEBUG - HTTP requesting GET http://plex.tv/pms/:/ip
Apr 04, 2018 15:10:40.473 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 PUT /:/prefs?PublishServerOnPlexOnlineKey=true (8 live) TLS GZIP 49ms 268 bytes (pipelined: 1)
Apr 04, 2018 15:10:40.482 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:40.482 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:40.484 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 2)
Apr 04, 2018 15:10:40.743 [0x7fef253ff700] DEBUG - HTTP 200 response from GET http://plex.tv/pms/:/ip
Apr 04, 2018 15:10:40.744 [0x7fef253ff700] DEBUG - PublicAddressManager: Got public IP from http://plex.tv: 68.69.161.216
Apr 04, 2018 15:10:40.996 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:40.996 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:40.998 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 3)
Apr 04, 2018 15:10:41.496 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:41.497 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:41.498 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 4)
Apr 04, 2018 15:10:41.997 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:41.997 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:41.999 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 5)
Apr 04, 2018 15:10:42.498 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:42.498 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:42.500 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 6)
Apr 04, 2018 15:10:42.997 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:42.998 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:42.999 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 7)
Apr 04, 2018 15:10:43.498 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:43.498 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:43.500 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 8)
Apr 04, 2018 15:10:43.998 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:43.998 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:44.000 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 9)
Apr 04, 2018 15:10:44.498 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:44.499 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:44.501 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 10)
Apr 04, 2018 15:10:44.998 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:44.998 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:45.000 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 11)
Apr 04, 2018 15:10:45.499 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:45.499 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:45.501 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 12)
Apr 04, 2018 15:10:46.000 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:46.000 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:46.002 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 13)
Apr 04, 2018 15:10:46.500 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:46.501 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:46.502 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 14)
Apr 04, 2018 15:10:47.000 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:47.000 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:47.002 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 15)
Apr 04, 2018 15:10:47.499 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:47.499 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:47.501 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 16)
Apr 04, 2018 15:10:47.998 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:47.999 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:48.000 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 2ms 798 bytes (pipelined: 17)
Apr 04, 2018 15:10:48.498 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:48.498 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:48.500 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 18)
Apr 04, 2018 15:10:48.997 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:48.998 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:49.000 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 2ms 798 bytes (pipelined: 19)
Apr 04, 2018 15:10:49.497 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:49.498 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:49.499 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 20)
Apr 04, 2018 15:10:49.996 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:49.996 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:49.998 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 21)
Apr 04, 2018 15:10:50.496 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:50.496 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:50.498 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 22)
Apr 04, 2018 15:10:50.756 [0x7fef253ff700] DEBUG - NAT: UPnP, found device <http://10.0.1.201:32469/DeviceDescription.xml> with private address <10.0.1.201>
Apr 04, 2018 15:10:50.756 [0x7fef253ff700] DEBUG - NAT: UPnP, not an IGD: <http://10.0.1.201:32469/DeviceDescription.xml>.
Apr 04, 2018 15:10:50.756 [0x7fef253ff700] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
Apr 04, 2018 15:10:50.997 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:50.997 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:50.999 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 798 bytes (pipelined: 23)
Apr 04, 2018 15:10:51.007 [0x7fef253ff700] WARN - NAT: PMP, got an error: Not Supported by gateway.
Apr 04, 2018 15:10:51.010 [0x7fef253ff700] DEBUG - MyPlex: Sending Server Info to myPlex (user=redacted, ip=, port=32400)
Apr 04, 2018 15:10:51.011 [0x7fef253ff700] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=5c50673c-c1ab-40e8-9a46-d1b3f84539b9
Apr 04, 2018 15:10:51.497 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:51.497 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:51.499 [0x7fef2b7ff700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (8 live) TLS GZIP 1ms 799 bytes (pipelined: 24)
Apr 04, 2018 15:10:51.659 [0x7fef253ff700] DEBUG - HTTP 201 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=5c50673c-c1ab-40e8-9a46-d1b3f84539b9
Apr 04, 2018 15:10:51.659 [0x7fef253ff700] DEBUG - MyPlex: Published Mapping State response was 201
Apr 04, 2018 15:10:51.660 [0x7fef253ff700] DEBUG - MyPlex: Got response for d974ad5c078af8c9f97c203308f8455820982975 ~ registered :0
Apr 04, 2018 15:10:51.660 [0x7fef253ff700] DEBUG - MyPlex: Updating device connections (from timer: 0)
Apr 04, 2018 15:10:51.660 [0x7fef253ff700] DEBUG - HTTP requesting PUT https://plex.tv/devices/d974ad5c078af8c9f97c203308f8455820982975?Connection[][uri]=http://10.0.1.201:32400&httpsEnabled=1&httpsRequired=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Apr 04, 2018 15:10:51.667 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:51.667 [0x7fef2c7ff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] PUT /myplex/refreshReachability (8 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:51.667 [0x7fef2c7ff700] DEBUG - MyPlex: Requesting reachability check.
Apr 04, 2018 15:10:51.668 [0x7fef2c7ff700] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/d974ad5c078af8c9f97c203308f8455820982975/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=e3099184-0d3f-48a0-9eaa-ae18565172b4
Apr 04, 2018 15:10:52.001 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:52.001 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57871 (Subnet)] GET /myplex/account (10 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:52.003 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57871] 200 GET /myplex/account (10 live) TLS GZIP 1ms 854 bytes (pipelined: 1)
Apr 04, 2018 15:10:52.229 [0x7fef253ff700] DEBUG - HTTP 200 response from PUT https://plex.tv/devices/d974ad5c078af8c9f97c203308f8455820982975?Connection[][uri]=http://10.0.1.201:32400&httpsEnabled=1&httpsRequired=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Apr 04, 2018 15:10:52.233 [0x7fef2c7ff700] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/d974ad5c078af8c9f97c203308f8455820982975/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=e3099184-0d3f-48a0-9eaa-ae18565172b4
Apr 04, 2018 15:10:52.234 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 PUT /myplex/refreshReachability (10 live) TLS GZIP 567ms 268 bytes (pipelined: 25)
Apr 04, 2018 15:10:52.364 [0x7fef26bfc700] DEBUG - EventSource: Got event [data] '<Message address="" port="0" asyncIdentifier="e3099184-0d3f-48a0-9eaa-ae18565172b4" connectivity="0" command="notifyConnectivity"/>'
Apr 04, 2018 15:10:52.364 [0x7fef26bfc700] DEBUG - PubSub: Got notified of reachability: 0 for :0
Apr 04, 2018 15:10:52.371 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:52.371 [0x7fef0d7fe700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /myplex/account (10 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:52.373 [0x7fef2affe700] DEBUG - Completed: [10.0.1.205:57862] 200 GET /myplex/account (10 live) TLS GZIP 1ms 861 bytes (pipelined: 26)
Apr 04, 2018 15:10:53.427 [0x7fef2b7ff700] DEBUG - handleStreamRead code 335544539: short read
Apr 04, 2018 15:10:53.435 [0x7fef2affe700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:10:53.436 [0x7fef0dfff700] DEBUG - Request: [10.0.1.205:57862 (Subnet)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (9 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:10:53.436 [0x7fef0dfff700] DEBUG - Beginning read from two-way stream.
Apr 04, 2018 15:11:01.829 [0x7fef2b7ff700] DEBUG - CERT: incomplete TLS handshake: short read
Apr 04, 2018 15:11:01.967 [0x7fef26bfc700] DEBUG - EventSource: Got event [data] '<Message address="68.69.xxx.xxx" port="32400" asyncIdentifier="5c50673c-c1ab-40e8-9a46-d1b3f84539b9" connectivity="0" command="notifyConnectivity"/>'
Apr 04, 2018 15:11:01.967 [0x7fef26bfc700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (5c50673c-c1ab-40e8-9a46-d1b3f84539b9, expected e3099184-0d3f-48a0-9eaa-ae18565172b4)
Apr 04, 2018 15:11:13.437 [0x7fef2b7ff700] DEBUG - handleStreamRead code 335544539: short read
Apr 04, 2018 15:11:13.450 [0x7fef2b7ff700] DEBUG - Auth: authenticated user 1 as SuperSecret
Apr 04, 2018 15:11:13.450 [0x7fef26bfc700] DEBUG - Request: [10.0.1.205:57875 (Subnet)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (7 live) TLS GZIP Signed-in Token (SuperSecret)
Apr 04, 2018 15:11:13.451 [0x7fef26bfc700] DEBUG - Beginning read from two-way stream.
9

Hi,

the incorrect async identifier is an issue the teams are already looking into that does seem to be the cause of your issue. a Mismatch between a new state of server and what we have at plex.tv.

I am told a browser refresh on settings page might correct the display of red dot to correct what it actually is but i have a feeling after this much time you have already done that. It seems like this issue has happens after an upgrade to new version of server.

it was recommended that if you toggle the Remote Access enable that you wait a couple minutes before switching it from disabled to ensabled or vice versa. the quick flipping of it off then on we think can cause it.

10

The following warning log entry was actually not a factor

Apr 04, 2018 15:11:01.967 [0x7fef26bfc700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (5c50673c-c1ab-40e8-9a46-d1b3f84539b9, expected e3099184-0d3f-48a0-9eaa-ae18565172b4)

It happens due to timing issues when multiple requests get made and events received out of sequence - it should settle after a while when viewing the remote access settings page. Refreshing the browser may help. Rapid clicking on retry could give rise to such timing issues - but they also arise when enabling remote access

As I said, this time, within the log extract you provided, it did not have an impact

When viewing the remote access settings page and remote access is enabled, a reachability test is requested by the server

Apr 04, 2018 15:10:51.667 [0x7fef2c7ff700] DEBUG - MyPlex: Requesting reachability check.
Apr 04, 2018 15:10:51.668 [0x7fef2c7ff700] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/d974ad5c078af8c9f97c203308f8455820982975/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=e3099184-0d3f-48a0-9eaa-ae18565172b4

what happens next should be a WAN request - typically from WAN IP 50.xx.xx.xx or 54.xx.xx.xx for /identity
If this is received by the server and responded to, then a Pubsub event is received for the public wan and port with a success indication connectivity="1"

In your case I cannot see any WAN GET /identity request coming in and the event received confirms the failure to get through

Apr 04, 2018 15:11:01.967 [0x7fef26bfc700] DEBUG - EventSource: Got event [data] '<Message address="68.69.xxx.xxx" port="32400" asyncIdentifier="5c50673c-c1ab-40e8-9a46-d1b3f84539b9" connectivity="0" command="notifyConnectivity"/>'

So you have a port forward in the router ? to forward requests coming into WAN Port 32400 to go to local port 32400 for 10.0.1.201 ?

You could use wireshark to see if the WAN http request for /identity does reach the server

These errors are relevant

Apr 04, 2018 15:10:50.756 [0x7fef253ff700] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
. . . 
Apr 04, 2018 15:10:51.007 [0x7fef253ff700] WARN - NAT: PMP, got an error: Not Supported by gateway.

The public IP is confirmed by querying the router - but that failed - so the cached IP held in plex.tv was used.
If that cached IP is correct then that router error would not have mattered
If the Public IP held by plex.tv for the server is wrong then the connectivity test would fail.
You can check that out and eliminate it as a possibility

11

@BigWheel that is good to know, thank you.

@sa2000 Your vast knowledge never ceases to amaze me. Thank you very much for the insight. I worked with some of the folks on the Ubiquiti side and they identified the issue as the router itself! It is incorrectly handling SSL traffic when hardware offloading of PPPoE is enabled. I had all the correct port forward and nat options set up and could see the port as open from the outside, but this SSL error was what caused the connection to fail. They’ve logged the bug and are working to fix it.

Note that during all of this debugging I did swap back to my Untangle router box and Plex worked 100% as expected, further showing that the issue was with the Ubiquiti router and not Plex.

12

Thanks for the update.