Remote access chooses a seemingly random port, only works with upnp enabled

Server Version#: 1.13.7.5369

I am getting some really strange behavior with remote access. I just upgraded my router to an Asus RT-AC86U. I set a static DHCP lease for my server. I set up port forwarding on 32400. I verified that the port is correctly forwarded in the asus system logs. I do not have double NAT. canyouseeme.org tests port 32400 as open, but the plex remote access test fails!

It only works if I enable uPnP on the router, which I do not want to do. When I enable uPnP the remote access test succeeds, but it uses public port 13194 and forwards to 32400 internal port. If I manually choose 32400 in server settings with uPnP enabled the remote access check fails.

I have no clue why it is randomly choosing public port 13194 with uPnP. Searches for “plex port 13194” turn up nothing.

I also have no clue why the remote access check fails when I clearly have the port open and forwarded (using canyouseemee.org).

Anybody else run into something like this? Any clues or pointers?

This is a known issue with the latest version. You have two options:

  1. Revert to the last public release of PMS v1.13.5.5332. Turn off Plex Pass Downloads to access the latest public version
  2. Leave UPnP enabled in your router because this is the regression in the latest PMS and manually configure your port forward as normal.

Thanks! I thought I was going crazy or there was some strange bug with the new Asus router.

I’m experiencing the same on ubuntu 18.04. would love to be notified of a fix at some point

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