Plex Update 1.10.1.4602 seems to break remote connectivity

General Discussions
61

Excellent, so everything is back to how it was, except I am now operating a fresh PMS install, I also remove all instances of my old server in devices.

Just a shame I have to start again, but not the end of the world, My brother is now happily watching Harry Potter 50 miles away though :slight_smile:

@ChuckPA said:
That does make sense.

I checked the results of your last connectivity test with Plex.tv. It shows connected which is confirmed in your logs.

You should be good to go

Dec 23, 2017 14:51:17.829 [0x70000ef14000] DEBUG - NAT: UPnP, found device <http://192.168.0.1:5431/dyndev/uuid:7050aff9-0b78-780b-f9af-507050f9780000> with private address <192.168.0.25>
Dec 23, 2017 14:51:17.836 [0x70000ef14000] DEBUG - NAT: UPnP, usable device <http://192.168.0.1:5431/dyndev/uuid:7050aff9-0b78-780b-f9af-507050f9780000> with private address <192.168.0.25>.
Dec 23, 2017 14:51:17.839 [0x70000ef14000] DEBUG - NAT: UPnP, public address is 94.195.42.133
Dec 23, 2017 14:51:17.840 [0x70000f6c1000] DEBUG - MyPlex: Sending Server Info to myPlex (user=mrhyde@me.com, ip=, port=13304)
Dec 23, 2017 14:51:17.840 [0x70000ef14000] DEBUG - MyPlex: Last published value didn't change, we're done.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to pubsub.plex.tv was 24 ms.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to 139.162.245.220 was 28 ms.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to 82.94.168.54 was 37 ms.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to 85.90.244.55 was 64 ms.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to 50.116.51.249 was 179 ms.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to 45.79.210.23 was 196 ms.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to 45.79.11.43 was 265 ms.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to 184.105.148.101 was 278 ms.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to 139.162.7.93 was 372 ms.
Dec 23, 2017 14:51:17.847 [0x70000f63e000] DEBUG - PubSubManager: Time to connect to 139.162.115.125 was 485 ms.
Dec 23, 2017 14:51:17.848 [0x70000f63e000] DEBUG - PubSubManager: Updating best ping time for pubsub.plex.tv to 24 ms.
Dec 23, 2017 14:51:17.849 [0x70000f6c1000] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=6b403f68-8498-4840-bc33-25eb948a206d
Dec 23, 2017 14:51:17.999 [0x70000f6c1000] DEBUG - HTTP 201 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=6b403f68-8498-4840-bc33-25eb948a206d
Dec 23, 2017 14:51:18.000 [0x70000f6c1000] DEBUG - MyPlex: Published Mapping State response was 201
Dec 23, 2017 14:51:18.000 [0x70000f6c1000] DEBUG - MyPlex: Got response for ef5c5f324bcbff93c8b5701404ccff483853a3a6 ~ registered :0
Dec 23, 2017 14:51:18.000 [0x70000eb7f000] DEBUG - MyPlex: Requesting reachability check.
Dec 23, 2017 14:51:18.010 [0x70000eb7f000] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/ef5c5f324bcbff93c8b5701404ccff483853a3a6/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=99cd8180-03fd-4d2e-9b02-e2cfff35ee47
Dec 23, 2017 14:51:18.105 [0x70000ea79000] DEBUG - Request: [54.229.99.71:28093 (WAN)] GET /identity (11 live) TLS Signed-in Token (MrHyde)
Dec 23, 2017 14:51:18.106 [0x70000e249000] DEBUG - Completed: [54.229.99.71:28093] 200 GET /identity (11 live) TLS 1ms 357 bytes
Dec 23, 2017 14:51:18.127 [0x70000eb7f000] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/ef5c5f324bcbff93c8b5701404ccff483853a3a6/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=99cd8180-03fd-4d2e-9b02-e2cfff35ee47
Dec 23, 2017 14:51:18.128 [0x70000f09d000] DEBUG - MyPlex: Sending Server Info to myPlex (user=mrhyde@me.com, ip=, port=13304)
Dec 23, 2017 14:51:18.133 [0x70000e249000] DEBUG - Completed: [127.0.0.1:49382] 200 PUT /myplex/refreshReachability (11 live) GZIP 5947ms 268 bytes (pipelined: 4)
Dec 23, 2017 14:51:18.141 [0x70000f09d000] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=77ea06db-58f1-410e-86d0-4ec1af9bdfa0
Dec 23, 2017 14:51:18.144 [0x70000e249000] DEBUG - Auth: authenticated user 1 as MrHyde
Dec 23, 2017 14:51:18.144 [0x70000eafc000] DEBUG - Request: [192.168.0.23:58952 (Subnet)] GET /:/websockets/notifications (11 live) GZIP Signed-in Token (MrHyde)
Dec 23, 2017 14:51:18.145 [0x70000eafc000] DEBUG - WebSocket: Performing handshake from origin 
Dec 23, 2017 14:51:18.145 [0x70000eafc000] DEBUG - Beginning read from WebSocket
Dec 23, 2017 14:51:18.304 [0x70000f09d000] DEBUG - HTTP 201 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=77ea06db-58f1-410e-86d0-4ec1af9bdfa0
Dec 23, 2017 14:51:18.304 [0x70000f09d000] DEBUG - MyPlex: Published Mapping State response was 201
62

Well, this thread helped me. I disconnected my switch and ap from my Main switch and everything worked like a charm

63

I am having this issue with the Nvidia Shield Pro. I tried everything already to. I’m guessing I need to downgrade?

64

I am having this issue with the mac server :frowning:

65

@kvolke said:
I am having this issue with the mac server :frowning:

I had to delete my install of PMS and start afresh :frowning: I also rebooted all network devices. Its working fine now, I am convinced an update just corrupted my install.

66

@MrHyde said:

@kvolke said:
I am having this issue with the mac server :frowning:

I had to delete my install of PMS and start afresh :frowning: I also rebooted all network devices. Its working fine now, I am convinced an update just corrupted my install.

yes it works , have to delete all and install again :frowning: so sad