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

    Captive Portal Forbidden 403

    Scheduled Pinned Locked Moved Captive Portal
    2 Posts 2 Posters 951 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.
    • C
      chummertb
      last edited by

      Hello - currently running

      2.1.5-RELEASE (amd64)
      built on Mon Aug 25 07:44:45 EDT 2014
      FreeBSD 8.3-RELEASE-p16

      I'm running captive portal on the pfsense box in a primarily windows domain.  We use the box for snort capabilities and to track wireless access.  We have ran the box for years with very few issues until about 2 weeks ago when some users started reporting getting 403 forbidden errors when they attempted to connect to areas of the network governed by captive portal.  The issue is very strange in that 2 users literally feet away from each other with the same devices experience different results - one may get the forbidden page INSTEAD of the login page while the other's device works just fine.  There has been a wide range of devices with this issue both Android and Apple as well as location differences and network segments.  My past experience with captive portal problems has almost always been an all or nothing kind of deal, this is very intermittent.  One thing that is reproducible is when the user experiences the 403, clearing cache, device restarts, nothing seems to work.  I also don't get any sort of authentication log from the user that gets hit with the forbidden page.  The user does get a valid ip address from dhcp, it just seems they can never get to the login page for pfsense.

      Any help at all would be greatly appreciated!

      Regards,
      Chummer

      1 Reply Last reply Reply Quote 0
      • M
        muswellhillbilly
        last edited by

        I would start by comparing the DNS settings on the machines which work against those that don't. If they're using different DNS servers then that could possibly account for the conflicting behaviour. Check the routing, too.

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