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

    Losing UI access after creating adapter for VPN connection

    Scheduled Pinned Locked Moved General pfSense Questions
    7 Posts 2 Posters 1.1k 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.
    • J
      Jarpse
      last edited by

      Please move this thread if it should't be here.

      I have a pfSense managed from the WAN side (no LAN configged, intentionally), anti knockout rule is in place.

      When adding an adapter for an OpenVPN connection and enabling it, I can't access the WebUI anymore. The VPN connects from the other side though, and I can keep pinging the machine as well.

      I've tried the enableallowallwan, but since the pings (enabled ICMP) and connection get through, I assume this isn't the problem. Anyone that might know what I've forgotten here?

      1 Reply Last reply Reply Quote 0
      • K
        kejianshi
        last edited by

        Did you put your VPN on port 443 or 80?  TCP?

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

          Nope, default 1194. Web UI dies when I select "Enable Interface" and save it, box itself still has connection.

          1 Reply Last reply Reply Quote 0
          • K
            kejianshi
            last edited by

            No idea

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

              I've got it working now. Not sure what the problem was, but I placed the WebUI on a separate port and opened that up in the firewall. It stayed reachable now.

              1 Reply Last reply Reply Quote 0
              • K
                kejianshi
                last edited by

                Are you forwarding 80 or 443?

                Because usually thats the only time that happens?

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

                  Nope. No 80 or 443 come to play. I've changed the Web UI's port and opened it in the firewall, it stays reachable now. Not sure what happens, seems like the anti-knockout rule isn't effective anymore as other connections continue to work. Should be able to verify that when changing it back to 443 and opening the port seperately from the knockout rule.

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