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

    404 Not Found

    Scheduled Pinned Locked Moved Captive Portal
    11 Posts 6 Posters 3.2k 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.
    • R
      redeyes
      last edited by

      Where was it redirecting to before ?

      Check whether if you've  PORTAL_ZONE in your Captive Portal login form.  Are you using custom Captive Portal login page or the default ?

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        @redeyes:

        Check whether if you've  PORTAL_ZONE in your Captive Portal login form.

        that's not strictly required in 2.3-REL as it was in pre-release versions, I brought back similar functionality to what lighttpd was doing with the redirect there.

        As to the problem, redeyes questions are good, need answers to that. What is the 404 specifically?

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

          Dear cmb

          Have you a solution for this problem ??

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

            Hope you know what's the problem and how to fix it ?

            @MohamedMagdi:

            Dear cmb

            Have you a solution for this problem ??

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              There isn't enough information here to have any idea what you're seeing. No, there aren't any known problems in captive portal that result in 404s.

              1 Reply Last reply Reply Quote 0
              • J
                jassrahal
                last edited by

                I am getting the same error, I think it only happens if you have made changes to the default page of captive portal because after setting it to default everything starts working.

                1 Reply Last reply Reply Quote 0
                • D
                  DiodeDave
                  last edited by

                  Hi Guys,

                  I was able to fix my captive portal by adding the following to my custom portal page. it was not required before?

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

                    @DiodeDave:

                    Hi Guys,

                    I was able to fix my captive portal by adding the following to my custom portal page. it was not required before?

                    It was part of the default 'html logine page' when I was using 2.6.x as far as I can recall.
                    I guess checking has been re-enforced, because multiple portal zones can exist - and this is the way the portal server can know where the visitors are connecting from (which zone)

                    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
                    • J
                      jassrahal
                      last edited by

                      Yes, this line was there in previous versions but instead of value="$PORTAL_ZONE$" you had to specify the zone name.. So does this replaces the previous one or it's a addition?

                      1 Reply Last reply Reply Quote 0
                      • C
                        cmb
                        last edited by

                        @jassrahal:

                        Yes, this line was there in previous versions but instead of value="$PORTAL_ZONE$" you had to specify the zone name.. So does this replaces the previous one or it's a addition?

                        You could always specify the hard-coded name as the value instead of the variable, but the variable should always be used, in all versions. That way if you change your zone name, you don't have to change your portal page.

                        There is only one such line in the portal page.

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