Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Port forwarding for Plex

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    7 Posts 3 Posters 7.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C Offline
      ChacalCH
      last edited by

      Hello

      I know there is already a thread related to plex, but the suggestions didn't really help me and I'd like to get the Plex Service up and running again soon.

      First of all, everything worked fine with the Sonicwall I had installed before (so it has to be a firewall issue).

      I tried to forward the following Port: 32400

      With this NAT rule (see attachement)

      I'm using pfsense 2.2.1-RELEASE

      Greetz Daniel

      Unbenannt.PNG
      Unbenannt.PNG_thumb

      1 Reply Last reply Reply Quote 0
      • W Offline
        Wolf666
        last edited by

        What's your firewall log? Do you see blocks on port 32400?

        Modem Draytek Vigor 130
        pfSense 2.4 Supermicro A1SRi-2558 - 8GB ECC RAM - Intel S3500 SSD 80GB - M350 Case
        Switch Cisco SG350-10
        AP Netgear R7000 (Stock FW)
        HTPC Intel NUC5i3RYH
        NAS Synology DS1515+
        NAS Synology DS213+

        1 Reply Last reply Reply Quote 0
        • C Offline
          ChacalCH
          last edited by

          Unfortunately I didn't see anything in the logs that this particular port was blocked (the firewall rule is auto-added, so IMHO there shouldn't be any issues :/).

          1 Reply Last reply Reply Quote 0
          • M Offline
            morphmkd
            last edited by

            Does the the device running the plex service have the pfsense set as it's default gateway?

            1 Reply Last reply Reply Quote 0
            • C Offline
              ChacalCH
              last edited by

              Plex is running on a Windows 2012 r2 installation, the gateway is the pfsense firewall.

              1 Reply Last reply Reply Quote 0
              • M Offline
                morphmkd
                last edited by

                @ChacalCH:

                Plex is running on a Windows 2012 r2 installation, the gateway is the pfsense firewall.

                You can try to get a Packet capture on the interface closest to the plex server to see whether the packets are actually being forwarded to the server.
                Diagnostics / Packet Capture and select the interface that is closest to the plex server. Click start and then try to access the plex server through the pfsense. After you click stop you can see whether packets are actually being forwarded by the pfsense.

                1 Reply Last reply Reply Quote 0
                • C Offline
                  ChacalCH
                  last edited by

                  I got the solution.
                  I deleted the NAT again and created a new one without automatic rule linked to it. That's how I found the problem. The order of the auto-added firewall rule was wrong. It was added below the block-all rule, I just had to change the order, pretty simple if you think about it… Still I don't know why the rejecte packets weren't visible in the logfile.

                  Thank you all for your replies.

                  Greetz Daniel

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.