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

    WebUI takes a long time to load

    Scheduled Pinned Locked Moved webGUI
    14 Posts 3 Posters 2.0k 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.
    • KOMK
      KOM
      last edited by

      It was Services - DNS Forwarder - Interfaces.  Leave it set to localhost.

      1 Reply Last reply Reply Quote 0
      • H
        Heli0s
        last edited by

        I use Chrome. But it seems to be an issue in either browser.

        It was Services - DNS Forwarder - Interfaces.  Leave it set to localhost.

        I've tried that, but it looks like my clients lose access to the DNS when I do that. Is there something I need to set in the DNS Forwarder page? Or any checkboxes that I need to set?

        1 Reply Last reply Reply Quote 0
        • KOMK
          KOM
          last edited by

          All I know is that when I changed the Interface from Localhost to All, the GUI became really unresponsive.  The only things I have set in DNS Forwarder are Enable and Interfaces - Localhost.

          1 Reply Last reply Reply Quote 0
          • H
            Heli0s
            last edited by

            @KOM:

            All I know is that when I changed the Interface from Localhost to All, the GUI became really unresponsive.  The only things I have set in DNS Forwarder are Enable and Interfaces - Localhost.

            So all other checkmarks are unchecked (you only have one checkbox checked)? I have some checkmarks in other checkboxes, so that might be the issue.

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM
              last edited by

              Yes.

              dns.png
              dns.png_thumb

              1 Reply Last reply Reply Quote 0
              • H
                Heli0s
                last edited by

                Thanks!

                Thanks a lot of IP addresses  :)

                1 Reply Last reply Reply Quote 0
                • KOMK
                  KOM
                  last edited by

                  Huh, I just noticed that I left those in the image.  Oh well, whatever.  I can count on pfSense to protect me.

                  1 Reply Last reply Reply Quote 0
                  • H
                    Heli0s
                    last edited by

                    I followed your advice, but the issue is that once I set the DNS Forwarder to localhost, all clients on the network lose DNS (they can still ping the WAN using IPs). I have the Google DNS servers (8.8.8.8 and 8.8.4.4) configured in the pfSense settings and the DHCP server dispenses the gateway's IP as the DNS server to the clients. Is there anything that needs to be done?

                    1 Reply Last reply Reply Quote 0
                    • H
                      Heli0s
                      last edited by

                      @phil.davis:

                      Are you using Firefox?
                      Did you read this post?
                      https://forum.pfsense.org/index.php?topic=82828.0

                      I'm using Chrome, but the same thing happens on Firefox as well. Also, I'm using HTTP and not HTTPS.

                      1 Reply Last reply Reply Quote 0
                      • KOMK
                        KOM
                        last edited by

                        Is there anything that needs to be done?

                        Sorry, no idea.  I was just sharing my experience with what happened to me.

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