Windows Server - Can't connect locally over Wifi

Plex Media Server Desktops & Laptops
1

Server Version#: 1.13.8.5395

I have a strange issue with Plex at the moment. I’ve had no issues for really, and I know it was working last wednesday - 10th of October as I used it.

Setup is a a windows 10 PC, connected to a wired network. Remote access is working, and the ocal PC can connect to servername:32400, x.x.x.x:32400, 127.0.0.1:32400 and localhost:32400, I can also connect to all of the above via other computers on the wired network.

The issue then comes to light when I try and connect wirelessly (as I’ve said this was all working a week ago) via laptop plex app, laptop web browser, iPhone App, AmazonFire Plex App or LG TV. Web gives ERR_CONNECTION_RESET

The server does not respond, although I can ping it via host name, or by IP address, I can also RDP onto the computer via IP address or via host name.

I have a NAS that is also connected wirelessly with a web interface, abd the NAS is responding as expected.

I’ve turned off the firewall on the the plex computer, as well as on the main laptop that I am using to connect but this has not helped.

Anywhere else I could look at as to why plex?

2

Are all these devices on the same network, e.g. 192.168.1.x? Also, have you checked the PMS logs yet?

3

Yes, they are all on the same network.

I’m not sure what I logs I can look at for plex?

4

Post/check the server logs. Make sure debug logging is checked for the server in question under “General”. You can find out how to find the logs here: https://support.plex.tv/articles/200250417-plex-media-server-log-files/

5

Not sure if I want to post logs, lot of details in those.

I’ve used fiddler, so it looks like the client is connecting, but the server isn’t responding.

[Fiddler] ReadResponse() failed: The server did not return a complete response for this request. Server returned 0 bytes.

ClientConnected: 21:41:13.717
ClientBeginRequest: 21:41:13.728
GotRequestHeaders: 21:41:13.728
ClientDoneRequest: 21:41:13.728
Determine Gateway: 0ms
DNS Lookup: 0ms
TCP/IP Connect: 4ms
HTTPS Handshake: 0ms
ServerConnected: 21:41:13.732
FiddlerBeginRequest: 21:41:13.732
ServerGotRequest: 21:41:13.732
ServerBeginResponse: 00:00:00.000
GotResponseHeaders: 00:00:00.000
ServerDoneResponse: 21:41:32.641
ClientBeginResponse: 21:41:32.641
ClientDoneResponse: 21:41:32.641

6

If you don’t want to post the PMS logs, check them yourself. Make sure the server at least sees the client trying to connect. If so, the server might also log the reason it did not respond.

And just to be clear: You can connect via Ethernet but not via WiFi using the same client for testing (laptop for example)?

7

yes, that’s right - the laptop connects wired, but not when in wireless (even though it can ping the server by ip or name)

There doesn’t look to be anything in the server log that related to the laptop IP address at the time

