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 connect to a 2nd PMS server on my LAN, a Synology, but then deleted that rule, for other reasons having to do with Plex on the NAS binding order). Never touched the existing rule.

When Plex shows the red exclamation next to “Remote Access”, and says I am not fully accessible, if I click on “Apply” next to the manual port line, it says “Connecting”, and thenremote access is re-enabled. Then later, it will go offline again, without me touching anything.

Anyway, I will attach the logs from my PMS. If anyone can see what’s up, I would appreciate it.

Plex Media Server Logs_2018-07-08_18-48-56.zip (1.1 MB)

UPDATE: my server currently says not accessible.

Yet I am able to connect via the Internet from my Android phone, and my friend is able to play media from his house. So it appears as if I am accessible, despite what the screenshot shows.

Attached new logs.

Plex Media Server Logs_2018-07-08_19-31-52.zip (1.1 MB)

Just chiming in, having the same issue with my Mac PMS after the most recent update. We are using the same router on Comcast/Xfinity. Not sure if that is the commonality here. Other folks on a Plex User FB group are experiencing similar issues, not on Comcast, so I doubt the router is the issue. I’m going to check back for replies on your thread and mine, to see if we can both get our issues fixed.

Same Here. I’ve been running plex (with port forward) for I believe over 5 years. After discovering that Plex is wrong when it reports “not available”, I was told to just leave it alone and it’ll straighten itself out… (NOT).

I did receive many instructions on how to fix my suddenly failing port forwarding, however. :slight_smile:

I’m seeing it with 2 different Linux servers.

Well, I’m glad that it’s not Just Me, I suppose. LOL

nope, same problem here, Linux server with PMP1.13.2 … can’t get it “remote accessible” … even thou it has been working for 2years+ …

2weeks offline now … tried reinstalls, manual port forwards, … (Belgacom BBOX3)

I am seeing this same problem on a Linux (Ubuntu) server.

I will get calls from the in-Laws complaining they can’t connect “to Plex” and when I login to the webUI and check server status, I see that “server is not available outside your network”

I usually do the disable/enable remote access dance and it fixes whatever this problem is, but it eventually does come back.

Ubuntu 16.04.4
PMS 1.13.2.5154

It just happened to me again today. Had to disable/enable remote access 3 times before it would work. I also noticed that every time I enabled remote access, the external port was 0.

It wasn’t until it used a port other than 0 (duh), that it would work.

Would be nice if someone from Plex would comment on this. Its frustrating.

Seems like we’re talking to /dev/null here… Looks like Plex employees are ignoring this subject.

I finally caught this problem under debug. Seems like this is the problem:

Jul 11, 2018 20:05:44.777 [0x7fe99affe700] WARN - NAT: UPnP, error mapping port 26256, error: Unknown Error, controlURL: http://192.168.1.253:56867/ctl/IPConn.
Jul 11, 2018 20:05:44.777 [0x7fe99affe700] DEBUG - PublicAddressManager: Mapping failed.

192.168.1.253 is the address of my router

I think I might have solved this problem. Digging into my router, I found 100s of old UPNP rules in the port forwarding table for plex-media-server

I dont know if the router is supposed to clear them after sometime, or its part of the UPNP standard.

But after clearing them all out, ‘enabling remote access’ seems to work. we’ll see if it breaks again on its own.

It would appear that PMS is constantly having to change its port for remote access. Checking the server, I see that a new port is assigned for remote access and in my router, there were several entries for plex-media-server… but it seems to be “working” for now…

same here, all my family is gettings disconnect over wan,

  • Android TV device problems.
  • Transcoder error problems.
  • Remote acces problems.

1 Year ago we haven’t got this problems, software seems to have lots of bugs.

In my case, my PMS says that it is not reachable. Yet it is accessible, I have had multiple friends watch media even though my PMS says it is not accessible,

I even had to restart my PMS (for other reasons; Windows updates), and the same is happening after a reboot: PMS says it is online, then eventually says it is not accessible. But in reality, it is accessible the whole time.

This thread seems to be getting traction: Remote Access Drops with Version 1.13.2.5154

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