RasPlex Players not appearing in players list due to firewall issue

Dev Community Apps & Creations
1

I’m running CentOS 7 and firewalld. I’ve opened the listed ports required from the article below:

https://support.plex.tv/hc/en-us/articles/201543147-What-network-ports-do-I-need-to-allow-through-my-firewall-

One area that isn’t working is the Plex Players option in the GUI doesn’t appear anymore. This means I can’t control my other Plex clients devices like RasPlex (Raspberry Pi). In addition, they are not showing up on other devices like iOS as well.

There is no firewall running on the Raspberry Pi (OpenELEC doesn’t enable one by default).

When I disable firewalld on CentOS the Players option appears so I’m pretty confident its the firewall on the server. I’m thinking it might be related to multicast.

What port/configuration am I missing in the firewall? I’ve checked multiple resources and I can’t find any other ports mentioned.

2

So I’m still not sure what exactly is being blocked by the firewall, but as I’ve been messing around with firewalld for way too long, I’ve decided just to do an allow all rule for the Rasplex devices:

firewall-cmd --zone=public --add-rich-rule='rule family="ipv4" source address="xx.xx.xx.xx" accept'

Replace - xx.xx.xx.xx with IP of Rasplex device
Zone - Change this if you use something other than public.

Yes its not best practice, but until I find more motivation to find out the real source (oh look a network pun!) of what exactly the firewall is blocking, this will do. I still suspect unicast/multicast.

3

@jamesmacwhite said:
So I’m still not sure what exactly is being blocked by the firewall, but as I’ve been messing around with firewalld for way too long, I’ve decided just to do an allow all rule for the Rasplex devices:

firewall-cmd --zone=public --add-rich-rule='rule family="ipv4" source address="xx.xx.xx.xx" accept'

Replace - xx.xx.xx.xx with IP of Rasplex device
Zone - Change this if you use something other than public.

Yes its not best practice, but until I find more motivation to find out the real source (oh look a network pun!) of what exactly the firewall is blocking, this will do. I still suspect unicast/multicast.

Your suspicions are correct.