Remote access Stopped working

[darklight917]

I’ve only been using plex about a week, in the middle of a movie this morning it kicked me to an indirect link and disabled remote access.
I haven’t installed anything new lately and I have not changed any network settings. I restarted the app/desktop/router several times, it worked once for about a minute and now will only work for .5 seconds when I disable and enable the remote access again.

I’ve set up a static IP in both the router and my desktop to do the port forward to 32400, and I’ve confirmed that I set it up right, but for some reason canyouseeme says that “Error: I could not see your service insert IP address on port (32400)”

I’ve also hard reset my modem/router and reconfigured them, enabling UPnP even though I’m pretty sure it wasnt before. I went into my firewalls and made rules for both plex and the port even though they already had them and disabling the firewalls entirely didnt work either.

I’ve run out of ideas as to why or how this could have happened so any help would be appreciated.

[Atomsk]

I’m having the same problem. It looks like it’ll be enabled for like a second and then immediately switch back to Not available. What version of PMS are you using?

[darklight917]

Plex Media Server 1.13.5.5291

[systemshark]

Can you try signed out and in again. I’ve seen this error style of issue with a signin error.

[darklight917]

Yeah I’ve definitely done that sooo many times.

[MewMew]

Darklight, please refer to my thread, as I answered you there with troubleshooting tips. Plex not acessable from outside network

[anon18523487]

If it still doesn’t work, please restart PMS. Don’t do anything, just let it sit for about 3 minutes, then check the remote access page. Then get the entire log package and upload it here for me to review.

[m1e1w1]

I’ve been having this issue across PMS versions as far back as 0.9.12.x trough 1.13.5 on windows 7, windows 8, windows 10, ubintu 14.04, 15.x 16.04 and have tried static IP, manual port mapping, automatic port mapping, 3 completely different routers (linksys, Buffalo, and belkin). Restarts, fresh installs, NAT tests (which are not a problem) and through everything, i can still connect to the server remotely with multiple device types, multiple accounts but no matter what, the server shows that “plex is inaccessible outside your home network” … but it does work.

Years of this, and it’s not really fixed.

[darklight917]

Plex Media Server Logs_2018-08-07_21-25-01.zip (1.9 MB)

I probably disabled and re enabled the remote server a couple times routing different ports, otherwise those logs are as you specified.

[BermudaLamb]

I’ve been experiencing the same issue ever since upgrading to this same version (1.13.5.5291). Remote Access works for a little bit, and then poof, its gone again. I’ve restarted my PC several times, rebooted both my modem and router. I’ve even exited and restarted PMS numerous times, per the various replies above. I haven’t had any issues with Remote Access with the past releases, and this has only been happening since installing this release.

[tylerversion2]

I’m having the exact same issue. Remote access is extremely flaky. It works a little…and then it just bails out. This doesn’t matter much for some things, like PMP or my browser when I’m away from home…but it does severely affect things like PlexAmp or Sonos. It suddenly can’t see the server and breaks hard.

It’s only been an issue for the last few months. I tons of this in my log:

