PlexConnect to PMS through a firewall

Hi All,

I’m hoping someone in the forums has come across an odd issue I’ve hit with my PlexConnect server. As a bit of background, I currently have my PMS, PlexConnect and Apple TV devices on the same subnet. In this set up everything works perfectly fine. However, as part of my network enhancements I’m introducing segmentation which means the PMS and PlexConnect servers will no longer be on the same subnet. When I tried to implement this PlexConnect stopped working properly. I updated the ATV to use the new PlexConnect IP address for DNS lookups but as soon as I try to open Trailers it says unable to connect. When I review the logs for PlexConnect it has thrown a bunch of exceptions to do with sockets and an error 10054.

Between the PMS and PlexConnect there is a Palo Alto firewall (PA-200) but I have completely opened up access between the two IP addresses for testing. When reviewing the firewall logs there is nothing being blocked and I’m seeing the DNS and SSL connections going through. I thought this may be a limitation of PlexConnect that it has to reside on the same subnet as PMS so I tried placing the PlexConnect server on a different VLAN on the switch so it’s still on a different subnet but with no firewall in the middle. Now in this set up everything works just fine.

So my obvious question is what could be causing the exception errors in PlexConnect when traversing a firewall? Any help would be great!

Regards,

Craig

Did you enable ports 80 & 443 in the firewall ?

At the moment I’ve set the port to ANY on the rule.

Logs from the two situations please (separate VLAN, with and without firewall): PMS (debug log), and PlexConnect (normal log).

Having PMS and PlexConnect on separate subnet will make PMS think that PlexConnect is remote. To avoid this you have to use this PMS setting:

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