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

    Need help forward Plex and ownCloud hosted in a Freenas server

    NAT
    2
    6
    1.0k
    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.
    • J
      joseph_lin
      last edited by

      I have been working on this for "days" and I still cannot get it to work :( I need sets of fresh eyes to help me trouble shoot the problems. Here's my settings.

      Appreciate your help.

      Capture.JPG
      Capture.JPG_thumb
      Capture2.JPG
      Capture2.JPG_thumb
      Capture3.JPG
      Capture3.JPG_thumb

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Doesn't look like you let pfSense create your firewall rules from your NAT rules. The port forward for 443 is TCP/UDP while the firewall rule is TCP-only. That should be fine for HTTPS unless owncloud needs UDP/443 for some reason.

        Same for 32400 on Plex. No idea if Plex needs TCP/UDP or just TCP.

        You sure about the freenas jail IP addresses of 192.168.0.3 and 192.168.0.4?

        https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • J
          joseph_lin
          last edited by

          On my old router I used TCP for HTTPS. The TCP/UDP is just the left over of my trial and error. I never experience any difficulties in other routers. pfSense is the one that gives me trouble. Yes, the jail IP for Plex is 192.168.0.4 and ownCloud is 192.168.0.3.

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • J
              joseph_lin
              last edited by

              Read it and tried for three days. Not helping…
              Any other suggestions?

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                That list covers just about everything it could be.

                You'll probably have to start looking at packet captures to see where you went wrong.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

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