Navigation

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

    Strange issue with Webconfigurator

    Firewalling
    2
    3
    541
    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
      craigjl77 last edited by

      If I change the Webconfigurator from HTTPS to HTTP I cannot connect to it from my LAN. The LAN and Bridge rules are attached.
      I guess one of my questions is does the Antilockout rule need to be duplicated on the Bridge interface for this to work, on my setup?




      1 Reply Last reply Reply Quote 0
      • P
        phil.davis last edited by

        I guess one of my questions is does the Antilockout rule need to be duplicated on the Bridge interface for this to work, on my setup?

        No, the pass-all rule on the bridge is going to let you in anyway, unless your are Kids or Blake.
        I am not sure why you would want to change the Webconfigurator back to HTTP anyway? By default, when you connect to HTTP (port 80) it redirects to HTTPS and works securely.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

          Hi Phil,

          Thanks. Just curious as to why I got locked out of the web interface on the change ;-)

          1 Reply Last reply Reply Quote 0
          • First post
            Last post