Repeating messages in Plex Media Server.log

Plex Media Server Desktops & Laptops
1

Server Version#: 1.13.9.5456

I’m seeing the following lines repeating in the Server Log:

Feb 03, 2019 16:00:29.135 [0x7f240cbf9700] DEBUG - NetworkServiceBrowser: found 0 SSDP devices via http://192.168.0.254:49152/wps_device.xml
Feb 03, 2019 16:00:29.135 [0x7f240cbf9700] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.0.254:49152/wps_device.xml
Feb 03, 2019 16:00:29.135 [0x7f240cbf9700] DEBUG - HTTP requesting GET http://192.168.0.254:49152/wps_device.xml
Feb 03, 2019 16:00:32.145 [0x7f240cbf9700] ERROR - Error issuing curl_easy_perform(handle): 7
Feb 03, 2019 16:00:32.145 [0x7f240cbf9700] WARN - HTTP error requesting GET http://192.168.0.254:49152/wps_device.xml (0, No error) (Failed connect to 192.168.0.254:49152; No route to host)

There’s no device at 192.168.0.254. In fact, my server is running on the 192.168.1.0 network.

Any ideas what may be causing this?

Thanks.

Tom

2

What is your machine’s and device’s netmask as SSDP does not cross subnet boundaries

3

The mask is 255.255.255.0. All my devices are in my subnet. I have no devices with the 192.168.0.254 IP address.

4

something must be on the 192.168.0.x subnet. I don’t know how but by definition it must be. Chromecast? something with WiFi which is hard wired?

5

There is another router (my cable modem) at 192.168.0.1. It’s connected to my WIFI router. My network looks like this:

image

My Plex server lives in the 192.168.1.0 network. Both routers are configured to do port forwarding. There are no other devices connected to my cable modem besides my WIFI router.

6

Ah, so there is device. Thank you. The diagram also helps.

May I suggest a technique which I also needed to do for my home?

Make the LAN “flat” (single subnet)

Switch the WiFi “router” into “bridge” mode. This makes it an Access Point (AP) . It will exist at 192.168.0.2. All your wifi devices will be assigned IP addresses on the 192.168.0.x subnet.

Double NAT will be immediately eliminated for all WiFi devices.
PMS, which is currently on the 192.168.1.x subnet will be Remote Access available should you so desire it. It will properly find and identify your cable modem as the IGD

7

Thanks for the input. It’s not clear to me why I need to change my network to eliminate these (every 3 secs) messages. PMS appears to be functioning just fine otherwise.

8

Do you use remote access from PMS which is on the 192.168.1.x subnet?
Do you have any wired (192.168.0.x) devices which want to use PMS on the Wireless 192.168.0.x subnet?

9

Do you use remote access from PMS which is on the 192.168.1.x subnet?

Yes. That works fine. “Fully accessible outside your network”

Do you have any wired (192.168.0.x) devices which want to use PMS on the Wireless 192.168.0.x subnet?

No.

10

If it all works for you in that configuration, meaning you’ve already created a path onto the *.0.x side, there’s nothing which can be done

11

If it all works for you in that configuration, meaning you’ve already created a path onto the *.0.x side, there’s nothing which can be done

Sounds like there’s nothing that can be done that’s certain to eliminate the messages in the log. Bummer.

1 Like
12

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