I have been running Plex Media Server on Windows for a long time, and am about to migrate to Docker/Linux, so I’m trying to sort out which ports I need to open on my Linux server’s firewall for PMS (it’s behind my router, so not sitting on the open-Internet)?
Here’s what I see on the Linux server where I’m running a test PMS Docker container (with host mode networking):
$ sudo netstat -tulpn | grep Plex | grep -v 127\.0\.
tcp6 0 0 :::32400 :::* LISTEN 66211/Plex Media Se
udp 0 0 0.0.0.0:32410 0.0.0.0:* 66211/Plex Media Se
udp 0 0 0.0.0.0:32412 0.0.0.0:* 66211/Plex Media Se
udp 0 0 0.0.0.0:32413 0.0.0.0:* 66211/Plex Media Se
udp 0 0 0.0.0.0:32414 0.0.0.0:* 66211/Plex Media Se
udp 0 0 192.168.1.12:49225 0.0.0.0:* 66211/Plex Media Se
udp 0 0 192.168.1.12:58552 0.0.0.0:* 66211/Plex Media Se
udp 0 0 0.0.0.0:1901 0.0.0.0:* 66211/Plex Media Se
udp 0 0 192.168.1.12:51826 0.0.0.0:* 66211/Plex Media Se
The documentation I linked to includes UDP port 1900, but mine seems to be 1901, and I’m not sure what 49225, 51826, and 58552 are used for - anyone know?
I know that I can test blocking/allowing each port, and see what breaks, but I’m hoping someone that knows can share the info, and that the official post can be updated with the latest port list/descriptions.
EDIT: changed the word, “says” to, “includes” in: “The documentation I linked to includes…”
I run Plex in a docker on a machine behind my NAT router using host networking. The only port I have opened on my router and forwarded to the machine is TCP port 32400 for allowing remote access to Plex.
Thanks @frederick.grayson - my question is really about ports for local (LAN) access. (The firewall I’m talking about is on my Linux server, not my router.)
Thanks, @Orko - I know that 32400 is the port I have to have open from the Internet, if I want to open up access from outside my network, but expect there are some LAN clients that benefit from at least some of these other ports being open (looks like for service discovery and DLNA clients, and maybe something else?).
It shows the list of ports which need to be forwarded to the container. Consequently, these same ports would need to be opened in your host’s firewall (even if you’re using host networking for your container instead of bridged).
Why are you running a firewall on a machine that is on your local network? It is not needed since your behind your router which is your firewall also where it is needed.
@pshanew correct again - on my, “real” (Windows) PMS, it’s enabled, but not on my new test Docker PMS. I just enabled it and see port 1900 listening (and a bunch of other new ones). I’ll stick with the ports noted in the, “Bridge Networking” section of the link you posted - thanks again!
FYI, after enabling DLNA:
$ sudo netstat -tulpn | grep Plex | grep -v 127\.0\.
tcp 0 0 0.0.0.0:32469 0.0.0.0:* LISTEN 1202559/Plex DLNA S
tcp 0 0 0.0.0.0:1838 0.0.0.0:* LISTEN 1202559/Plex DLNA S
tcp6 0 0 :::32400 :::* LISTEN 66211/Plex Media Se
udp 0 0 0.0.0.0:7268 0.0.0.0:* 1202559/Plex DLNA S
udp 0 0 0.0.0.0:32410 0.0.0.0:* 66211/Plex Media Se
udp 0 0 0.0.0.0:32412 0.0.0.0:* 66211/Plex Media Se
udp 0 0 0.0.0.0:32413 0.0.0.0:* 66211/Plex Media Se
udp 0 0 0.0.0.0:32414 0.0.0.0:* 66211/Plex Media Se
udp 0 0 192.168.1.12:49225 0.0.0.0:* 66211/Plex Media Se
udp 0 0 192.168.1.12:58552 0.0.0.0:* 66211/Plex Media Se
udp 0 0 0.0.0.0:1900 0.0.0.0:* 1202559/Plex DLNA S
udp 0 0 0.0.0.0:1901 0.0.0.0:* 66211/Plex Media Se
udp 0 0 192.168.1.12:51826 0.0.0.0:* 66211/Plex Media Se
udp 0 0 0.0.0.0:46056 0.0.0.0:* 1202559/Plex DLNA S
udp 0 0 0.0.0.0:6290 0.0.0.0:* 1202559/Plex DLNA S
udp 0 0 0.0.0.0:47429 0.0.0.0:* 1202559/Plex DLNA S