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

    HTTPS on pfsense and another box

    Scheduled Pinned Locked Moved NAT
    2 Posts 2 Posters 1.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.
    • N
      nore
      last edited by

      Greetings

      I have the following rule to enable access to pfsense using https:

      TCP * * WAN address 443 (HTTPS) *

      and it works fine.

      But, I have another box (a web server, https) in my LAN that i want to access from outside using HTTPS
      What do I have to port forward on pfsense in order to access that box ? should it be something like that:

      WAN TCP 443 (HTTPS) 192.168.1.200 443 (HTTPS)
                  (or any other port)  (ext.: 192.168.100.2)

      I believe this will cause a conflict.
      Another thing, "External port range" (in NAS)  is the destination port in the packet heading for pfsense, is that right?

      1 Reply Last reply Reply Quote 0
      • GruensFroeschliG
        GruensFroeschli
        last edited by

        You should move the webGUI to a different port if you want to have 443 for your webserver.

        Yes "External port ranges" is the destination port in the packet going to the pfSense from the outside.
        The pfSense then rewrites it to whatever you define and sends it to your server.

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

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