For Windows users, here are some helpful PowerShell commands to create the port openings. Note, they only create the port openings for Domain and Private network profiles. If you actually do want to open the ports for direct internet access, you can add ‘Public’ to the list in each command where ‘Domain’ and ‘Private’ are listed.
At an Administrative PowerShell prompt, paste in the following (tested on PS 5.x)
New-NetFirewallRule -DisplayName ‘Plex Media Server Inbound TCP’ -Profile @(‘Domain’, ‘Private’) -Direction Inbound -Action Allow -Protocol TCP -LocalPort @(‘3005’, ‘8324’, ‘32400’, ‘32469’) -Description ‘TCP Ports for Plex Media Server.’
New-NetFirewallRule -DisplayName ‘Plex Media Server Outbound TCP’ -Profile @(‘Domain’, ‘Private’) -Direction Outbound -Action Allow -Protocol TCP -LocalPort @(‘3005’, ‘8324’, ‘32400’, ‘32469’) -Description ‘TCP Ports for Plex Media Server.’
New-NetFirewallRule -DisplayName ‘PlexMedia Server Inbound UDP’ -Profile @(‘Domain’, ‘Private’) -Direction Inbound -Action Allow -Protocol UDP -LocalPort @(‘1900’,‘5353’,‘32410’,‘32412’,‘32413’,‘32414’) -Description ‘UDP Ports for Plex Media Server.’
New-NetFirewallRule -DisplayName ‘PlexMedia Server Outbound UDP’ -Profile @(‘Domain’, ‘Private’) -Direction Outbound -Action Allow -Protocol UDP -LocalPort @(‘1900’,‘5353’,‘32410’,‘32412’,‘32413’,‘32414’) -Description ‘UDP Ports for Plex Media Server.’
The article:
https://support.plex.tv/articles/201543147-what-network-ports-do-i-need-to-allow-through-my-firewall/
is not clear which ports require inbound, outbound, or both. The above commands will create inbound and outbound for both TCP and UDP traffic. It would be nice if Plex indicated in more detail how much is needed to only give as much as necessary