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

    Slow redirect after successful authentication

    Scheduled Pinned Locked Moved Captive Portal
    4 Posts 3 Posters 780 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.
    • Z
      zak_coslat
      last edited by

      When user login for the first time the website take too much time to respond therefore redirection sometimes it take up to 30 sec to redirect.
      Database insertion is very quick
      I think that it take some time to add & allow the user ip & mac address in ipfw

      F 1 Reply Last reply Reply Quote 0
      • F
        free4 Rebel Alliance @zak_coslat
        last edited by

        @zak_coslat hello,

        are you using any of "high availability" settings ?
        (I'm asking because it could be related)

        Z 1 Reply Last reply Reply Quote 0
        • Z
          zak_coslat @free4
          last edited by

          Hi @free4 ,
          I'm using default Pfsense 2.4.4 without changing any settings
          this happen almost every first time the user login

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

            Hi,

            This :

            @zak_coslat said in Slow redirect after successful authentication:

            Database insertion is very quick

            is important.
            I'm quiet sure you can also check quickly ( read this so you know how to check ) that the device's MAC and IP are added to the two ipfw tables that are related to your captive portal instance.
            ipfw is the firewall the captive portal portal is using for it's magic.

            Which means : it's all open ...

            Btw : the GUI firewall rules for the interface that the captive portal is using are ok, right ?

            If you have the possibility to add a cert - one that is signed by a know and recognized cert authority like Letsencrypt - to your captive portal's login page you will see things speed up quiet a lot. You can use the acme package to handle all the details.
            The bad news is : you will be needing a domain name like "my-site-network.tld" and have to create a cert like "portal-my-site-network.tld" and use this cert on the captive portal's setup so the portal login page will get loaded using https.
            ( and will you're at it, ask the entire "wild card" cert for "*.my-site-network.tld" so you can also use it for your pfsense.my-site-network.tld and nas.my-site-network.tld and printer.my-site-network.tld etc etc on your local network (for all your https capable devices )

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

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