Oct 17, 2018 21:41:13.978 [10684] VERBOSE - WebSocket: processed 1 frame(s)
Oct 17, 2018 21:41:15.354 [10684] VERBOSE - WebSocket: processed 1 frame(s)
Oct 17, 2018 21:41:16.205 [9344] VERBOSE - LongPoll: Sending data…
Oct 17, 2018 21:41:16.205 [10684] VERBOSE - LongPoll: got onDataRequested, closing connection
Oct 17, 2018 21:41:16.206 [10684] DEBUG - handleStreamRead code 2: End of file
Oct 17, 2018 21:41:16.206 [10684] VERBOSE - [IDLE] Removing (1->0) work item http_download - /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1&X-Plex-Product=Plex%20Web&X-Plex-Version=3.67.1&X-Plex-Client-Identifier=jycf47t4lqaozrzm0jyhz1tt&X-Plex-Platform=Chrome&X-Plex-Platform-Version=69.0&X-Plex-Sync-Version=2&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=1332x640%2C1366x768&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&X-Plex-Language=en
Oct 17, 2018 21:41:16.207 [10684] VERBOSE - [IDLE] Server is now idle
Oct 17, 2018 21:41:16.215 [10680] VERBOSE - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
Oct 17, 2018 21:41:16.215 [10680] DEBUG - Auth: authenticated user 1 as tubs74
Oct 17, 2018 21:41:16.215 [10680] VERBOSE - Auth: Came in with a super-token, authorization succeeded.
Oct 17, 2018 21:41:16.216 [8664] DEBUG - Request: [127.0.0.1:50267 (Loopback)] GET /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (6 live) GZIP Signed-in Token (tubs74)
Oct 17, 2018 21:41:16.217 [8664] VERBOSE - * Host => 127.0.0.1:32400
Oct 17, 2018 21:41:16.217 [8664] VERBOSE - * Connection => keep-alive
Oct 17, 2018 21:41:16.217 [8664] VERBOSE - * Accept => text/plain, /; q=0.01
Oct 17, 2018 21:41:16.217 [8664] VERBOSE - * Origin => http://juno:32400
Oct 17, 2018 21:41:16.217 [8664] VERBOSE - * Accept-Language => en
Oct 17, 2018 21:41:16.217 [8664] VERBOSE - * User-Agent => Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
Oct 17, 2018 21:41:16.217 [8664] VERBOSE - * Referer => http://juno:32400/web/index.html
Oct 17, 2018 21:41:16.218 [8664] VERBOSE - * Accept-Encoding => gzip, deflate, br
Oct 17, 2018 21:41:16.218 [8664] VERBOSE - * X-Plex-Client-Identifier => jycf47t4lqaozrzm0jyhz1tt
Oct 17, 2018 21:41:16.218 [8664] VERBOSE - * X-Plex-Device => Windows
Oct 17, 2018 21:41:16.218 [8664] VERBOSE - * X-Plex-Device-Name => Chrome
Oct 17, 2018 21:41:16.218 [8664] VERBOSE - * X-Plex-Device-Screen-Resolution => 1332x640,1366x768
Oct 17, 2018 21:41:16.218 [8664] VERBOSE - * X-Plex-Language => en
Oct 17, 2018 21:41:16.218 [8664] VERBOSE - * X-Plex-Platform => Chrome
Oct 17, 2018 21:41:16.218 [8664] VERBOSE - * X-Plex-Platform-Version => 69.0
Oct 17, 2018 21:41:16.219 [8664] VERBOSE - * X-Plex-Product => Plex Web
Oct 17, 2018 21:41:16.219 [8664] VERBOSE - * X-Plex-Sync-Version => 2
Oct 17, 2018 21:41:16.219 [8664] VERBOSE - * X-Plex-Token => xxxxxxxxxxxxxxxxxxxx
Oct 17, 2018 21:41:16.219 [8664] VERBOSE - * X-Plex-Version => 3.67.1
Oct 17, 2018 21:41:16.219 [8664] VERBOSE - * deviceClass => pc
Oct 17, 2018 21:41:16.219 [8664] VERBOSE - * protocolVersion => 1
Oct 17, 2018 21:41:16.219 [8664] VERBOSE - * protocolCapabilities => timeline,playback,navigation,mirror,playqueues
Oct 17, 2018 21:41:16.219 [8664] VERBOSE - * timeout => 1
Oct 17, 2018 21:41:16.219 [8664] VERBOSE - * X-Plex-Product => Plex Web
Oct 17, 2018 21:41:16.220 [8664] VERBOSE - * X-Plex-Version => 3.67.1
Oct 17, 2018 21:41:16.220 [8664] VERBOSE - * X-Plex-Client-Identifier => jycf47t4lqaozrzm0jyhz1tt
Oct 17, 2018 21:41:16.220 [8664] VERBOSE - * X-Plex-Platform => Chrome
Oct 17, 2018 21:41:16.220 [8664] VERBOSE - * X-Plex-Platform-Version => 69.0
Oct 17, 2018 21:41:16.220 [8664] VERBOSE - * X-Plex-Sync-Version => 2
Oct 17, 2018 21:41:16.220 [8664] VERBOSE - * X-Plex-Device => Windows
Oct 17, 2018 21:41:16.220 [8664] VERBOSE - * X-Plex-Device-Name => Chrome
Oct 17, 2018 21:41:16.220 [8664] VERBOSE - * X-Plex-Device-Screen-Resolution => 1332x640,1366x768
Oct 17, 2018 21:41:16.221 [8664] VERBOSE - * X-Plex-Token => xxxxxxxxxxxxxxxxxxxx
Oct 17, 2018 21:41:16.221 [8664] VERBOSE - * X-Plex-Language => en
Oct 17, 2018 21:41:16.221 [8664] VERBOSE - [IDLE] Adding (0->1) work item http_download - /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1&X-Plex-Product=Plex%20Web&X-Plex-Version=3.67.1&X-Plex-Client-Identifier=jycf47t4lqaozrzm0jyhz1tt&X-Plex-Platform=Chrome&X-Plex-Platform-Version=69.0&X-Plex-Sync-Version=2&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=1332x640%2C1366x768&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&X-Plex-Language=en
Oct 17, 2018 21:41:16.221 [8664] VERBOSE - [IDLE] Server is now active
Oct 17, 2018 21:41:16.222 [8664] VERBOSE - [IDLE] * http_download - /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1&X-Plex-Product=Plex%20Web&X-Plex-Version=3.67.1&X-Plex-Client-Identifier=jycf47t4lqaozrzm0jyhz1tt&X-Plex-Platform=Chrome&X-Plex-Platform-Version=69.0&X-Plex-Sync-Version=2&X-Plex-Device=Windows&X-Plex-Device-Name=Chrome&X-Plex-Device-Screen-Resolution=1332x640%2C1366x768&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&X-Plex-Language=en - 1 active item(s)
Oct 17, 2018 21:41:16.222 [8664] DEBUG - Beginning read from two-way stream.
Oct 17, 2018 21:41:23.978 [10680] VERBOSE - WebSocket: processed 1 frame(s)
Oct 17, 2018 21:41:25.354 [10680] VERBOSE - WebSocket: processed 1 frame(s)
Oct 17, 2018 21:41:33.249 [10680] VERBOSE - We didn’t receive any data from 86.139.114.9:54262 in time, dropping connection.
Oct 17, 2018 21:41:33.979 [10684] VERBOSE - WebSocket: processed 1 frame(s)
Oct 17, 2018 21:41:35.355 [10680] VERBOSE - WebSocket: processed 1 frame(s)
Oct 17, 2018 21:41:36.221 [9344] VERBOSE - LongPoll: Sending data…
Oct 17, 2018 21:41:36.221 [10680] VERBOSE - LongPoll: got onDataRequested, closing connection

