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

    Unable to reach WebGUI after initial setup

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 2 Posters 485 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.
    • T
      Trent2458
      last edited by Trent2458

      Hey all,

      I created a HyperV environment for pfSense using This tutorial . I completed the initial setup, and both switches have been configured. My LAN is set to static and WAN set to DHCP. My problem is my modem IP range starts at 192.168.1.64, i'm guessing this needs to be adjusted in order for me to access the webgui?

      1685e7fd-be71-434f-8e98-4632270a2ca1-image.png

      22b3864a-b9f4-48e0-8275-3c498088f75e-image.png

      T 1 Reply Last reply Reply Quote 0
      • T
        Trent2458 @Trent2458
        last edited by Trent2458

        @Trent2458

        update: I set to dhcp and still experiencing the same problem. LAN is configured to 192.168.1.100/24

        rebooted and recieved this.

        79a9cac1-3d31-4ac3-8c9c-34eb14619fa9-image.png

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          You need to change one of those subnets. The WAN and LAN are conflicting. Try changing the pfSense LAN subnet to, for example, 192.168.100.1/24

          T 1 Reply Last reply Reply Quote 1
          • T
            Trent2458 @stephenw10
            last edited by

            @stephenw10 okay, I set my WAN to 192.188.1.88 and my LAN to 192.168.100.1, do i need to setup a port forward to access the webgui??

            T 1 Reply Last reply Reply Quote 0
            • T
              Trent2458 @Trent2458
              last edited by

              @Trent2458 This ended up fixing it. I was trying to connect while on WAN, connected to my LAN and it started working

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