Well, the problem here seems to be with the new version of PMS, which can’t load at all the web interface. The SSL cert I’m using is from letsencrypt and gives no error.
Try it out: https://gigaworld.org:32400
Can you / do you mind replicating the pubsub issue with both current PMS version and the previous, without touching your configuration in any way?
If you would, it would give us exactly what’s needed to fix it.
- Recreate with version A, capture ZIP
- Recreate with version B, capture ZIP
- Attach both , identifying which is which please.
Thanks.
OMG,
I thought I was going crazy, this has been happening to me for the past week or so, I thought it was my firewalls…
This is running in a Docker container but as an experiment I also ran it up in a new Ubuntu 16.04 LTS in a new VM, same experience.
The server will come up for about 30 seconds, after about a 4 minute wait. and then as soon as this comes up, you’re dead in the water: “Aug 07, 2018 10:05:02.800 [0x14d5c5bff700] DEBUG - MyPlex: We appear to have regained Internet connectivity.”
Aug 07, 2018 10:02:38.777 [0x14d5c03ff700] WARN - PubSubManager: Connection to 45.79.11.43 failed: Connection timed out.
Aug 07, 2018 10:02:38.777 [0x14d5c03ff700] WARN - PubSubManager: Connection to 50.116.59.4 failed: Connection timed out.
Aug 07, 2018 10:02:38.777 [0x14d5c03ff700] WARN - PubSubManager: Connection to 172.104.129.32 failed: Connection timed out.
Aug 07, 2018 10:02:38.777 [0x14d5c03ff700] WARN - PubSubManager: Connection to 139.162.117.249 failed: Connection timed out.
Aug 07, 2018 10:02:38.777 [0x14d5c03ff700] WARN - PubSubManager: Connection to 139.162.245.220 failed: Connection timed out.
Aug 07, 2018 10:02:38.777 [0x14d5c03ff700] WARN - PubSubManager: Connection to 172.104.173.210 failed: Connection timed out.
Aug 07, 2018 10:02:38.777 [0x14d5c03ff700] WARN - PubSubManager: Connection to 184.105.148.108 failed: Connection timed out.
Aug 07, 2018 10:02:38.777 [0x14d5c03ff700] WARN - PubSubManager: Connection to 184.105.148.102 failed: Connection timed out.
Aug 07, 2018 10:02:41.980 [0x14d5bebfd700] ERROR - Error issuing curl_easy_perform(handle): 28
Aug 07, 2018 10:02:41.980 [0x14d5bebfd700] DEBUG - HTTP simulating 408 after curl timeout
Aug 07, 2018 10:04:25.191 [0x14d5c2bff700] DEBUG - BPQ: [Starting] -> [Processing]
Aug 07, 2018 10:04:25.192 [0x14d5c2bff700] DEBUG - BPQ: generating queue items from 0 generator(s)
Aug 07, 2018 10:04:25.192 [0x14d5c2bff700] DEBUG - BPQ: generated 0 item(s) for queue
Aug 07, 2018 10:04:25.193 [0x14d5c2bff700] DEBUG - PlayQueue: 0 generated IDs compressed down to a 2 byte blob.
Aug 07, 2018 10:04:25.193 [0x14d5c2bff700] DEBUG - PlayQueue: 0 generated IDs compressed down to a 2 byte blob.
Aug 07, 2018 10:04:25.211 [0x14d5c2bff700] DEBUG - BPQ: [Processing] -> [Idle]
Aug 07, 2018 10:04:46.913 [0x14d5c3bca700] DEBUG - NAT: UPnP, not an IGD: http://172.16.10.1:5000/ssdp/desc-DSM-eth4.xml.
Aug 07, 2018 10:04:46.913 [0x14d5c3bca700] DEBUG - NAT: UPnP, getPublicIP didn’t find usable IGD.
Aug 07, 2018 10:04:47.164 [0x14d5c3bca700] WARN - NAT: PMP, got an error: Not Supported by gateway.
Aug 07, 2018 10:04:47.164 [0x14d5b8fff700] DEBUG - PublicAddressManager: Obtaining public address and mapping port.
Aug 07, 2018 10:04:47.164 [0x14d5c59fe700] DEBUG - PublicAddressManager: Obtaining public address and mapping port.
Aug 07, 2018 10:04:47.164 [0x14d5c59fe700] DEBUG - MyPlex: We appear to have regained Internet connectivity.
Aug 07, 2018 10:04:47.164 [0x14d5c03ff700] DEBUG - PublicAddressManager: Obtaining public IP.
Aug 07, 2018 10:04:47.164 [0x14d5c5bff700] DEBUG - PublicAddressManager: Obtaining public address and mapping port.
Aug 07, 2018 10:04:47.164 [0x14d5c5bff700] DEBUG - MyPlex: We appear to have regained Internet connectivity.
Aug 07, 2018 10:04:47.164 [0x14d5c59fe700] DEBUG - EventSource: Successfully connected to 184.105.148.102.
Aug 07, 2018 10:04:47.164 [0x14d5c03ff700] DEBUG - HTTP requesting GET http://plex.tv/pms/:/ip
Aug 07, 2018 10:04:47.164 [0x14d5c5bff700] DEBUG - EventSource: Successfully connected to 184.105.148.102.
Aug 07, 2018 10:04:47.164 [0x14d5badfe700] DEBUG - MyPlex: Updating device connections (from timer: 0)
Aug 07, 2018 10:04:47.164 [0x14d5badfe700] DEBUG - HTTP requesting PUT https://plex.tv/devices/4779d07a40030ff812e655a5bb860f298c43ea0d?Connection[][uri]=http://172.16.0.245:32400&httpsEnabled=1&httpsRequired=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Aug 07, 2018 10:04:47.165 [0x14d5c59fe700] DEBUG - EventSource: Failure in IdleTimeout (0 - Success).
Aug 07, 2018 10:04:47.165 [0x14d5c59fe700] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Aug 07, 2018 10:04:47.165 [0x14d5c59fe700] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Aug 07, 2018 10:04:47.165 [0x14d5c5bff700] DEBUG - EventSource: Failure in IdleTimeout (0 - Success).
Aug 07, 2018 10:04:47.165 [0x14d5c5bff700] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Aug 07, 2018 10:04:47.165 [0x14d5c5bff700] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
Aug 07, 2018 10:04:47.165 [0x14d5c59fe700] ERROR - EventSource: Retrying in 15 seconds.
Aug 07, 2018 10:04:47.165 [0x14d5c5bff700] ERROR - EventSource: Retrying in 15 seconds.
Aug 07, 2018 10:04:47.165 [0x14d5b8fff700] DEBUG - HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Aug 07, 2018 10:04:47.165 [0x14d5c59fe700] DEBUG - Completed: [127.0.0.1:43174] 200 GET / (4 live) GZIP 139699ms 1210 bytes
Aug 07, 2018 10:04:47.165 [0x14d5c2bff700] DEBUG - Request: [127.0.0.1:43396 (Loopback)] GET /servers (3 live) GZIP Signed-in Token (bobertc)
Aug 07, 2018 10:04:47.166 [0x14d5c5bff700] DEBUG - Completed: [127.0.0.1:43396] 200 GET /servers (3 live) GZIP 0ms 539 bytes
Aug 07, 2018 10:04:47.166 [0x14d5b65f8700] DEBUG - MyPlex: Sending Server Info to myPlex (user=bobertc@gmail.com, ip=, port=32401)
Aug 07, 2018 10:04:47.167 [0x14d5b65f8700] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=c608ea3f-4dc7-4cba-ac29-2c4e8b7c5607
Aug 07, 2018 10:04:47.487 [0x14d5c03ff700] DEBUG - HTTP 200 response from GET http://plex.tv/pms/:/ip
Aug 07, 2018 10:04:47.487 [0x14d5c03ff700] DEBUG - PublicAddressManager: Got public IP from http://plex.tv: 207.6.205.58
Aug 07, 2018 10:04:47.833 [0x14d5badfe700] DEBUG - HTTP 200 response from PUT https://plex.tv/devices/4779d07a40030ff812e655a5bb860f298c43ea0d?Connection[][uri]=http://172.16.0.245:32400&httpsEnabled=1&httpsRequired=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Aug 07, 2018 10:04:47.835 [0x14d5badfe700] DEBUG - CERT: Certificate will not expire soon.
Aug 07, 2018 10:04:47.863 [0x14d5b8fff700] DEBUG - HTTP 200 response from GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Aug 07, 2018 10:04:47.864 [0x14d5b8fff700] DEBUG - Running database fix-ups.
Aug 07, 2018 10:04:47.866 [0x14d5b8fff700] DEBUG - Database Fixups: Destroyed 0 transient items.
Aug 07, 2018 10:04:47.870 [0x14d5b8fff700] DEBUG - Collections: Found 96 collections tags in section 1.
Aug 07, 2018 10:04:47.870 [0x14d5b8fff700] DEBUG - Collections: We had 96 collections in the library already.
Aug 07, 2018 10:04:47.871 [0x14d5b8fff700] DEBUG - Collections: Synced tags in section 1 in 3ms.
Aug 07, 2018 10:04:47.899 [0x14d5b65f8700] DEBUG - HTTP 201 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=c608ea3f-4dc7-4cba-ac29-2c4e8b7c5607
Aug 07, 2018 10:04:47.899 [0x14d5b65f8700] DEBUG - MyPlex: Published Mapping State response was 201
Aug 07, 2018 10:04:47.899 [0x14d5b65f8700] DEBUG - MyPlex: Got response for 4779d07a40030ff812e655a5bb860f298c43ea0d ~ registered 207.6.205.2:32401
Aug 07, 2018 10:04:47.923 [0x14d5b8fff700] DEBUG - Collections: Refreshed attributes for 96 collections in section 1 in 52ms.
Aug 07, 2018 10:04:47.928 [0x14d5b8fff700] DEBUG - Collection: Refreshed visibility in section 1 in 4ms.
Aug 07, 2018 10:04:47.929 [0x14d5b8fff700] DEBUG - Collections: Found 0 collections tags in section 2.
Aug 07, 2018 10:04:47.929 [0x14d5b8fff700] DEBUG - Collections: We had 0 collections in the library already.
Aug 07, 2018 10:04:47.929 [0x14d5b8fff700] DEBUG - Collections: Synced tags in section 2 in 0ms.
Aug 07, 2018 10:04:47.930 [0x14d5b8fff700] DEBUG - Collections: Refreshed attributes for 0 collections in section 2 in 0ms.
Aug 07, 2018 10:04:47.931 [0x14d5b8fff700] DEBUG - Collection: Refreshed visibility in section 2 in 1ms.
Aug 07, 2018 10:04:47.931 [0x14d5b8fff700] DEBUG - Running database fix-ups completed in 0.0 seconds.
Aug 07, 2018 10:04:47.931 [0x14d5b8fff700] DEBUG - HTTP requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Aug 07, 2018 10:04:48.576 [0x14d5b8fff700] DEBUG - HTTP 200 response from GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Aug 07, 2018 10:04:58.732 [0x14d5b9fff700] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 21.978100 seconds: 172.16.0.42
Aug 07, 2018 10:05:02.165 [0x14d5c59fe700] DEBUG - EventSource: Resolving 184.105.148.102 port 443s
Aug 07, 2018 10:05:02.165 [0x14d5c5bff700] DEBUG - EventSource: Resolving 184.105.148.102 port 443s
Aug 07, 2018 10:05:02.165 [0x14d5c59fe700] DEBUG - EventSource: Resolved 184.105.148.102 to 184.105.148.102
Aug 07, 2018 10:05:02.165 [0x14d5c5bff700] DEBUG - EventSource: Resolved 184.105.148.102 to 184.105.148.102
Aug 07, 2018 10:05:02.245 [0x14d5c5bff700] DEBUG - EventSource: Connected in 54 ms.
Aug 07, 2018 10:05:02.245 [0x14d5c59fe700] DEBUG - EventSource: Connected in 55 ms.
Aug 07, 2018 10:05:02.245 [0x14d5c59fe700] DEBUG - EventSource: Wrote data, reading reply.
Aug 07, 2018 10:05:02.245 [0x14d5c5bff700] DEBUG - EventSource: Wrote data, reading reply.
Aug 07, 2018 10:05:02.800 [0x14d5c5bff700] DEBUG - EventSource: Read HTTP reply header.
Aug 07, 2018 10:05:02.800 [0x14d5c5bff700] DEBUG - MyPlex: We appear to have regained Internet connectivity.
Aug 07, 2018 10:05:02.801 [0x14d5c59fe700] DEBUG - EventSource: Read HTTP reply header.
Aug 07, 2018 10:05:02.801 [0x14d5c59fe700] DEBUG - MyPlex: We appear to have regained Internet connectivity.
Aug 07, 2018 10:05:06.841 [0x14d5b9fff700] DEBUG - NetworkServiceBrowser: SSDP arrived: 172.16.0.42 (http://172.16.0.42:8088/description)
Aug 07, 2018 10:05:06.842 [0x14d5b65f8700] DEBUG - HTTP requesting GET http://172.16.0.42:8088/description
Aug 07, 2018 10:05:06.874 [0x14d5b65f8700] DEBUG - HTTP 200 response from GET http://172.16.0.42:8088/description
Does it happen to you too that sometimes Plex stops responding for 5/10 minutes while watching a video? No buffering, nothing, just stops and refreshing the web interface does nothing.
Oh absolutely. Under my system I’m doing a:
tail - f (Plex folder) Plex Media Server.log
The server will only be up for about 10 to 20 seconds. It will then timeout and do it all over again. The servers disappear and won’t come back until it repeats. Usually in 5 maybe 10 minutes?
I thought that this was a DNS rebind issue and spent 3 days trying different firewall configurations.
Only found this thread this morning.
Are you using a dedicated server? If so, which provider are you using? Sometimes it seems like if there is some filtering on Plex’s side. I tried watching 3 videos yesterday, 40 mins each. Every 10-15 minutes or so I had to wait for my PMS to revive by itself as it was totally unresponsive. My dedicated server processes were all good. CPU was totally fine, no hard work in background. I really don’t get it.
My main server is an unRAID box, it’s been running very well for 4 months, I fired up the previous box I had with unRAID on it (a much more power hungry system, Dual Xeon versus Single Xeon) it did exactly the same thing. These are both Docker/Linux variants.
I then built a system under my ESXi box under Ubuntu (Linux) as well. All of the systems did the exact same thing, which I why I figured it MUST be my network. But what could possibly have changed since last week… (when did the last Plexpass version update come out?..)
I spent a LOT of time over the past four days on this.
Thanks for the log snippet
what do you mean by this ?
What happens when you open browser directly on the server and go to http://127.0.0.1:32400/web ?
and could you also try with the local ip instead of 127.0.0.1
Are there multiple network interfaces ?
and could you attach zip of the logs folder (and PMS Plugin Logs subfolder) after you try that and screenshot and indicating time it was done
Hi sa2000,
I’ve been chatting with ChuckPA about this, but what happens is the server will come up for about 20 seconds and around the time that message comes up the server disppears. You cannot see it. It vanishes from all web devices. Keep in mind this is running in a docker environment. But I experienced the exact same problem with an Ubuntu 16.04LTS environment.
Note, this is in a docker environment that’s been working for 9 months. Last week it broke, presumably because of the new network detection feature.
I’ve now gone into the network setup and forced it to the actual NIC instead of the other 3 (like locahlost, etc.) the behaviour continues.
IMHO it’s failing to lock onto the correct network interface. If I leave the system up for about 3 hours it eventually figures it out. (the log files are too short for me to figure out exactly how long this takes but I walk away then it miraculously comes back.
You could increase the number of log files to 50 or 100 by editing the Preferences.xml
See LogNumFiles setting mentioned on this article
https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
could you tidy up the servers list within plex.tv
In Plex Web select Settings / Devices / Server and remove old duplicate obsolete servers
There are a number of servers showing same local IP 172.17.0.1 in plex.tv
May be not all within the same network - but best to remove obsolete servers as client apps would get a list of servers and their IP addresses from plex.tv and then try and use that information to connect to the servers
You can see what plex.tv holds as routes to your servers by looking at the resources.xml which you can obtain as outlined here
https://support.plex.tv/articles/206721658-using-plex-tv-resources-information-to-troubleshoot-app-connections/
If you have made use of the setting to select a specific network interface, then would need to always see the first log file after launch - so need to capture logs when the issue arises and they need to go back to the time when the server was launched
Make sure clients and server authenticate to plex.tv with the same account
When providing logs please also provide your docker configuration and network settings for docker and confirm that this ties in with the interface that you selected
It is probably better to do a test first without use of the network interface selection setting
Are you able to get also netstat -a -b -n to see what IP addresses listening to 32400
If you like to make the resources.xml available - please do not post but zip and send privately in private message
Hi @sa2000 I’ve been pruning the servers and excess devices all along… However, you are correct, this server is in devices twice today. Just deleted it.
However, considering how many times I’ve done re-installs with many different dockers, It would not surprise me if the data on your end was a bit wonky. I only see one device, but when I fire up my Android client, I see about 10. I can edit them, re-order them, but I cannot delete them.
Just checked the XML file and I see only the devices I would expect to see at this URL “https://plex.tv/api/resources?X-Plex-Token=”
I’ve tried bridge and host, even forced fixed external IP address.
The problem is the XML file from unRAID is certainly not the usual compose commands we’re all used to in docker under Linux.
When I was able to get the server up (for 30 seconds) I tried the new bind it to a specific address. Even tried forcing it in XML.
I’m still unsure if it’s a DNS/Rebind issue. But the timing is suspicious.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
