Media Server Ports

Plex Media Server
, ,
1

I am trying to find out what other ports are used by Plex.
Because for me WebOS player app does not work (cannot find server on my LAN), even with the server IP loaded into prefer IP setting, and insecure over lan set.

Previously it worked until I started using a VPN on my server and Whitelisted all of the below ports advised in the linked article below.
the White-listings should have opened up the App to access the Server. But it cannot find the server when the VPN is on, this really only means 1 thing.
there are extra ports not advised in this article.

The whole LAN /24 subnet is whitelisted too. but that has not helped

This is the current Article:

It states these ports are used:
"
The most important port to make sure your firewall allows is the main TCP port the Plex Media Server uses for communication:

  • TCP: 32400 (access to the Plex Media Server) [required]
    The following additional ports are also used within the local network for different services:
  • UDP: 1900 (access to the Plex DLNA Server)
  • UDP: 5353 (older Bonjour/Avahi network discovery)
  • TCP: 8324 (controlling Plex for Roku via Plex Companion)
  • UDP: 32410, 32412, 32413, 32414 (current GDM network discovery)
  • TCP: 32469 (access to the Plex DLNA Server)
    "

So I have done a “tcpdump” of that interface of the server filtered by the client IP. and it has some extra portsd it is coming in on, and going out on.
UDP 54622

are there any more?

I see the server communicating out on other ports like 42618, 42678, 42888, …, … not sure if I have to whitelist these, or how many there are?

2

A VPN moves your server to a different network (at the exit).

Unless you’ve configured the VPN to allow (not remap) the local subnet, the adapter is ‘captured’ and all traffic exiting it are routed out the VPN.

Consequently, LAN traffic is often excluded.

Broadcast messages (like Plex’s discovery) cannot cross subnet boundaries and additionally blocked by standard TCP/IP rules.

VPN’s and Plex are problematic at best. It requires a lot of custom route table rule writing.

3

I get all that, cheers.

But in this situation MacBook/IOS/Android/Windows devices and apps all have no problem gaining access to the server on the same subnet as the server and the LG TV, the server with its whitelisted LAN subnet /24 mean all of 192.168.1.0/24, and the respective ports as advertised in the above article are whitelisted and do not go via the VPN.
yet the WEBOS app does have an issue. suggests something is very different with the networking of the WEBOS App.

hence my question about additional ports, because I am seeing traffic from and to various ports.
meaning not all ports are disclosed in the above article,

what I can see is attempts are made from a specific port on the LG TV, to the defined port within the app 32400,
and so maybe I need whitelist a range of ports for the LG TV

4

The reason for the VPN is Deluge.
and hence to secure its traffic (and only Deluge)
I have tried to stand up deluge in a VM, and it was successful but it is now failing due to ubuntu updates.

5

So the principal here is Deluge in/out via VPN, and everything else outside the VPN.
this is technically difficult.

Is there any other high level solutions i should consider?

I could arrange 2 adapters, or put the VPN on the router might be best???
willing to try anything.

6

you mention whitelisting. If you’re all on the same subnet, no whitelisting should be needed.

I have an LG/WebOS (LG C1 series). To make it behave, I had to assign a static IP to the TV to put it on the subnet with the right netmask.

Once that was done, everything went fine. The Plex LG app can see the server without issue.

WebOS itself is kinda weird. I’m still learning it. As an engineer – I’m not impressed with the implementation … which is why I let my pfsense lock down its IP and subnet mask.

1 Like
7

Yes Static IP and netmask already done. something else weird is going on. preventing its access.

I am a little proficient with networking.
But WEBOS no idea. maybe I can turn on some developer tools and set an outgoing port range. :frowning:

8

By TCP/IP definition, outgoing ports are randomly assigned.
The stack assigns the next available as a socket connection is requested.
When the counter gets to the top (65535), it’s reset back to start counting again.

9

Thanks Again Chuck,

I think I am going to have to use something more professional like iptables or pfsense.
do you have any good articles on either that tie in with Plex.
This box is specifically a HTPC, sitting on prem.

I am now thinking it would be great to have a complete architecture/network diagram of all of this.
If I get this working I will draw one up.

10

I have pfSense as my gateway/edge device.
I attach my VPNs in pfsense.

My LAN is flat.

By default, every host on the LAN points to pfsense when the IP isn’t on this subnet.

It routes appropriately and automatically.
Problem solved. :slight_smile:

11

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