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

    Portal cautivo redirecciona solo en HTTP y no en HTTPS ayuda por favor

    Español
    4
    4
    1.1k
    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.
    • A
      AdrianCuba
      last edited by

      El Portal cautivo redirecciona en  HTTP o sea yo pongo una pagina en HTTP y redirecciona al portal cautivo sin problemas el problema es que cuando pongo una HTTPS no redirecciona no se que pasa saludos.

      1 Reply Last reply Reply Quote 0
      • pttP
        ptt Rebel Alliance
        last edited by

        Lee: https://doc.pfsense.org/index.php/Captive_Portal_Troubleshooting#Captive_portal_not_redirecting

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

          @AdrianCuba:

          El Portal cautivo redirecciona en  HTTP o sea yo pongo una pagina en HTTP y redirecciona al portal cautivo sin problemas el problema es que cuando pongo una HTTPS no redirecciona no se que pasa saludos.

          ya encontraste alguna solucion, tengo ese problema pero no encuentro solucion

          1 Reply Last reply Reply Quote 0
          • A
            arnoldo0945
            last edited by

            ???  Leiste el Link, a la Documentacion Oficial, que dejaron en el post anterior al tuyo ?

            Captive portal not redirecting

            If clients are not being redirected to the portal page when attempting to browse on an interface with captive portal enabled, it's most always one of the following causes.

            1. DNS resolution not functioning - the clients on the captive portal interface must either be using the DNS forwarder on pfSense, on the IP of the interface where the client resides (which is the default configuration), or if using some other IP for DNS, it must be an allowed IP entry. If DNS fails, the browser never issues the HTTP request, hence it cannot be intercepted and redirected.

            2. Firewall rules on the captive portal interface do not allow the initial HTTP request - if the user is trying to browse to google.com, but HTTP connections are not allowed to google.com, the HTTP request will be blocked and hence cannot be redirected. Under Firewall > Rules, on the interface where captive portal is enabled, the traffic to be redirected must be allowed to pass. This is most commonly HTTP to any destination.

            3. The client has an HTTPS home page - The request must be to an HTTP site in order for the portal to redirect the client

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