Server Version#: 1.27.0.5897-3940636f2
Player Version#: web
What can I say except when the Plex server is running its ruining my internet either i get disconnected while playing games or watching youtube just everything and as soon as i stop the server again all of the nonsense is gone
On what distro are you running your server (platform, version)? Does this behavior impact your entire home network or only the device which is hosting your Plex Media Server?
I cannot remember other reports like this (like ever).
So I’m not sure if this is caused by Plex or is due to some weird configuration on your system…
its the latest debian 11 and is impacting on the whole local network and i think my friends also get kicked from other servers im hosting so its pretty severe
This sounds fishy.
A single app shouldn’t be able to impact the entire internet access of your home network (unless it’s installed on the gateway). My money is still on some weird configuration on your server (e.g. forcing the network connection to switch when Plex is active to run all traffic over a VPN…). I’ve never seen Plex act like this on its own.
its just a plain debian server running a teamspeak server and a minecraft server no kind of vpn or complex stuff (of which im not even able to) so there shouldnt be something to interfear
DEBUG log files will be needed to investigate further.
There is no way the .service file can cause any problem unless it was modified.
If PMS is overloading the server, the logs will show this.
where exactly can i find these logs so if it happends again (i will let it run from now on again) i can post them here
Plex Media Server Logs_2022-07-02_02-22-00.zip (964.8 KB)
i just got kicked from my teamspeak server i hope there is something you can find
Thank you for the logs.
You are definitely having connectivity problems.
I’ve dedacted your all public IP addresses
Jun 09, 2022 12:58:46.004 [0x7fcc3b5eeb38] DEBUG - HTTP requesting GET http://192.168.2.167:9080
Jun 09, 2022 12:58:46.013 [0x7fcc3bcd3b38] DEBUG - [HttpClient] HTTP/1.1 (0.0s) 200 response from GET http://192.168.2.167:9080
Jun 09, 2022 12:58:46.013 [0x7fcc3b5eeb38] ERROR - XML: Entity: line 1:\00
Jun 09, 2022 12:58:46.013 [0x7fcc3b5eeb38] ERROR - XML: parser\00
Jun 09, 2022 12:58:46.013 [0x7fcc3b5eeb38] ERROR - XML: error :\00
Jun 09, 2022 12:58:46.013 [0x7fcc3b5eeb38] ERROR - XML: Start tag expected, '<' not found\00
Jun 09, 2022 12:58:46.013 [0x7fcc3b5eeb38] ERROR - XML: status=ok\00
Jun 09, 2022 12:58:46.013 [0x7fcc3b5eeb38] ERROR - XML: ^\00
Jun 09, 2022 12:58:46.013 [0x7fcc3b5eeb38] ERROR - Error parsing content.
Jun 09, 2022 12:58:46.014 [0x7fcc3b5eeb38] ERROR - Error parsing XML: Error parsing file.
Jun 09, 2022 12:58:46.014 [0x7fcc3b5eeb38] ERROR - SSDP: Error parsing device schema for http://192.168.2.167:9080
Jun 09, 2022 12:58:55.994 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] Resolving 194.233.164.25 port 443
Jun 09, 2022 12:58:55.994 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] Resolved 194.233.164.25 to 194.233.164.25:443
Jun 09, 2022 12:58:56.035 [0x7fcc3bf43b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] Connected in 41 ms.
Jun 09, 2022 12:58:56.035 [0x7fcc3bf43b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] Wrote data, reading reply.
Jun 09, 2022 12:58:56.147 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] Read HTTP reply header.
Jun 09, 2022 12:58:56.147 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] MyPlex: We appear to have regained Internet connectivity.
Jun 09, 2022 12:58:56.163 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] PublicAddressManager: Obtaining public address and mapping port.
Jun 09, 2022 12:58:56.163 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] MyPlex: async reachability check - current mapped state: 'Mapped - Not Published'.
Jun 09, 2022 12:58:56.163 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] MyPlex: Requesting reachability check.
Jun 09, 2022 12:58:56.163 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] PublicAddressManager: Obtaining public IP.
Jun 09, 2022 12:58:56.163 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] HTTP requesting GET http://plex.tv/pms/:/ip
Jun 09, 2022 12:58:56.163 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] HTTP requesting PUT https://plex.tv/api/servers/af440f0728488a7aee4691fe91993e77bfd2479b/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=79c40aed-821a-4975-ad76-fcbe502d92ac
Jun 09, 2022 12:58:56.325 [0x7fcc3bcd3b38] DEBUG - [HttpClient] HTTP/2.0 (0.2s) 200 response from PUT https://plex.tv/api/servers/af440f0728488a7aee4691fe91993e77bfd2479b/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=79c40aed-821a-4975-ad76-fcbe502d92ac
Jun 09, 2022 12:58:56.326 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] Successfully connected to 194.233.164.25.
Jun 09, 2022 12:58:56.388 [0x7fcc3bcd3b38] DEBUG - [HttpClient] HTTP/2.0 (0.2s) 200 response from GET http://plex.tv/pms/:/ip
Jun 09, 2022 12:58:56.388 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] PublicAddressManager: Got public IP from http://plex.tv: XXX.XXX.XXX.XXX
Jun 09, 2022 12:58:56.418 [0x7fcc3b562b38] DEBUG - Request: [54.170.120.91:26530 (WAN)] GET /identity (2 live) TLS Signed-in
Jun 09, 2022 12:58:56.418 [0x7fcc3bf43b38] DEBUG - Completed: [54.170.120.91:26530] 200 GET /identity (2 live) TLS 0ms 398 bytes (pipelined: 1)
Jun 09, 2022 12:58:56.544 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] EventSource: Got event [data] '<Message address="XXX.XXX.XXX.XXX" port="32400" asyncIdentifier="79c40aed-821a-4975-ad76-fcbe502d92ac" connectivity="1" command="notifyConnectivity"/>'
Jun 09, 2022 12:58:56.544 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] PubSub: Got notified of reachability for async identifier 79c40aed-821a-4975-ad76-fcbe502d92ac: 1 for 91.19.104.115:32400 (responded in 218 ms)
Jun 09, 2022 12:58:56.544 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] MyPlex: reachability check - current mapping state: 'Mapped - Not Published'.
Jun 09, 2022 12:58:56.544 [0x7fcc3bf66b38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] MyPlex: mapping state set to 'Mapped'.
Jun 09, 2022 12:59:09.007 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] NAT: UPnP, not an IGD: <http://192.168.2.167:9080>.
Jun 09, 2022 12:59:09.019 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] NAT: UPnP, found device <http://192.168.2.1:43665/rootDesc.xml> with private address <192.168.2.164>
Jun 09, 2022 12:59:09.019 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] NAT: UPnP, not an IGD: <http://192.168.2.1:43665/rootDesc.xml>.
Jun 09, 2022 12:59:09.019 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] NAT: UPnP, getPublicIP didn't find usable IGD.
Jun 09, 2022 12:59:09.269 [0x7fcc3b3cbb38] WARN - [EventSourceClient/pubsub/XXX.XXX.XXX.XXX:443] NAT: PMP, got an error: Not Supported by gateway.
Jun 09, 2022 12:59:09.269 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/XXX.XXX.XXX.XXX:443] HTTP requesting GET https://91-19-104-115.75a31cd55d704206bad573cd8eb9a42b.plex.direct:32400/identity
Jun 09, 2022 12:59:09.304 [0x7fcc3b562b38] DEBUG - Request: [XXX.XXX.XXX.XXX:37262 (WAN)] GET /identity (2 live) TLS GZIP Signed-in
Jun 09, 2022 12:59:09.312 [0x7fcc3bcd3b38] DEBUG - [HttpClient] HTTP/1.1 (0.0s) 200 response from GET https://XXX-XXX-XXX-XXX.75a31cd55d704206bad573cd8eb9a42b.plex.direct:32400/identity
Jun 09, 2022 12:59:09.313 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] MyPlex: mapping state set to 'Mapped - Not Published'.
Jun 09, 2022 12:59:09.313 [0x7fcc3bf66b38] DEBUG - Completed: [91.19.104.115:37262] 200 GET /identity (2 live) TLS GZIP 9ms 479 bytes (pipelined: 1)
Jun 09, 2022 12:59:09.313 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] MyPlex: Updating device connections (from timer: 0)
Jun 09, 2022 12:59:09.313 [0x7fcc3b3cbb38] DEBUG - [EventSourceClient/pubsub/194.233.164.25:443] HTTP requesting PUT https://plex.tv/devices/af440f0728488a7aee4691fe91993e77bfd2479b?Connection[][uri]=http://192.168.2.164:32400&Connection[][uri]=http://[2003:f1:6704:df33:34c5:9759:f7fd:6c8d]:32400&Connection[][uri]=http://[2003:f1:6704:df33:ba97:5aff:fe61:1914]:32400&httpsEnabled=1&httpsRequired=0&dnsRebindingProtection=0&natLoopbackSupported=1&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Jun 09, 2022 12:59:09.373 [0x7fcc3bcd3b38] DEBUG - [HttpClient] HTTP/2.0 (0.1s) 200 response from PUT https://plex.tv/devices/af440f0728488a7aee4691fe91993e77bfd2479b?Connection[][uri]=http://192.168.2.164:32400&Connection[][uri]=http://[2003:f1:6704:df33:34c5:9759:f7fd:6c8d]:32400&Connection[][uri]=http://[2003:f1:6704:df33:ba97:5aff:fe61:1914]:32400&httpsEnabled=1&httpsRequired=0&dnsRebindingProtection=0&natLoopbackSupported=1&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (reused)
Jun 09, 2022 12:59:24.005 [0x7fcc3b5eeb38] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.2.167:9080
Jun 09, 2022 12:59:24.005 [0x7fcc3b5eeb38] DEBUG - HTTP requesting GET http://192.168.2.167:9080
Jun 09, 2022 12:59:24.013 [0x7fcc3bcd3b38] DEBUG - [HttpClient] HTTP/1.1 (0.0s) 200 response from GET http://192.168.2.167:9080
Jun 09, 2022 12:59:24.013 [0x7fcc3b5eeb38] ERROR - XML: Entity: line 1:\00
Device at 192.168.2.167 is constantly squawking bad XML in reply to SSDP inquiry.
It’s advertizing itself as a player but not responding as one.
Do you have any special networking configuration?
im not sure about what im saying now but if i would need to guess which device that is is propably a devolo powerline plug which kinda confuses me
what do you mean with special networking configuration?
Your power plugs have IP addresses? All those I’ve seen have been media converters.
(Ethernet → powerline adapter ------house wires ------- powerline adapter → ethernet)
Do you have any special LAN configuration ? (subnets, vlans, etc)
Is your server’s IP address set manually (static) or with DHCP ?
If it’s DHCP, and the interval is too short, this type of disruption can occur.
its a powerline adapter, no, its DHCP set to 3 weeks (which is the hiighes i can set it to)
How does your server connect to the modem/router?
Is that directly connected ?
with a telekom repeater
repeater?
Wireless?
wired to the repeater and then wireless to the router
is your server physically that distant from the internet router?
Something like this is what you use?
yes on the other side of the appartment actually
that exact thing i have here
