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

    CP portal page not showing on VLAN

    Scheduled Pinned Locked Moved Captive Portal
    5 Posts 3 Posters 949 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.
    • L
      lionafurbish
      last edited by

      Hello,
        I have a CP zone on two interfaces (same hw adapter), where one of them is a VLAN.
        Every interface has a DHCP server enabled; the DNS forwarder is also turned on.
        When a client connects to the VLAN, it gets an IP address from the right DHCP server.
        DNS is also working: a test with nslookup shows that the DNS server being used is the IP of the VLAN network and addresses are correctly resolved.
        When the client tries to browse, however, no captive portal page is loaded.
        However, if the client goes to http://ip_add:8000 (where the portal page is hosted) the page shows up and the users is correctly authenticated. Then the user can browse with no other problems.

      Any suggestion? Regards,

      1 Reply Last reply Reply Quote 0
      • K
        KrisseZ
        last edited by

        Hello.

        I just want to inform you that I'm in the same situation.

        We have a 2.1.5 version pfSense operating one-handed and the captive-portal
        won't direct users into the CP-login screen. With manual url insertion the portal
        is usable and functioning.

        Any suggestions?

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

          If the initial site attempted by the browser is HTTPS, redirection won't happen.

          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
          • K
            KrisseZ
            last edited by

            I have confirmed this behavior.

            Is there any known fix or workaround for this?

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

              No.  The CP is a man in the middle.  HTTPS is designed to prevent the same.

              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.