8

Firstly, turn off verbose logging. That should only be used when working with someone to troubleshoot a specific issue. Otherwise, there is too much info and the key problems can get lost.

Second, if this only happens on WiFi, I would look at your network setup first. Please describe how your network is setup. Don’t forgot to include switches, repeaters, access point, any other network gear you have. One of these could be causing the issue.

Lastly, Please don’t post logs as plain text. This is hard to read and just clutters up the thread. If you need to, paste it into a file and attach the file.

9

Network Map - quite Simple
[BT Router & Wifi]–(Wired)–[Switch1]–(Wired)–[Switch2]

[BT Router & Wifi]
Wifi, DHCP, ADSL, DNS
Wired Connection to Switch 1

[Switch1] - Connections
Plex PC
NAS (Zyzel web Inetrface)
PC
Wired Connection to switch 2

[Switch2] - Connections
PC
Laptop1 (tested - working)

[Wifi] - Connections
Laptop1 - Not working with Plex, can ping Plex PC, and also RDP to it. Can also contact NAS Web interface.
iPhone - Not working with Plex (sever unavailable)
LG TV - Not working with Plex (server unavailable)

[Outside (not connected locally)]
iPhone - Can connect to Plex remotely

10

Sounds weird. Make sure the WiFi does not have any port filtering turned on.

