Plex server suddenly not available remotely

General Discussions
1

My server has been running fine for years, but today it’s suddenly showing as not available remotely. I’ve power cycled my router a few times, I’ve rebooted the plex server, I even broke down and installed the latest version of plex, which I usually wait for a few months before I do.

I also tried manually forwarding tcp 32400 to the plex server, nothing. It still will connect remotely, but it throws the indirect connection error before it does.
Details
Windows server 2012 R2 hyper-v guest
Running plex 1.14.0.5465

Anyone have any ideas?

2

I’m having the same problem, and haven’t had this problem before about a day ago.

As I attempt to re-enable, it seems to say Remote Access is available for a second, then switches back to not available.

I will follow the thread for updates.

3

Yeah, that’s the same behavior I am experiencing. I’ve moved my server to the DMZ in my network and that seems to work. So I’ll have to lock down the host firewall. Not sure why this would happen suddenly.

4

Just for kicks, I reverted to the previous version. at first it seemed to have no impact. but then I restarted the plex server at remote access started working again.
So, skip version 1.14.5465

5

Reverting to previous version also worked for me.

Of course, now I can’t assist in troubleshooting the problem.

But if Plex admins out there need additional information and want me to switch back again and run logs let me know.

Thanks

6

I had same issue with 1.13.8.5395. I rolled back to 1.13.5.5332 and that has been solid.

7

Hello: mortalic, This topic will help you address your issue a lot better, supply your Logs with a Wireshark Pcap and they’ll be able to help you fix your issue. (Rolling back is the only way at the moment it seems)

8

A problem has been identified in 1.14.0.5465 that resulted in failure to map port through uPnP on some routers. A fix is being tested by @beefsnack and @neiljohn and feedback so far is positive.

Server logs would show if it is this problem

9

Any idea when a patched update will be released?

10

There is no information available as to when there will be a 1.14.1 release

11

If your Issues are the same as mine then you will get what you need, it’s only been a few select people with the same issues, but As sa2000 says, can’t really tell if he cant see your logs. Have faith guys, he’ll get er done!

12

Have you identified the impacted router manufacturers?

13

I’ve rolled back to 1.13.9.5456 until this issue is resolved.

And FWIW, I have an Actiontec MI424WR.

https://www.actiontec.com/products/wifi-routers-gateways/fiber/bhr-rev-i/

If you need another tester please let me know and I’ll update to 1.14.9.5456 again and ship my logs to you.

14

@ankushnarula you get your hotfix yet, you back in business?

15

No - only have 3 sets of logs provided and only 2 routers mentioned

It appears to be routers that have not implemented the 2010 version of uPnP WIN IP Connection Version 2 documented here http://www.upnp.org/specs/gw/UPnP-gw-WANIPConnection-v2-Service.pdf

1 Like
16

any idea when this will be posted or a work around. I have a netgear night hawk x6 r8000 and I update the firmware and that did not help. stopped and starts upnp and that did not work either.

17

The upnp issue manifests itself with errors like this in the server log
WARN - NAT: UPnP, error mapping port 20392, error: Unknown Error, controlURL: http://192.168.1.1:49152/upnp/control/WANIPConn1.

I am hopeful that there will be a hotfix beta release to 1.14.0 sometime next week

18

Plex Media Server 1.14.0.5468 has just been released as Beta. It has two fixes for bugs that impacted Remote Access

See Release Notice

  • Automatic port mapping could fail with some older routers (#9335)
  • Fix for Server Unreachable and Remote Access issues (#9228)

Anyone running an early beta or a development build with early release of these fixes should now update to the official beta, Thank you for helping confirm the fixes

19

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