@SunnyDays - Pubsub is not a list manager.
List managers are sites that give you lists of addresses to place in the block list.
It’s been a while, but I don’t remember Peerblock having any way to add exceptions by name.
Which is a major drawback in todays networking world, because a single server name (like pubsub.plex.tv) can have many addresses to distribute load and location speed.
@JamminR yes I understand,
I would like to mention though that if the Plex ‘Allowed IP lists were sent through to the iblocklist team @ https://www.iblocklist.com/, along with the Peerblock team themself, for them to add to their list updates/subscription lists, this issue could then indeed be addressed for everyone that does use Peerblock and the iblocklist lists, so some food for thought 
Also, if Peerblock cannot be used for the above quoted solution, how does one then ‘whitelist’ the Plex domains? Via the router settings?
Apologies, just a tad bit confused is all, thanks
You can’t whitelist the Plex domains, because with Amazon, they will keep changing. It’s not possible to whitelist all the potential IPs Amazon may use. Anything that requires a “whitelist” is just not going to work with Plex.
Not fully true - if a device or application requires IP ADDRESS whitelisting, then yes, too great a number of IP addresses exist that Amazon / Linode can switch at anytime and cause blocking.
As I mentioned in a previous post - if your block application allows whitelist by domain names, adding pubsub.plex.tv (pubsub.plex.bz) will be of great value, as no matter what ip address it’s using at any time of day, it can be reached.
I use Tomato firmware on my router. It downloads several dns blocklists weekly of hundreds of domain names it blocks. Though I’m not exactly sure which of about 6 lists block pubsub.plex.tv, I have a field I can enter exceptions in which I’ve had to allow pubsub.plex.tv for it to function.
EDIT - Additionally - if your block application allows exception by executable name, you could allow PlexMediaServer.exe and PlexScriptHost.exe have access to everything.
REPORT - Saturday 8/11, beginning at 6:34am, and ending at 9:23AM EST, I had 6 notifications.
As it was a Saturday and I was home/awake - I went ahead into the remote management settings of Plex and clicked “Retry” - it immediately re-established “remote access” available.
So, keeping this list going.
Date - Quantity - Start - End (Times are US EST)
6/4 - 6 - 0557 - 0634
6/6 - 6 - 0336 - 0633
6/8 - 6 - 0430 - 0633
6/14 - 10 - 0425 - 1145
6/28 - 21 - 2208 - 6/29 0805
7/16 - 22 - 0600 - 1447
7/17 - 24 - 0320 - 1446
7/19 - 20 - 0449 - 1446
Adjustment to 12 minute interval was on/about 7/20
7/28 - 28 - 0511 - 1935
Adjustment to 21 minute interval was on 7/29
8/11 - 6 - 0634 - 0923 ('forced' reconnect)More today.
Date - Quantity - Start - End (Times are US EST)
6/4 - 6 - 0557 - 0634
6/6 - 6 - 0336 - 0633
6/8 - 6 - 0430 - 0633
6/14 - 10 - 0425 - 1145
6/28 - 21 - 2208 - 6/29 0805
7/16 - 22 - 0600 - 1447
7/17 - 24 - 0320 - 1446
7/19 - 20 - 0449 - 1446
Adjustment to 12 minute interval was on/about 7/20
7/28 - 28 - 0511 - 1935
Adjustment to 21 minute interval was on 7/29
8/11 - 6 - 0634 - 0923 ('forced' reconnect)
8/15 - 38 - 0335 - 2247 ('forced' reconnect)
I’ve been thinking about this and I wonder if the Plex devs would be willing to try a temporary solution.
When I become aware that I’ve lost access, I go the web interface and click ‘Retry’. If that doesn’t work, I disable and re-enable remote access.
Why not build this into the Plex server as a fix until the underlying problem is resolved? It could be a user-selectable feature which would activate when the server loses remote access. It could attempt retry a couple of times (about a minute apart) and then escalate to a couple of attempts at the disable/reenable cycle. If it doesn’t work, then the server could stop trying.
I’m sure there are details I’m missing here, but it seems like it would be worth a shot.
The solution is they should just add an isup=true or something to the API so that Tautulli (and anybody else) can just call it separately. This would probably take like 15 minutes of their time and solve all of these problems.
No, that doesn’t solve it because that is already what Tautulli is doing (checking for mappingState="mapped").
The problem is mappingState="mapped" doesn’t change unless you refresh it, either by visiting the remote access settings page, or refresh it through the API (which is what Tautulli is doing).
You can read my post above where I demonstrate how it doesn’t refresh automatically.
An update: The latest Plex Media Server update, being Version 1.13.5.5332, has indeed fixed my remote access issues since updating it 3 days ago, which is a great news.
Firstly try updating the Plex Media Server via the Plex web app, and also restarting your PC and refreshing your router. If remote access still has on-going issues, you can try uninstalling PMS and then re-installing it, along with a PC restart and router refresh. A great job done by the Plex team!
The latest update appeared to make mine alot worse! I have downgraded to Version 1.13.3.5208 and it is rock solid now.
I am still experiencing this issue on my Ubuntu 16.04 LTS installation. It still seems to be connected even though it reports otherwise as I have not heard anyone complain. Anyone have a suggestion I can use to resolve this I am on the latest version 1.13.5.5332 which is what broke it. Any help would be greatly appreciated.
As indicated in my last post, I’ve not had an issue since 8/15.
After 8/15, I adjusted Tautulli to test remote connectivity every 13 minutes and 13 seconds, as shown here in line 409 of Tautulli init.py.
Is everyone else here using Tautulli? I’m not so sure everyone here experiencing problems is.
If you are using Tautulli, please make sure to adjust the line to increase it’s time.
Plex Media Server Beta Release 1.13.8.5388 addresses one of the timing issues that may affect Remote Access which appears to have come in with 1.13.3. There is still the original potential timing issue that may arise when refreshing Reachability
See Release Notice Plex Media Server
I also seem to be having this issue:
Nov 05, 2018 09:09:17.616 [0x7f8a9a7ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (b52005a6-ea8d-4466-8790-2e1e5c8df5fb, expected 57e3281d-a8f3-4187-9278-d154bddcd2b9)
Nov 05, 2018 09:09:31.037 [0x7f8a9a7ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (3b8ca712-c11e-402f-a242-b823bdd8746a, expected 1c073c8c-f6fb-4ead-b891-e2875fd280c3)
Nov 05, 2018 09:09:39.774 [0x7f8a99ffe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (7a8d0f06-5a33-4f06-afd4-6c0eb31a2c2a, expected bce07828-7a6c-417f-a373-1865426a4668)
Nov 05, 2018 09:09:40.935 [0x7f8a99ffe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (1c073c8c-f6fb-4ead-b891-e2875fd280c3, expected d7707410-1727-4e8e-b505-7901d77039f3)
Nov 05, 2018 09:09:42.050 [0x7f8a99ffe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (27529ec1-a6c1-4be0-ad81-3eaa7d95305c, expected d7707410-1727-4e8e-b505-7901d77039f3)
Nov 05, 2018 09:09:48.713 [0x7f8a99ffe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (bce07828-7a6c-417f-a373-1865426a4668, expected 3baf6fa8-b92c-4e45-9e23-83db98971243)
Nov 05, 2018 09:09:50.762 [0x7f8a9a7ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (d7707410-1727-4e8e-b505-7901d77039f3, expected 3baf6fa8-b92c-4e45-9e23-83db98971243)
Nov 05, 2018 09:10:38.714 [0x7f8a9a7ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (032a2ec7-c4af-4950-8513-9116b3d121b0, expected 48c8c284-fcec-459d-b55c-7cf8a96ea8e6)
Nov 05, 2018 09:10:38.874 [0x7f8a99ffe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (8170475d-4780-43ba-a4c7-3a82d91763a5, expected efabe1dc-20cd-4539-8dac-9306d370c5a8)
Nov 05, 2018 09:10:38.940 [0x7f8a99ffe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (48c8c284-fcec-459d-b55c-7cf8a96ea8e6, expected efabe1dc-20cd-4539-8dac-9306d370c5a8)
Plex 1.13.9.5456
Tautulli w/ activity_pinger.check_server_access set to 10 minutes
Attempted both uPnP and manual port
Connection goes up and down, clicking retry does not always resolve.
Please provide full logs with debug logging enabled covering time when remote access drops out. These warning messages in the log are most times harmless and the notifications get back in step later.
I have the same issue as the modem7 on 1.13.9.5456.
Remote access goes in and out, mostly out though.
PM/DM logs to you.
Does it actually go down - or it that the status on the settings page that shows it as down?
We do have a timing issue that could give rise to the status indicator being inaccurate. A browser screen refresh whilst viewing the settings page normally corrects the problem.
The logs do not show any issue. At 14:10 connectivity test was successful.
At 14:11 you disabled remote access and re-enabled it. Connectivity test was ok but due to the timing bug i mentioned, it did not show as successful. A browser refresh could have corrected it
At 14;14 you disabled remote access and re-enabled it. This time the timing issue corrected itself and remote access should have got marked as enabled at 14:14:41
When you noticed a problem - what device / app were you trying to connect to the server from ? and at what time?
If you end up with the same state again, could you get me extra diagnostics at the time
In a browser go to
https://plex.tv/api/resources?includeHttps=1&includeRelay=1&X-Plex-Token=YOURTOKENHERE
You would need to put the server token instead of YOURTOKENHERE
To find the token - see https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
Copy the response to a text file
Also this request
https://10-0-10-9.99e1584554b34f2489cd28100cbbe9de.plex.direct:32400/myplex/account?X-Plex-Token=YOURTOKENHERE
Again copy the response to text file and zip both files and send me by private message
And upload logs zip please and indication as to when remote access was lost and from where
It is always best to include whole zip of logs
See https://support.plex.tv/articles/200250417-plex-media-server-log-files/
The September server update seems to have fixed my particular issue. After the pms update, I set Tautulli back to defaults. I’ve not had issue since 8/15.
Good luck to the rest of you.
