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

    How to allow ssl on other port than 443, http://x.x.x.x:8090 for example.

    Scheduled Pinned Locked Moved Firewalling
    7 Posts 3 Posters 5.1k 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.
    • A
      arobert
      last edited by

      how to allow ssl on other port than 443, http://x.x.x.x:8090 for example.
      Ms Isa ok, sme server squid ok, but pfsense ?

      1 Reply Last reply Reply Quote 0
      • P
        Perry
        last edited by

        System: General Setup

        webGUI protocol    HTTP      HTTPS
        webGUI port
        Enter a custom port number for the webGUI above if you want to override the default (80 for HTTP, 443 for HTTPS). Changes will take effect immediately after save.

        /Perry
        doc.pfsense.org

        1 Reply Last reply Reply Quote 0
        • A
          arobert
          last edited by

          http://x.x.x.x:8090 is not my pfsense but an owa exchange publish on the web. It's s outside of my network.  :(

          1 Reply Last reply Reply Quote 0
          • P
            Perry
            last edited by

            The default lan rule allows you to connect to any site using any port

            /Perry
            doc.pfsense.org

            1 Reply Last reply Reply Quote 0
            • A
              arobert
              last edited by

              Yes, but my default rule is disable because i'm allow only the most restrictive rule.
              I dont want any P2P in the network. (it's a school, wifi….)
              http, https , ftp is allow and nothing else.
              i'll want to allow https and https on other than standard port.
              Where is the squid.conf file in pfsense

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

                just add an allow rule with destination port: 8090 obove your block rule.

                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
                • A
                  arobert
                  last edited by

                  Thanks
                  I'm using a copy of defaut rule and i restrict only for my x.x.x.x ip

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