11

What type of Wireless network did you set up? Make sure network isolation is not enabled or that you are using a guest network.

If that look fine, try connecting again from your iPhone, then get me the logs from both the iPhone and PMS.

12

I’ve been away so not able to look at this during the last week - so just some updates

Wifi - The router is a “provider” supplied Router/Modem/Wifi - there is very little control for this, it is as it is, and has been working fine, as has Plex up until this issue. The “network” is very simple and flat - no VLANs, some trunking between two swicthes and the NAS box. This again was all working, and indeed the wired section seems to be working as expected.

The Plex PC (which is a windows 10 dell laptop plugged into switch1), is contactable via RDP from the wireless network, and is also contactable on port 8080 via the wireless laptop (laptop1) I am writing this on, (I’ve tested this morning with a openhab webserver install that was on there but not running before today). The Plex web interface is not contactable from this laptop1.

The only thing I can see that happened at around the same time as this issue popping up was the install of the Oct windows update on my Plex PC - i can’t uninstall as another update has also applied in the mean time.

13

I’ve uploaded logs from

  1. The plex Server
  2. Logs from the windows store app (i don’t have access to iphone at mo)

Diagnostics.zip (10.6 KB)
Plex Media Server Logs_2018-10-27_12-00-17.zip (2.2 MB)

14

I’ve also completed the normal device troubleshooting - updated drivers, BIOS - and just completed a repair install of PLEX to see if that has made any difference.

If, I was unable to access the PC with plex in any other way, I would have been pointing at the router having some sort of issue - but as I can access 8080, RDP, ping etc I’m not sure that would be the issue - the only other thing would be that BT have put some block between the wifi/wired network and port 32400.

15

Taking a guess that your Oct Update was 1809? If so, Microsoft pushed out some crap Intel drivers. Related? Maybe. I don’t have a fix for it if this is the problem.

Have you tried killing the power on your router, then rebooting it?

Try changing your port off 32400 just to see what happens.

You’ve uploaded your logs. I don’t debug logs, but maybe someone else can.

16

To rule out your router, see if you can borrow a different router, config it for your network and see if it works. If it works, you’ve got a problem with your normal router.

17

interesting - see the investigation on this thread and the outcome

18

For info, the factory reset only worked for a while.
If I keep remote access on part way through a film; I loose connection again. A reboot of the router doesn’t help but a factory restore does.
Without remote access i have played a number of films without issue.
Not sure what has changed either with router or Plex but they won’t play nicely together anymore:(
For now I will stay on local only; might see if I can get hold of another router

19

It could be adapting its configuration

When I was with BT and using a BT Homehub 5, which has built-in DNS Rebinding Protection, i did notice a number of times that it was allowing some of these requests through initially but then starting to block them after a while - as if it is learning from what it is seeing and making adjustments to its rules

May be there is something similar here for wifi - or may be they are updating the settings and firmware

20

Okay, so yea it is the hub, and it is the remote access.

  1. Upnp on, automatic port on plex, remote access on, remote works, internal wifi access does not work.
  2. Upnp on, Remote access off - works on wifi
  3. A manual port and specified port rule on router, remote access on, remote fails, internal wifif access does not work.
  4. A manual port, specified port rule on router, remote access off (remote fails as expected) wifi does not work.
  • If firewall rule is UDP only, remote access does not work, but internal wifi does, if the rule is tcp/udp or tcp, remote access does not work and neither does internal wifi.

Oh, as aside, I have 3 x Upnp based wifi camera, and a security PVR that also uses UPnP and a web based interface - these are all working as expected, so it definitely seems to be Plex related as they should do the same thing, but are fully working as expected.