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

    [captive portal errors solved] errors after updating from 2.2.4 to 2.3

    Scheduled Pinned Locked Moved Captive Portal
    3 Posts 2 Posters 904 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.
    • G Offline
      glennmckenna
      last edited by

      hello,
      yesterday i updated to pfsense 2.3
      and now I've got multiple problems

      • the captive portal only works on mobile devices

      • when i connect to the wifi it will ask me to login on pfsense (so that's normal)

      • the mac filtering still works as it's meant to (allowing people to bypass the captive portal if there mac adresse is in the list)

      • the captive portal doesn't work on computers or laptops

      • when i connect to the wifi  and i haven't logged in it will not automatically redirect me to the captive portal

      • when i try to access the captive portal with the link (192.168.0.251:8002) all i get is a blank page

      may i also add that I've also got problems with squid
      https://forum.pfsense.org/index.php?topic=111190.msg619229#msg619229

      1 Reply Last reply Reply Quote 0
      • G Offline
        glennmckenna
        last edited by

        problem solved
        i was going to the wrong link
        192.168.0.251:8002
        instead of
        http://192.168.0.251:8002/index.php?zone=mdl

        1 Reply Last reply Reply Quote 0
        • GertjanG Offline
          Gertjan
          last edited by

          Something is still broken in your setup.
          After a 'dummy' http request like http://www.google.fr, the navigator will be directed to '162.168.0.251:8002', nothing less, nothing more.
          The captive portal will show up.

          Adding something like "?zone=mdl" isn't needed.

          Check this with your PC's:
          DHCP activated on PC ?
          Did it get an IP ? Gateway IP ? DNS IP (should be as the gateway IP = pfSense) ?

          Of course, an initial https:// request won't work, this is normal.

          Use the default captive portal 'html login page' to start with.

          No "help me" PM's please. Use the forum, the community will thank you.

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