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

    WebUI takes a long time to load

    webGUI
    3
    14
    1.7k
    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.
    • H
      Heli0s
      last edited by

      I'm having an issue where the webUI would work fine, but then every so often I would click to go somewhere and it would become non responsive. Even opening a new window takes a while. It's like there are connection hiccups. What could be the cause of that?

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

        I had a slow GUI issue once that involved a DNS setting I had changed from default in pfSense, but I don't remember where.  It was a list of interfaces for DNS to bind to, and I changed it from localhost to All or something.

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

          I did set it to ALL. But I'm still having issues. Is there any other setting that I need to set in the DNS Forwarder GUI?

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

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

            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
            • 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.