Aug 08, 2018 04:18:02.264 [0x7f2f177fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (b8892db1-3cd3-43ba-9106-5d80b1767f3c, expected f04fd894-6845-4536-9359-a410cfa87113)
Aug 08, 2018 04:18:02.316 [0x7f2f177fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (f04fd894-6845-4536-9359-a410cfa87113, expected 98804859-4e9e-415a-9e1e-78d7d0bd8355)
Aug 08, 2018 04:18:02.317 [0x7f2f177fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (f04fd894-6845-4536-9359-a410cfa87113, expected 98804859-4e9e-415a-9e1e-78d7d0bd8355)
Aug 08, 2018 04:18:06.073 [0x7f2f177fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (98804859-4e9e-415a-9e1e-78d7d0bd8355, expected f04fd894-6845-4536-9359-a410cfa87113)
Aug 08, 2018 04:18:06.073 [0x7f2f17fff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (98804859-4e9e-415a-9e1e-78d7d0bd8355, expected f04fd894-6845-4536-9359-a410cfa87113)
Aug 08, 2018 10:10:42.250 [0x7f2f177fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (, expected 98804859-4e9e-415a-9e1e-78d7d0bd8355)
Aug 08, 2018 10:10:42.250 [0x7f2f177fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (, expected f04fd894-6845-4536-9359-a410cfa87113)
Aug 08, 2018 10:10:42.251 [0x7f2f17fff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (, expected 98804859-4e9e-415a-9e1e-78d7d0bd8355)
Aug 08, 2018 10:10:42.251 [0x7f2f17fff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (, expected f04fd894-6845-4536-9359-a410cfa87113)

Specifically it shows up when I hit the “Retry” button on the Remote Access settings page. It feels like there’s wrong with Plex’s discovery servers - it’s not returning the expected token. Maybe somebody goofed up an SQL statement, SQL replication is too slow, somehow there’s stale data in there, or they need to run ntpdate and fix their servers’ times.

All I know is that in my logs, I see the received and expected identifiers all mixed up, reversed. It gets A, but expected B…and then in the next line it got B, but expected A.

[anon18523487]

@darklight917

I probably disabled and re enabled the remote server a couple times routing different ports, otherwise those logs are as you specified.

I see where it was first trying to use the automatic setting and failed. Then you switched to manual and it still failed. PMS reports a NAT issue, which means that the public IP it detected and sending back to Plex does not match the actual public address needed to access your server.

Try using a site like canyouseeme.org to check if your ip and port are correct and match what is shown in the PMS remote access page.

[darklight917]

canyouseeme.org doesnt seem to work no matter what port I try. But yes it does say the same public IP that plex does and also my ipconfig does.

However, when I type netstats -ab into CMD I dont see any ports from that IP at all.

[anon18523487]

Check your Windows firewall. Maybe it’s blocking the ports on your PC.

These are normally opened automatically by the install app, but they could have been blocked. See https://support.plex.tv/articles/201543147-what-network-ports-do-i-need-to-allow-through-my-firewall/ for the ports that need to be open.

[SunnyDays]

Hi,
I am not sure if you guys are aware, but this remote access major outage is now a well known issue that has been affecting the majority of PMS users and updates after the .5142 PMS server update. I can confirm that the backdated .5142 update has remote access working fine, but any update after this, including the current one does not work. Other threads where this prominent remote access issue has been attentioned includes, from my knowledge:-

Plex Constantly Loses Remote Access

This is very disappointing. I was hoping a Plex dev would post something, anything. So far they have been silent. This is a frustrating problem that apparently many of us are having. Rolling back versions is not a solution. It’s a temporary fix. However, from what I can tell from this post and reading other posts with the similar issue, it’s not a problem Plex takes seriously. I don’t have to have Plex to play my media. I don’t have to have Plex to play my media remotely. There are ot…

Random loss of remote - hundreds of pubsub async errors

@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.

Remote Access Drops with Version 1.13.2.5154

And now remote access is not working Jul 20, 2018 10:34:28.972 [0x7f5d64fff700] DEBUG - NAT: UPnP, found device http://192.168.1.253:49062/rootDesc.xml with private address <192.168.1.250> Jul 20, 2018 10:34:28.985 [0x7f5d64fff700] DEBUG - NAT: UPnP, usable device http://192.168.1.253:49062/rootDesc.xml with private address <192.168.1.250>. Jul 20, 2018 10:34:33.992 [0x7f5d64fff700] WARN - NAT: UPnP, error mapping port 25058, error: Unknown Error, controlURL: http://192.168.1.253:49062/ctl/IP…

PMS on Win 10 suddenly losing remote access

I am running pMS on Win 10 Pro; have been doing so for years. I have had remote access working for all that time (I manually specify a port of 32400, and my router [an Xfinity router Model:TG862G] is set to port forward correctly. Today, I’ve noticed that sometimes if I go to the “Server” settings on my PMS, it says that my server is no longer fully accessible from the outside. Haven’t changed the PMS config, nor changed the port forward rule on the router. (I had added a rule, to try and connec…

To name the threads that I am aware of so far. Its true that this issue is affecting a lot of PMS users now and should really be addressed sooner than later. Cheers.

[darklight917]

Yeah I’ve manually created rules for the ports, outbound and inbound, also tried completely disabling all of my firewalls for a few seconds and testing.

[anon18523487]

@darklight917

also tried completely disabling all of my firewalls for a few seconds and testing.

That won’t work. Windows goes into a weird mode when you disable the firewall so that is not a valid test. Can you show me a screenshot of your firewall rules for Plex?

@SunnyDays

I can confirm that the backdated .5142 update has remote access working fine, but any update after this, including the current one does not work.

I am running 5291 and remote access is working fine for me. Please provide more details and your PMS logs as I described previously.

[Vidzjunkie]

Same here, still no answer to why

[SunnyDays]

Hi to MovieFan.Plex,

I appreciate you trying to help, honestly I do. I have although tried my best to also figure this out in a few of the above forum links that I posted regarding this issue, and my PMS logs were already scrutinised by sa2000 in the below thread link,

Random loss of remote - hundreds of pubsub async errors

@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.

It although seems nothing much was in the end addressed or figured out, so I will then not be attaching any more logs this time, cheers.

Edit: Along with the above, I have now noticed another thread with a clear example of why I will not be updating PMS to the current version until issues are resolved:

Downgrade from 5291

Thanks for the detail Would like to concentrate initially on why http://127.0.0.1:32400/web is not working. Would like to match what you had on the screenshot to the logs. What time was the 2nd screenshot which shows a black screen could you get me the output from sudo lsof -iTCP:32400 sudo lsof -iTCP:32401 I am not sure if this just lists PIDs or process names as well. If not, you can use ps -ef to get list of PIDs Could I have that captured in terminal session on the mac from the faili…

[anon18523487]

Ah Peerblock. Anytime you run something that may block internet traffic, you risk blocking intended ones too. I don’t know how PeerBlock works but if you need to whitelist sites, that won’t work as Plex uses Amazon’s distributed system for our servers so the IPs could change and a whitelist won’t be able to keep up.

@SunnyDays

Edit: Along with the above, I have now noticed another thread with a clear example of why I will not be updating PMS to the current version until issues are resolved:

I don’t understand. What in that statement bothers you?