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

    Captive portal issues?

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    6 Posts 2 Posters 3.7k 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
      louis-m
      last edited by

      since my upgrade from 2.0 to 2.1, my captive portal has stopped with no errors getting logged. tried deleting, recreating etc but to no avail.
      anybody else had this?

      1 Reply Last reply Reply Quote 0
      • B
        bardelot
        last edited by

        Have you tried the most recent snapshot, it should be working again. You may have to open the CaptivePortal settings and "Save" to get it working after a reboot.

        1 Reply Last reply Reply Quote 0
        • L
          louis-m
          last edited by

          yep. tried that. all i get is:

          minicron: (/etc/rc.prunecaptiveportal) terminated by signal 15 (Terminated: 15)

          captiveportal is set on a vlan'd interface if that makes any difference.

          1 Reply Last reply Reply Quote 0
          • L
            louis-m
            last edited by

            On further testing, it's working with radius authentication (radius 2 package)
            The only issue is that services status shows it as not started when it clearly is:

            php[27472]: /pkg_edit.php: The command '/usr/local/etc/rc.d/radiusd.sh stop' returned exit code '1', the output was 'radiusd not running?'

            1 Reply Last reply Reply Quote 0
            • L
              louis-m
              last edited by

              Was playing with this a bit further and it appears that if you enter the portal name in UPPERCASE, pfsense reports it as not started in services even though it is.

              Once I changed the portal name to LOWERCASE everything appears OK. I created another portal to confirm this and the same happened.

              1 Reply Last reply Reply Quote 0
              • B
                bardelot
                last edited by

                @louis-m:

                Was playing with this a bit further and it appears that if you enter the portal name in UPPERCASE, pfsense reports it as not started in services even though it is.

                Once I changed the portal name to LOWERCASE everything appears OK. I created another portal to confirm this and the same happened.

                There's one more patch that has to be pulled afterwards that should be fixed.

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